[07:21] <mzanetti> Saviq: morning
[07:21] <mzanetti> Saviq: jenkins finally approved this: https://code.launchpad.net/~unity-team/unity8/launcher-backend/+merge/173189
[07:22] <mzanetti> so if you're still happy with it I think we can try to land it
[07:43] <mzanetti> MacSlow: hey
[07:43] <mzanetti> MacSlow: all the notification tests fail for various reasons here
[07:43] <mzanetti> MacSlow: but not the one you said :D
[07:44] <MacSlow> mzanetti, did you kill notify-osd?
[07:45] <mzanetti> MacSlow: I started a new dbus session
[07:45] <mzanetti> MacSlow: the notification shows up just fine
[07:45] <mzanetti> MacSlow: but then everything starts going wrong
[07:46] <MacSlow> mzanetti, I have never seen an issue with the opacity
[07:47] <MacSlow> mzanetti, I'm not starting a new dbus-session... just getting rid of notify-osd
[07:48] <mzanetti> MacSlow: no... I don't want to reboot my machine every time I run your tests :D
[07:48] <mzanetti> MacSlow: the d-bus session is just fine... the notifications show up as expected
[07:48] <mzanetti> btw... Frank Zappa looks way better than the name would suggest
[07:48] <MacSlow> mzanetti, :)
[07:49] <MacSlow> mzanetti, I had to use the stock assets :)
[07:49] <mzanetti> :D
[07:50] <MacSlow> mzanetti, so you just started the notification ap-test with "autopilot run unity8.tests.testnotifications"?
[07:50] <mzanetti> MacSlow: autopilot run unity8.tests.testnotifications.TestNotifications.test_sd_incoming_call
[07:50] <mzanetti> but yeah
[07:51] <MacSlow> mzanetti, ah ok... just the single one... I see.
[07:51] <mzanetti> MacSlow: the shell comes up, it unlocks the greeter and the incoming notification shows up.
[07:51] <mzanetti> MacSlow: then it times out because it waits for the opacity to become 1 while it stays at 0.99..
[07:52]  * mzanetti believes that might be related to the layer.enabled: true thingie
[07:52]  * mzanetti tries
[07:53] <MacSlow> mzanetti, I get some warnings/failures too... but not any issue with opacity (http://pastebin.ubuntu.com/5860909)
[07:54] <MacSlow> mzanetti, I'll try on my laptop
[07:54] <mzanetti> MacSlow: hmm.... Indeed adding print()s to onOpacityChanged shows it never goes to 1.
[07:54] <Saviq> mzanetti, re: launcher-backend yeah, I rebuilt it to get the actually fixed shell for testing with packages on device
[07:54] <mzanetti> MacSlow: and also, I can see the header from the dash behind shining through
[07:54] <Saviq> mzanetti, will test now and skim through again
[07:55] <mzanetti> Saviq: cool, thanks
[07:57] <mzanetti> MacSlow: I changed the check to be Eventually(GreaterThan(0.999999))
[07:57] <mzanetti> seems to work
[07:57] <mzanetti> MacSlow: so now I can reproduce your fail
[07:58] <mzanetti> MacSlow: this one?
[07:58] <mzanetti> self.assertThat (self.action_send_message_triggered, Equals(True))
[07:58] <MacSlow> mzanetti, your issue with the opacity-check is odd still... it also works on veebers machine like that
[07:58] <mzanetti> MismatchError: True != False
[07:58] <MacSlow> mzanetti, yeah... that's the issue with the callback not touching the bool flag
[07:58] <mzanetti> MacSlow: yeah... its odd... no idea why it doesn't really go to 1
[07:59] <mzanetti> Saviq: any idea perhaps?^
[08:00] <mzanetti> MacSlow: actually... the heightBehavior.enabled=true would never be called in my case then
[08:00] <veebers> MacSlow, mzanetti: I'm not sure it's an autopilot issue. I tried a really simple example in a script and couldn't get my callback called
[08:00] <MacSlow> mzanetti, doh... still need to pull updates on my laptop... still seeing the "black button"-problem there
[08:00] <MacSlow> veebers, you think it's a general python-issue then?
[08:00] <sil2100> veebers: hi! Big thanks for fixing the autopilot issue ;)
[08:01] <Saviq> MacSlow you're using the Ubuntu easings etc.?
[08:01] <MacSlow> veebers, mzanetti: should we try a newer python? atm 2.7 is used iirc
[08:01] <veebers> MacSlow: or I'm not constructing the callback et. al correctly :-P
[08:01] <veebers> MacSlow: shouldn't matter
[08:01] <MacSlow> Saviq, for the anims... yes.
[08:01] <sil2100> I guess you guys are talking about the latest failures with opacity checks?
[08:01] <Saviq> MacSlow, mzanetti I suspect the same issue we found in the SDK yesterday
[08:01] <veebers> sil2100: no worries, this was the failing tests one yes?
[08:01] <mzanetti> ah...
[08:01] <MacSlow> Saviq, like what issue?
[08:01] <Saviq> https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1199550
[08:01] <mzanetti> Saviq: good point
[08:02] <Saviq> MacSlow the bezier easing added in rev 600 of the toolkit http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/revision/600
[08:02] <Saviq> MacSlow, seems to not reach 1.0
[08:02] <Saviq> MacSlow, some rounding error
[08:02] <MacSlow> veebers, well there's one "difference" between the autopilot tests and the plain python-regression-tests...
[08:03] <Saviq> MacSlow, ideally you should look to the animation's running prop, not compare reals
[08:03] <Saviq> MacSlow, mzanetti although I would consider that a bug that an animation that's supposed to reach 1.0 doesn't because of some interpolation error
[08:04] <Saviq> Kaleo wasn't convinced yesterday, but I'll have a chat with him about this later today
[08:04] <MacSlow> veebers, mzanetti: since we had to do this "from gi.repository import GLib, Notify" I had to change the parameters passed to add_action() ... needs two additional arguments now otherwise it fails
[08:04] <mzanetti> Saviq: yeah... but the panel.animating never becoming false might be caused by the same... some thing never reaching the final state because of the same
[08:04] <sil2100> Saviq: to me that's an error, especially that we sometimes assume it reaches 1.0
[08:04] <Saviq> sil2100, exactly, you expect it to
[08:05] <Saviq> mzanetti, it definitely is (fixed in toolkit trunk)
[08:05] <sil2100> (like with opacity, suddenly causing failures in many autopilot tests ;p)
[08:05] <Saviq> http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/revision/601
[08:05] <MacSlow> Saviq, ok.
[08:05] <Saviq> s/fixed/workarounded/
[08:06] <mzanetti> Saviq: yeah... that doesn't seem like a proper fix
[08:07] <Saviq> mzanetti, well, it fixes the issue at hand, but not all the others
[08:07] <mzanetti> Saviq: it fixes one of the symptoms, but not the cause
[08:09] <Saviq> mzanetti, yup, what I meant
[08:10] <mzanetti> now... what's a bit more of a problem is that I replaced the UbuntuNumberAnimation  with a NumberAnimation and I still see the issue
[08:11] <veebers> MacSlow: ugh, I can get it working if I look at these examples: http://hashbang.fr/tutoriel-notify.html
[08:11] <veebers> MacSlow: it's using Gtk.main() at the end
[08:11] <FernandoMiguel> morning
[08:11] <FernandoMiguel> anyone from the am working in unity 7, that can help me debug a bug on 13.10 ? thanks
[08:11] <MacSlow> veebers, hm... in the regression-tests I'm using a dedicated Gtk-mainloop too
[08:12] <MacSlow> veebers, but I did assume that I don't need that in autopilot-tests
[08:14] <MacSlow> veebers, http://bazaar.launchpad.net/~unity-api-team/unity-notifications/trunk/view/head:/examples/interactive-notification.py#L65
[08:14] <MacSlow> veebers, http://bazaar.launchpad.net/~unity-api-team/unity-notifications/trunk/view/head:/examples/sd-example-incoming-call.py#L102
[08:14] <MacSlow> veebers, just for reference
[08:15] <Saviq> MacSlow, mzanetti can you check the output from http://pastebin.ubuntu.com/5860941/
[08:15] <veebers> MacSlow: hmm thanks. I might have to ask thomi re: that one tomorrow
[08:15] <MacSlow> veebers, ok... at least we're a bit closer now to sort it out
[08:15] <veebers> MacSlow: aye
[08:16] <mzanetti> Saviq: yeah... thats the cause
[08:16] <mzanetti> Saviq: stays at 0.999999999634
[08:16] <MacSlow> Saviq, "true 0
[08:16] <MacSlow> false 1
[08:16] <MacSlow> "
[08:17] <mzanetti> MacSlow: you need to upgrade to the latest ubuntu-ui-toolkit to reproduce the bug
[08:17] <mzanetti> MacSlow: well, don't...
[08:17] <MacSlow> mzanetti, :)
[08:17] <mzanetti> Saviq: here's the exact output:
[08:18] <Saviq> mzanetti, this could even cause some unnecessary blending
[08:18] <mzanetti> true 0
[08:18] <mzanetti> false 0.9999999999361473
[08:18] <mzanetti> Saviq: yes, it does. I can see the background of the notifications shining through
[08:18] <Saviq> mzanetti, that's expected, actually ;D
[08:18] <mzanetti> Saviq: huh?
[08:18] <Saviq> mzanetti, they're see-through - that's per-design
[08:19] <MacSlow> mzanetti, certainly... at least in the "black" area
[08:19] <mzanetti> Saviq: If I change all the UbuntuNumberAnimations to just NumberAnimations its not the case any more
[08:19] <mzanetti> well, I'm talking about the icon mostly
[08:19] <MacSlow> mzanetti, only buttons, text and icons are meant to be opaque
[08:19] <Saviq> mzanetti, I doubt it's visible (I doubt 8 bits can represent the difference)
[08:19] <Saviq> when rendered into ARGB
[08:20] <mzanetti> right... I just checked more carefully again.. its still there
[08:20] <mzanetti> but tests are passing again
[08:20] <Saviq> mzanetti, if you can see through the avatar, for example, that's a visual bug
[08:20] <mzanetti> Saviq: I do
[08:21] <mzanetti> but only with the black icon... not with the Frank Zappa lady :D
[08:21] <MacSlow> mzanetti, Saviq: maybe another newly introduced issue with the SDK? I don't have that here on my desktop-machine... let me look at the version of the installed SDK
[08:21] <Saviq> mzanetti, what should I be looking at?
[08:22] <mzanetti> MacSlow: actually... why does the same test, the incoming call one most of the times have the picture of that woman, but sometimes some grey abstract thingie?
[08:22] <MacSlow> mzanetti, ?
[08:22] <MacSlow> mzanetti, never seen that issue
[08:23]  * mzanetti tries to reproduce
[08:23] <mzanetti> yeah... just happened again
[08:23] <mzanetti> running this "autopilot run unity8.tests.testnotifications.TestNotifications.test_sd_incoming_call"
[08:24] <mzanetti> most of the times I get that lady in the icon. Sometimes only some grey icons with slightly orange stripes in it. thats when the background shines through...
[08:24] <mzanetti> Saviq: ^
[08:24] <Saviq> mzanetti, sil2100, MacSlow bug #1199662
[08:24] <MacSlow> Saviq, mzanetti: for what it's worth... I've 0.1.46+13.10.20130709-0ubuntu1 of qtdeclarative5-ubuntu-ui-toolkit-plugin installed here on my desktop
[08:24] <Saviq> mzanetti, which branch btw?
[08:24] <mzanetti> Saviq: ~macslow/unity8/notification-autopilot-tests/
[08:26] <jamesh> Saviq: I'm looking at putting together a scope to expose recent apps on the phone (something that is currently handled via custom UI).  Do you know if the API it uses to get the list of running applications is available outside of the shell process?
[08:26] <Saviq> tsdgeos, http://pastebin.ubuntu.com/5860963/
[08:27] <tsdgeos> Saviq: yeah
[08:27] <tsdgeos> no clue where that warning comes from tbh
[08:27] <tsdgeos> had a look at the define
[08:27] <tsdgeos> and it has just one param :/
[08:27] <Saviq> tsdgeos, k
[08:27] <Saviq> jamesh, it is / could be, but I don't believe that's what you should be looking at
[08:27] <Saviq> jamesh, I believe we should use zeitgeist there
[08:28] <tsdgeos> Saviq: i'll have a second look
[08:28] <Saviq> jamesh, while a specialized renederer in the shell would pick up the snapshots
[08:28] <Saviq> jamesh, running apps are going to be killed arbitrarily to save resources
[08:29] <Saviq> jamesh, so your "Recent apps" would start disappearing randomly
[08:29] <tsdgeos> but yeah, all QSKIP in Qt code are like that
[08:29] <jamesh> Saviq: I remember you saying that, but when I was talking with thostr_ he said that the design still calls for it to show running apps :(
[08:29] <tsdgeos> ./auto/corelib/io/qfile/tst_qfile.cpp:1900:            QSKIP("Not enough space to run test");
[08:29] <Saviq> jamesh, that's because they don't have a clue what a running app is ;)
[08:30] <Saviq> jamesh, i.e. there can't be a notion of a running app if we're killing and restarting them all the time
[08:30] <Saviq> tsdgeos, k, throw a #pragma at it maybe at some point
[08:30] <Saviq> jamesh, but we talked about this yesterday
[08:30] <Saviq> jamesh, in the dash sync
[08:30] <Saviq> jamesh, and I think the agreement is that we should use zeitgeist
[08:31] <Saviq> jamesh, granted, you need to be able to "close" such a recent app
[08:31] <jamesh> okay.
[08:31] <Saviq> jamesh, and that would actually kill the app, if it's running, but otherwise it should just disappear from the recent ones, that's it
[08:31] <jamesh> so I guess we still need an API to identify the apps that are currently running?
[08:31] <nic-doffay> Saviq, since the OptionSelector has so many variations for content, should the delegate be set externally be the user?
[08:31] <nic-doffay> *by
[08:31] <Saviq> jamesh, the shell does, the scope doesn't
[08:32] <Saviq> jamesh, but please confirm with thostr that's where we're goinf
[08:32] <Saviq> going
[08:32] <jamesh> okay
[08:32] <Saviq> jamesh, both launching and closing apps should be events in zeitgeist, I think
[08:33] <Saviq> jamesh, and you should just look at that and compile a list that were recently launched but not yet closed
[08:33] <Saviq> jamesh, ordering might be tricky, though - we might need to put focus events in, too :/
[08:34] <Saviq> jamesh, as in "app focused" event to order by
[08:34] <Saviq> now it does feel like zg is maybe not the best place
[08:35] <Saviq> jamesh, greyback we might need to build a volatile stack of "apps launched, but not closed"
[08:35] <jamesh> okay
[08:35] <Saviq> jamesh, greyback is working on unity8 integration with Mir where all of this will happen
[08:36] <greyback> Saviq: ok. I'd expected as much
[08:36] <Saviq> greyback, that's for "running apps", that aren't necessarily running anymore (lifecycle)
[08:37] <Saviq> greyback, do you think it'd make sense for jamesh to build a scope that would talk to the current observer on Surfaceflinger
[08:37] <Saviq> greyback, or would the new API be different enough that he should target the new api straight away?
[08:38] <greyback> Saviq: yep. I'd assumed App Manager will have list of all apps running or suspended or killed-with-resume-data
[08:41] <greyback> Saviq: thinking... it doesn't really make sense to do the SF work, if it'll be thrown away within a few weeks.
[08:41] <Saviq> greyback, I agree
[08:42] <Saviq> greyback, will app manager know the difference between app-with-resume-data and app-with-no-resume-data?
[08:42] <greyback> Saviq: that I have to learn.
[08:42] <Saviq> jamesh, greyback can you please sync up on those topics?
[08:42] <greyback> Saviq: it will be the one sending the kill signal, so I expect so
[08:43] <greyback> jamesh: hey, let's have a meeting on this, so we can swap info
[08:45] <jamesh> greyback: sure.  I currently don't have any code for this, so there isn't any legacy concerns if there is a new API in development
[08:46] <greyback> jamesh: indeed.
[08:49] <greyback> jamesh: meeting scheduled, does hte time suit you?
[08:52] <jamesh> greyback: looks good.
[08:52] <greyback> jamesh: cool
[08:53] <mzanetti> Saviq: quick'n'easy one: https://code.launchpad.net/~mzanetti/unity8/fix-1199622/+merge/173883
[08:53] <Saviq> mzanetti, obviously the "Critical" there was tongue-in-cheek ;)
[08:53] <Saviq> mzanetti, I'd never have noticed (nor did our designers, so...)
[08:53] <mzanetti> yeah...
[08:54] <mzanetti> Saviq: but funnily Cimi noticed the same for the separator line, but not for the icon
[08:54] <Saviq> mzanetti, yeah remember that :)
[08:55] <Cimi> mzanetti, oh michael
[08:55] <Cimi> mzanetti, off topic
[08:55] <mzanetti> hehe
[08:55] <Cimi> mzanetti, a friend told me that the ubuntu icon is flipped
[08:55] <mzanetti> Cimi: haha
[08:55] <Cimi> mzanetti, is he right? don't have the phone running now
[08:55] <mzanetti> just fixed that
[08:55] <Cimi> ok
[08:55] <Cimi> good
[08:55] <mzanetti> Cimi: https://plus.google.com/u/0/photos/104438618743851678614/albums/5898788268517651553/5898788275502369234?cfem=1&pid=5898788275502369234&oid=104438618743851678614
[09:17] <sil2100> andyrock: hello!
[09:18] <andyrock> sil2100, hey
[09:19] <sil2100> andyrock: do you know what's the status with compiz on saucy? Can we re-enable it for daily release?
[09:19] <andyrock> sil2100, nope... there is a bad regression
[09:19] <sil2100> Oh?
[09:19] <andyrock> sil2100, let me find the bug number
[09:20] <andyrock> sil2100, https://bugs.launchpad.net/compiz/+bug/1198000
[09:20] <andyrock> we can revert that revision
[09:20] <andyrock> but than we have another regression with qml5 apps
[09:20] <andyrock> *qt5
[09:21] <sil2100> oh shit
[09:21] <sil2100> Ok, so there's a deadlock right now, hm - I see no one is assigned here
[09:22] <andyrock> i'm trying to fix it, but decor.cpp is not that simple :D
[09:23] <sil2100> hohoho
[09:23] <sil2100> Ooooh no it isn't ;) I had my share of that file
[09:23] <mhr3> andyrock, sil2100, also i can't build trunk compiz because of some gmock issues
[09:25] <sil2100> andyrock: ^ ? Did anything change regarding that?
[09:25] <andyrock> sil2100, mhr3 nope, maybe there is some cmake issue with xorg-gtest?
[09:26] <mhr3> well, i saw gmock fixes proposed for nux and unity.. so definitely something wrong there
[09:28] <mhr3> sil2100, btw is unity still failing on the dbus issues?
[09:28] <andyrock> mhr3, yeah but I still can build compiz trunk here
[09:28] <mhr3> andyrock, from clean tree? on s?
[09:28] <andyrock> mhr3, let me clean it
[09:29] <andyrock> yeah on S sure
[09:29] <sil2100> mhr3: not sure, didn't see the DBus hang this week, but there are a lot of tests failing anyway
[09:30] <mhr3> sil2100, well that is the dbus hang
[09:30] <sil2100> It is? But it's only around 21 failures per platform and all seem to be preview tests
[09:30] <mhr3> sil2100, all those other super-hangs were caused by the recordmydesktop issue
[09:30] <sil2100> MismatchError: After 10.0 seconds test on DashView.preview_displaying failed: True != dbus.Boolean(False, variant_level=1)
[09:31] <sil2100> These are because of DBus?
[09:32] <sil2100> http://<IP_ADDRESS>:8080/job/autopilot-saucy-daily_release/387/testReport/ <- that's why I wanted someone to take a look at yesterdays failures, since to me those looked like normal failures
[09:32] <sil2100> But I might be mistaken
[09:33] <mhr3> sil2100, i see preview failures, hud failures, search timeouts, bamf failures, all dbus stuff
[09:34] <FernandoMiguel> https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1199696
[09:34] <FernandoMiguel> if anyone from unity7 can look it up
[09:35] <mhr3> sil2100, is there any way to re-run the testing with bustle-pcap running?
[09:35] <mhr3> sil2100, but probably just for one run, cause 50minute bustle-pcap session will produce a file that will be a few hundred mb
[10:22] <sil2100> mhr3: hm, I guess we could do that, but not sure how to do it only for one run, although we might modify the configuration of otto temporarily and then resume it back to the way it was
[10:23] <sil2100> mhr3: good to know it's all caused by dbus issues
[10:23] <sil2100> mhr3: since really, the logs don't say anything about that
[10:23] <sil2100> At least not explicitly
[10:23] <mhr3> sil2100, guess we can just connect to the lxc once the testing starts and run it manually
[10:24] <mhr3> sil2100, although i see that libunity on powerpc failed
[10:24] <sil2100> Yes, and one scope, looking into that
[10:24] <sil2100> (for i386)
[10:25] <sil2100> Need to re-try the jobs
[10:25] <mhr3> sil2100, ping me once the ap testing will be about to start i'll try to do the bustle capture
[10:27] <mhr3> jibel, if i want a log file to survive and be exported as a result in jenkins is it enough to just put it some special dir?
[10:27] <sil2100> mhr3: ok - what about the libunity failure for powerpc? I saw some unit test failing I think... although I also think we're not really caring about the powerpc status
[10:27] <sil2100> mhr3: I think it's sufficient if it land in some non /tmp directory
[10:27] <sil2100> We can fetch if from the diff then
[10:27] <mhr3> sil2100, looks like some odd race, just re-run
[10:29] <sil2100> k
[10:33] <tsdgeos> Saviq: https://bugreports.qt-project.org/browse/QTBUG-32338#comment-209093 and https://codereview.qt-project.org/#change,60809
[10:34] <jibel> mhr3, put it in /var/local/autopilot/
[10:34] <jibel> and it will be attached as artifact under results/autopilot/
[10:34] <mhr3> jibel, great, thx
[10:40] <tsdgeos> Saviq: nic-doffay: any reason this is not top-approved? https://code.launchpad.net/~saviq/unity8/improve-openeffect/+merge/173752
[10:42] <sil2100> mhr3: re-ran the stack, will poke you once the check job gets pushed to otto
[10:42] <mhr3> sil2100, cool thx
[10:43] <sil2100> mhr3: ok, autopilot job started
[10:43] <sil2100> mhr3: http://<IP_ADDRESS>:8080/job/autopilot-saucy-daily_release/396/
[10:51] <nic-doffay> Saviq, figured you might want someone else to take a look. But I'll do it now.
[11:17] <Saviq> nic-doffay, this is a simple enough change, and easy to test (did you get to test on a Nexus 10, where the slowness is most visible?)
[11:18] <Saviq> nic-doffay, but it's mostly about assuring that you see no regressions
[11:19] <Saviq> tsdgeos, awesome
[11:21] <Saviq> tsdgeos, src/quick/items/qquickgridview.cpp only has whitespace change, is that allowed in Qt patches?
[11:21] <tsdgeos> Saviq: hmmm, hmmm
[11:21]  * tsdgeos looks at the code
[11:22] <Saviq> tsdgeos, scratch that
[11:22] <tsdgeos> ok
[11:22] <Saviq> tsdgeos, I just can't read the gerrit diff
[11:22] <tsdgeos> i moved the code outside the if
[11:22] <Saviq> tsdgeos, yeah
[11:22] <Saviq> tsdgeos, too bleak colors there :)
[11:23] <tsdgeos> he he
[11:27] <nic-doffay> Saviq, I didn't test on a Nexus 10 which is part of the reason I held off.
[11:27] <Saviq> nic-doffay, you don't have one, right?
[11:27] <nic-doffay> Saviq, negative.
[11:28] <Saviq> tsdgeos, mzanetti you guys have a n10?
[11:28] <mzanetti> Saviq: I do
[11:28] <tsdgeos> i do
[11:28] <Saviq> mzanetti, could you look at https://code.launchpad.net/~saviq/unity8/improve-openeffect/+merge/173752 quickly
[11:28] <mzanetti> Saviq: sure
[11:28] <Saviq> tsdgeos, if you want to, try that↑, too
[11:28] <Saviq> it's a simple fix for nasty UX :)
[11:28] <tsdgeos> well, it'll take ages
[11:29] <tsdgeos> have to charge, flash, try :D
[11:29] <mzanetti> same here ^^
[11:29] <Saviq> lol
[11:30] <mzanetti> at least I already have the flipped image on it... so maybe a reflash is not required
[11:30] <Saviq> guys, it only takes like 10 minutes to download & flash here ;P
[11:31] <Saviq> and anyway most of the download is common between devices, so :P
[11:31] <mzanetti> Saviq: yeah... but charging it enough to survive a flash takes a bit longer
[11:31] <Saviq> mzanetti, :P
[11:31] <mzanetti> Saviq: nah... 10 mins should be ok
[11:32] <sil2100> mhr3: any luck?
[11:33] <mhr3> sil2100, did it finish yet?
[11:34] <sil2100> mhr3: still running - did you start bustle-pcap?
[11:35] <mhr3> sil2100, yea, it's half a gig already :)
[11:35] <sil2100> ohshit
[11:35] <sil2100> jibel: hope there's enough space for that?
[11:35] <sil2100> ^
[11:35] <mhr3> that's why didn't want to do it on every run :)
[11:40] <jibel> sil2100, enough space for what where ? :)
[11:42] <sil2100> jibel: additional logs from bustle-pcap - it weights over 0.5GB already! ;)
[11:42] <sil2100> (just for one run)
[11:42] <Saviq> tsdgeos, some of the filters are taken from unity-2d, so © Kaleo 2011 might be right :)
[11:42] <Saviq> ®©™
[11:42] <tsdgeos> ahhh
[11:42]  * Saviq loves compose :D
[11:43] <jibel> sil2100, it will be fine on the test host but will maybe causes some problem with the publication to jenkins.qa.u.c
[11:44] <sil2100> jibel: can we not publish that one build?
[11:44] <Saviq> tsdgeos, I just love how small the Qt patch is :)
[11:44] <tsdgeos> yep :-)
[11:44] <jibel> sil2100, if it's running it's too late
[11:44] <Saviq> tsdgeos, it might actually get in upstream :D
[11:45] <sil2100> booo...
[11:45] <Saviq> tsdgeos, will setting null / undefined to those props call reset*?
[11:46] <tsdgeos> that is a good question
[11:46] <tsdgeos> i was wondering what uses the RESET property function
[11:46] <tsdgeos> tbh not sure
[11:46] <tsdgeos> that's why i added the Q_INVOKABLE to reset*
[11:47] <tsdgeos> let me see if undefined indeed calls the reset* and then don't need the Q_INVOKABLEs
[12:07] <Saviq> tsdgeos, btw, should we allow only setting one of them? I know it doesn't make much sense... and printing debugs will just spew errors out on normal usage due to lack of sync
[12:07]  * Saviq wants tuples ;)
[12:12] <mzanetti> Saviq: improves things a little yes.
[12:12] <mzanetti> Saviq: there is still a small hickup when it loads the image for the first time
[12:12] <mzanetti> Saviq: but once that happened, its perfectly smooth now
[12:13] <Saviq> mzanetti, yeah, the hiccup... hickup? hikkup? stupid speller
[12:13] <Saviq> mzanetti, it's the Image / UbuntuShape
[12:13] <Saviq> mzanetti, we have the same in the dash views now when whole categories are created at a time
[12:14] <Saviq> mzanetti, we should try and isolate that to either and make sure we fix it if it's the shape
[12:15] <pete-woods> can anyone point me in the direction of the media player app's QML plugin for the MPRIS API?
[12:15] <Saviq> I knew it was "hiccup", both en_US and en_GB, stupid aspell or whichever
[12:15] <pete-woods> I'm told it uses the C API generated from http://bazaar.launchpad.net/~unity-team/libunity/trunk/view/head:/src/unity-sound-menu-mpris.vala
[12:15] <pete-woods> but I just can't see it in the mediaplayer-app
[12:15] <Saviq> pete-woods, jhodapp and renato would be the best PoCs
[12:15] <pete-woods> Saviq: thanks
[12:15] <Saviq> pete-woods, they might not be here yet
[12:16] <pete-woods> Saviq: okay, seems everyone I need today is in the wrong timezone :)
[12:20]  * mzanetti wonders if its actually a good idea that we install app-specific plugins (not intended for usage in other apps) int QT_QML_DIR
[12:21] <didrocks> mzanetti: not sure what QT_QML_DIR is set to, but it should be some kind of libexec/<app_name>/(plugin?) as a private library dir
[12:22] <mzanetti> didrocks: QT_QML_DIR is /usr/lib/<arch>/qt5/qml/
[12:22] <mzanetti> didrocks: basically where Qt stuff itself is too
[12:22] <didrocks> yeah, should s/qt5/<appname>/ IMHO
[12:22] <mzanetti> didrocks: yeah. I agree
[12:22] <didrocks> if it's not going to be reused by multiple apps
[12:24] <Saviq> mzanetti, didrocks +1, what we did for the shell
[12:24] <Saviq> mzanetti, which plugins are you thinking?
[12:25] <mzanetti> Saviq: PhoneApp, Browser, CameraApp...
[12:25] <mzanetti> Saviq: bascially everything in there except Qt stuff itself and Ubuntu.Components
[12:25] <mzanetti> and a few other exceptions
[12:25] <mzanetti> lide Dee probably
[12:25] <mzanetti> like
[12:26] <mzanetti> ShareApp might be an exception too... depending on whats in there
[12:29] <Saviq> mzanetti, then yeah, +1
[12:29] <Saviq> mzanetti, they should be installed in private under $LIBDIR/<app_name>/qml
[12:31]  * mzanetti just realized that the terminal-app uses KDE's konsole :)
[12:31] <mzanetti> tsdgeos: ^
[12:34] <pete-woods-away> the terminal-app could do with exiting when you type exit! :p
[12:34] <sil2100> mhr3: the AP tests finished
[12:35] <mhr3> sil2100, yep, downloading the log
[12:35] <sil2100> mhr3: 511 MB ;)
[12:42] <kgunn> Saviq: ping
[12:43] <Saviq> kgunn, pong
[12:56] <tsdgeos> mzanetti: yep
[13:01] <Saviq> mzanetti, add =2 to pkg_check_modules(LAUNCHER_API REQUIRED unity-shell-launcher) maybe?
[13:01] <mzanetti> Saviq: is that really a question?
[13:02] <Saviq> mzanetti, you decide :D
[13:02] <mzanetti> dude
[13:02] <mzanetti> :SD
[13:02] <Saviq> mzanetti, it'll fail if the version is different, so yeah, probably makes sense :)
[13:02] <mzanetti> yes. I agree
[13:02]  * mzanetti fixes
[13:08] <mzanetti> Saviq: pushed
[13:08] <Saviq> mzanetti, thanks
[13:20] <mhr3> sil2100, ehm, so great, the bustle tools can't really handle huge captures
[13:20] <mhr3> $ bustle --count dbus.bustle
[13:20] <mhr3> Stack space overflow: current size 8388608 bytes.
[13:21] <mhr3> oh and yes, it was using 6gb of ram
[13:23] <Saviq> lol
[13:25] <sil2100> eeh
[13:25] <sil2100> So we're again with nothing? Or can you
[13:25] <sil2100> read something from what we got?
[13:25] <sil2100> (or we got nothing)
[13:32] <Saviq> mzanetti, hmm =2 didn't work
[13:32] <mzanetti> so... who is going to take notes... Saviq or Cimi?
[13:33] <dednick> Saviq: jenkins approve!!
[13:33] <mzanetti> Saviq: hmm. I did a test run here... printed "found launcher (version 2)"
[13:33] <Saviq> dednick, nice
[13:33] <Saviq> mzanetti, yeah, change it to 1 or 3
[13:33] <Saviq> mzanetti, says that it found (version 1) etc.
[13:33] <mzanetti> huh? stupid pkgconfig
[13:34] <Saviq> Cimi, standup?
[13:46] <Saviq> mzanetti, ok, so - if you can get pkgconfig to fail if !=2, that's the last thing I have there
[13:57] <Saviq> BOOM
[14:00] <tsdgeos> Saviq: do we really not need any ppa anymore?
[14:00] <Saviq> tsdgeos, not for build dependencies, for runtime... potentially, but those should start popping up in distro
[14:01] <Saviq> tsdgeos, we might need to add ppa:ubuntu-unity/next later, though
[14:01] <tsdgeos> :D
[14:01] <Saviq> tsdgeos, for stuff that's not yet distro-ready
[14:01] <tsdgeos> so waht do we do with https://code.launchpad.net/~saviq/unity8/clean-build-scripts-coding/+merge/173847 ?
[14:01] <tsdgeos> want me to get a VM and see if i can build and run with that code?
[14:01] <tsdgeos> or?
[14:01] <Saviq> tsdgeos, yeah please
[14:01] <Saviq> tsdgeos, but I can tell you that you can
[14:02] <Saviq> tsdgeos, indicators are not gonna be there, but they're not really there today either
[14:02] <tsdgeos> sure, but we're supposed to review the changes, no?
[14:02] <tsdgeos> :D
[14:02] <Saviq> tsdgeos, :F
[14:03] <tsdgeos> Saviq: we only support saucy, right?
[14:04] <Saviq> tsdgeos, +1
[14:05] <Saviq> dednick, hmm I just tried "autopilot run unity8.indicators_client"... I noticed that was wrong, but shouldn't we keep all our AP tests under unity8?
[14:06] <Saviq> dednick, they don't necessarily need to run with `autopilot run unity8`
[14:06] <Saviq> mzanetti_, thoughts ↑?
[14:09] <dednick> Saviq: dont understand. you want them to run with unity8 or not?
[14:09] <Saviq> dednick, not necessarily
[14:09] <Saviq> dednick, don't know, really
[14:10] <Saviq> dednick, it's cool keeping them separate
[14:10] <dednick> Saviq: the ap tests are in the unity8-autpilot package, but they are separated into a different suite
[14:10] <Saviq> dednick, but referenced by "unity8.indicators_client" nevertheless
[14:10] <Saviq> dednick, it's probably just a case of moving them under the unity8 dir
[14:10] <Saviq> dednick, I think we shouldn't install them directly on PYTHONPATH
[14:10] <dednick> Saviq: i c.
[14:11] <dednick> Saviq: although in that case they would run with unity8 i'm guessing
[14:11] <Saviq> dednick, not if they're not in unity8.tests
[14:11] <dednick> Saviq: ah. right
[14:11] <Saviq> dednick, you'd have to import them in there, I think
[14:11]  * Saviq checks
[14:12] <Saviq> dednick, yeah, imports need unity8. but that's about it
[14:13] <Saviq> dednick, nope, it recursively looks for tests
[14:13] <Saviq> dednick, I'm still better with that than polluting PYTHONPATH, to be honest
[14:14] <Saviq> mzanetti_, ↑ need your opinion here
[14:21] <pete-woods> is there a process for getting your API HTML docs onto developer.ubuntu.com?
[14:24] <seb128> dpm, ^ seems like a question for you ;-)
[14:24] <seb128> pete-woods, dpm can probably help there
[14:25] <pete-woods> seb128: thanks :)
[14:25] <seb128> yw
[14:27] <dpm> pete-woods, essentially get all the HTML docs in a -doc package and pinging me or mhall119 to get them imported into d.u.c
[14:27] <pete-woods> dpm: I already have them in a -doc package - it's libusermetrics-doc
[14:27] <dpm> pete-woods, for the nitty gritty details there's http://bazaar.launchpad.net/~api-doc-publisher-hackers/api-doc-publisher/trunk/view/head:/README#L37
[14:28] <dpm> pete-woods, ah, cool. What kind of API docs are they? I.e. which generator do you use? qdoc? doxygen? And for what programming language is the API for?
[14:29] <pete-woods> dpm: it's doxygen, the language is Qt/C++, there's also a pure C API
[14:30] <dpm> pete-woods, let me see if I can get the docs published now. I assume they are for saucy only?
[14:30] <pete-woods> dpm: yeah, the package is saucy only atm
[14:32] <pete-woods> dpm: and thanks!
[14:32] <mhall119> pete-woods: why doxygen and not qdoc?
[14:33] <dpm> pete-woods, there you go: http://developer.ubuntu.com/api/devel/ubuntu-13.10/cplusplus/usermetrics/
[14:33] <pete-woods> mhall119: er, no good reason?
[14:34] <pete-woods> dpm: awesome!
[14:39] <mzanetti> Saviq: dednick_: yeah... make them separate please
[14:39]  * mzanetti was cooking
[14:39] <mzanetti> we can then add multiple test suites to jenkins
[14:47] <dednick_> Saviq: unity8/shell & unity8/indicators_client ?
[14:49] <mzanetti> dednick_: tests/autopilot/unit8 (the existing ones) and tests/autopilot/indicators_client (the new ones)
[14:49] <mzanetti> dednick_: can be both in the same autopilot package tho
[14:50] <dednick_> mzanetti: yeah, that's what it is at the moment, but Saviq's issue is the pollution of the PYTHON_PATH folder.
[14:50] <mzanetti> ah
[14:50] <dednick_> although it's a sep app, so i dont see an issue really.
[14:50] <mzanetti> me neither... also, I believe (not entirely sure) that it neds to be top level for autopilot being able to process it
[14:51] <mzanetti> but that would need to be proved... as I said. not sure
[14:51] <dednick_> mzanetti: apparently not
[14:51] <dednick_> just need to import the folder in __init__
[14:53] <dednick_> i think Saviq may be cooking as well.
[14:53] <nic-doffay> mzanetti, need your thoughts on something super quick.
[14:54] <mzanetti> nic-doffay: I'll b back in 20 mins
[14:54] <nic-doffay> mzanetti, cool no rush.
[14:54] <nic-doffay> mzanetti, it's basically "how much of a hack do you think think this is"
[14:56] <dednick_> if you have to ask that...
[14:59] <nic-doffay> dednick_, good point.
[14:59] <nic-doffay> dednick_, I guess I wanted to check how guilty I am. :P
[15:14] <nic-doffay> Saviq, my expandable component currently inherits from ListItems.Base. I'm trying to wrap it around the ListView in my OptionSelector so that the expandable can handle the expansion.
[15:14] <nic-doffay> It's obscuring all the items in the list view though :P
[15:15] <nic-doffay> Any idea why? Even when I set it to opacity: 0 it doesn't make a difference.
[15:17] <Saviq> dednick_, mzanetti, well indicators_client is not really an app, is it...
[15:17] <Saviq> dednick_, should we just go unity8.shell and unity8.indicators_client, then?
[15:18] <Saviq> nic-doffay, I'd say Expandable should inherit from Empty at most
[15:18] <Saviq> nic-doffay, or is Base even higher up the stack?
[15:19]  * Saviq doesn't remember
[15:19] <nic-doffay> Saviq, empty is.
[15:19] <nic-doffay> Saviq, done. However I still need to disable the MouseArea support for the expandable component because it's swallowing the clicks that should be sent to the ListView delegates.
[15:19] <nic-doffay> Any ideas on how to achieve this?
[15:20] <mzanetti> Saviq: dednick_: if autopilot can handle it, its fine with me
[15:20] <mzanetti> nic-doffay: would be here now if you still need me
[15:21] <Saviq> nic-doffay, Empty doesn't have a MouseArea
[15:22] <Saviq> dednick_, ah, see! you read my mind :)
[15:22] <dednick_> Saviq: :)
[15:23] <Saviq> dednick_, I'd go for "autopilot-shell" for the target name, though ><
[15:24] <dednick_> Saviq: yup. when i make the changes to the folder structure i'll add a name to the add_autopilot_test macro
[15:27] <Saviq> dednick_, ah now I get what you said... was thinking you already moved the folders around
[15:28] <Saviq> dednick_, you probably need an empty __init__.py there
[15:28] <dednick_> Saviq: yeah. just with the imports in it i think
[15:32] <nic-doffay> Saviq, it does have an onClicked
[15:32] <Saviq> nic-doffay, Empty doesn't?
[15:33] <dednick_> Saviq: ok, done. Jenkins should be able to test it without manual trigger now there is only 1 suite.
[15:33] <Saviq> dednick_, indeed, we'll modify it later to have separate unity8.shell unity8.indicators_client maybe
[15:33] <Saviq> not sure that's desirable, though
[15:33] <Saviq> but doesn't really matter much
[15:34] <nic-doffay> Saviq, I'm pretty sure it does :P
[15:34] <nic-doffay> It doesn't compain with my onClicked logic.
[15:35] <nic-doffay> *complain
[15:35] <Saviq> nic-doffay, ah! it's an AbstractButton of course
[15:35] <nic-doffay> Saviq, which brings me to the swallowing touches question.
[15:35] <Saviq> nic-doffay, but then it shouldn't matter, anything you add _into_ it will be on top, why should it swallow the touches?
[15:35] <nic-doffay> Saviq, at the moment the Expandable is a parent of the ListView.
[15:36] <Saviq> nic-doffay, sure, Empty > Expandable { ListView }
[15:36] <Saviq> nic-doffay, so ListView is on top
[15:36] <nic-doffay> Saviq, yep.
[15:36] <Saviq> nic-doffay, so it takes over all mouse events
[15:36] <nic-doffay> Which I thought would be cool.
[15:36] <Saviq> nic-doffay, it is
[15:36] <nic-doffay> But it doesn't.
[15:37] <nic-doffay> Saviq, there might be some other issue though.
[15:37] <nic-doffay> ^ most likely the case.
[15:39] <Saviq> nic-doffay, http://pastebin.ubuntu.com/5861973/ works
[15:39] <Saviq> nic-doffay, so I see no reason why yours wouldn't
[15:41] <tsdgeos> Saviq: should i top approve https://code.launchpad.net/~saviq/unity8/clean-build-scripts-coding/+merge/173847 or want kgunn to have a look?
[15:44] <mzanetti> Saviq: found the issue... pushed the fix
[15:45] <kgunn> MacSlow: hey, so strehl and i were just chatting
[15:46] <MacSlow> kgunn, about the autopilot-issue?
[15:46] <Saviq> mzanetti, cheers
[15:46] <Saviq> tsdgeos, I assigned kgunn for it really to push it to the website
[15:46] <kgunn> MacSlow: sorry about notifications in general
[15:46] <kgunn> MacSlow: questoin is for things that want to produce  sound or haptics
[15:46] <Saviq> tsdgeos, so you can approve
[15:47] <tvoss_> sil2100, could you please try including QGLShaderProgram and getting rid of the manual gl version detection there?
[15:48] <MacSlow> kgunn, there's an optional "sound-file" hint... http://www.galago-project.org/specs/notification/0.9/x344.html
[15:49] <kgunn> MacSlow: so do we have that ? (sorry i'm on a nexus7 ...w/o modem)
[15:49] <MacSlow> kgunn, regarding "haptics" ... since we introduced our own hints... there's nothing stopping us for doing that for haptic-feedback on notifications should we chose to do so.
[15:49] <tvoss_> sil2100, you can just check for the default gles version macro then to define the texture target
[15:49] <MacSlow> kgunn, not atm... Design never pushed for this.
[15:49] <kgunn> MacSlow: but aren't notif's used for phone calls/sms's etc....
[15:50] <kgunn> vibra would be needed
[15:50] <MacSlow> kgunn, but at first glance it doesn't seem to be too much trouble to implement it... if there's a solid spec for it :)
[15:50] <kgunn> MacSlow: ok...sounds like we should add it as a work item in the bp
[15:51] <MacSlow> kgunn, since sound and haptic/vibration are not visual it could all just happen on the backend without the frontend/renderer needing to know?!
[15:52]  * tedg always wanted his phone to vibrate the calling number is Morse code
[15:52] <tedg> in
[15:52] <kgunn> MacSlow: this is why i was asking...who would really own
[15:52] <kgunn> ?
[15:52] <kgunn> MacSlow: strehl was thinking we should own
[15:53] <kgunn> MacSlow: is notif spec silent on this topic ?
[15:54] <MacSlow> kgunn, that question was never really answered... nobody really owns it... I tried what I can to cover for this in the mean-time... but having a team really own the spec (functional-design, tech-spec) would be great
[15:54] <nic-doffay> Saviq, see this is giving me the issues: https://pastebin.canonical.com/94121/
[15:55] <nic-doffay> The Expandable which is an Empty still swallows the clicks and I'm unable to see any of the ListView delegates.
[15:55] <MacSlow> kgunn, what spec are you refering to? ours or the freedesktop/galago one?
[15:55] <sil2100> tvoss_: k, thanks!
[15:55] <tvoss_> sil2100, yup :)
[15:55] <tvoss_> sil2100, let me know if that works
[15:55] <kgunn> MacSlow: galago one
[15:56] <MacSlow> kgunn, there's just this optional "sound-file" hint in http://www.galago-project.org/specs/notification/0.9/x344.html
[15:56] <Saviq> nic-doffay, what's your ListView's height, then?
[15:56] <nic-doffay> Saviq, 0 for some reason.
[15:56] <nic-doffay> But the delegates all print out their correct heights.
[15:57] <Saviq> nic-doffay, ListViews don't grow to their delegates by default
[15:57] <MacSlow> but speaking of the "incoming phone-call" use-case... wouldn't the phone-app ring/vibrate anyway?
[15:57] <Saviq> nic-doffay, height: contentHeight if you want it
[15:57] <nic-doffay> Saviq, kk thanks.
[16:10] <Saviq> dednick_, you didn't add the __init__.py in tests/autopilot/unity8
[16:10] <Saviq> dednick_, it can actually be empty
[16:11] <Saviq> dednick_, autopilot goes recursively through them it seems
[16:15] <Cimi> seb128, who do I need to ask if xorg crashes?
[16:16] <seb128> Cimi, #ubuntu-x you can try ping mlankhorst or tjaalton directly but they might be eod already
[16:16] <Cimi> seb128, like segfaulting :(
[16:16] <Cimi> on vmware
[16:16] <Cimi> after last update
[16:16] <Cimi> pixman
[16:17] <Cimi> or I try mir
[16:17] <mlankhorst> vmware doesn't have support for mir
[16:18] <Saviq> mzanetti, hmm, I'm not sure I'm liking what you did in CMake
[16:18] <mzanetti> Saviq: I feared that
[16:18] <Saviq> mzanetti, ;)
[16:18] <mzanetti> Saviq: whats your reason?
[16:19] <Saviq> mzanetti, my hope is that the plugins are as self-contained as possible (and I know they're not, yet)
[16:19] <mzanetti> Saviq: so... the thing is, it I do the check_pkg thingie twice, the second (in mocks) will override the first
[16:19] <mzanetti> Saviq: that was the reason why the check didn't work
[16:20] <Saviq> mzanetti, yeah, I get it, but if both have =2, it'll work, right?
[16:20] <mzanetti> Saviq: I could copy/paste the same into both
[16:20] <mzanetti> so the first one in plugins would be just "documentation" but basically useless
[16:20] <Saviq> mzanetti, the mock one will remain with us while Unity.Launcher can get moved to a separate project
[16:20] <mzanetti> Saviq: thats true, yes
[16:21] <mzanetti> ok... I can move it back into there
[16:21] <Cimi> mlankhorst, if pitman segfaults?
[16:21] <Cimi> *pixman
[16:22] <Saviq> mzanetti, dednick_ it's a race, btw, your branches conflict in debian/control. so whoever gets in first gets to not fix the conflict ;D
[16:22] <Saviq> unless one of you merges the other one's branch in and prerequisites it, of course ;D
[16:23] <tvoss_> mzanetti, ping
[16:23]  * mzanetti runs
[16:23] <mzanetti> tvoss_: pong
[16:23] <mzanetti> tvoss_: the run was not meant for you :D
[16:23] <Saviq> rotfl
[16:25] <Saviq> greyback_, can you invite me to your chat with jamesh please?
[16:25] <mlankhorst> Cimi: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vmware/+bug/1199403 ?
[16:26] <Cimi> mlankhorst, might be
[16:26] <Cimi> mlankhorst, I have the same issue
[16:26] <Cimi> so I guess it's the driver
[16:26] <greyback_> Saviq: we had it at 11am UTC today
[16:27] <Saviq> greyback_, lol
[16:27] <john-mcaleely> mfisch, ping...
[16:27] <mfisch> hey mhall119, john-mcaleely spotted a typo in the scopes tutorial, can you fix it?
[16:27] <Saviq> greyback_, thought jamesh was EOD by that time
[16:27] <mfisch> mhall119: https://bugs.launchpad.net/ubuntudeveloperportal/+bug/1199839
[16:27] <mfisch> its just a misspelling of "apt"
[16:37] <sil2100> tvoss_: strangely, now it doesn't find glUniformMatrix4fv when trying to build with GLES2
[16:37] <sil2100> tvoss_: even though it seems to include the right headers
[16:38] <sil2100> tvoss_: no, wait
[16:39] <john-mcaleely> mhall119, while I'm at it (spotting bugs), I'll have a look at adding some packaging to that example.
[17:02] <Saviq> didrocks, indicators-client is going away, like, tomorrow
[17:02] <Saviq> didrocks, i.e. it's getting merged into lp:unity8
[17:02] <didrocks> Saviq: I'm sure you will be happy the autopilot tests will run with nothing :p
[17:02] <didrocks> Saviq: thanks for the head's up!
[17:10] <didrocks> fginther: I see a lot of B09googletests hooks used in jenkins
[17:10] <didrocks> fginther: but most of the time, we already run the tests as part of the package
[17:10] <didrocks> so they are run twice
[17:11] <didrocks> fginther: we should maybe look at remove those which makes sense (and if we see that one isn't running tests while building the package, activating that?)
[17:11] <fginther> didrocks,yes. It's really a project by project check
[17:12] <didrocks> fginther: ok, I'll have a look tomorrow at that
[17:12] <didrocks> fginther: if nothing in the stack runs the tests, we don't need to have the googletests_cmake and _install?
[17:13] <fginther> didrocks, I'm not following.
[17:13] <fginther> do you mean project?
[17:13] <didrocks> fginther: I mean, if we don't nede the B09googletests hook in any project of the stack
[17:13] <didrocks> fginther: we should remove the other *googletests* hooks from the stacks?
[17:13] <fginther> didrocks, ah, right
[17:14] <didrocks> ok, will work on that tomorrow :)
[17:14] <fginther> didrocks, cool!
[17:14] <mzanetti> Saviq: ok. moved it back.
[17:15] <Saviq> mzanetti, thanks
[17:15] <mzanetti> Saviq: I left the add_subdirectory where it is now... next to the other one and the comment
[17:15] <mzanetti> fits better there
[17:15] <Saviq> mzanetti, k
[19:45] <mzanetti> Saviq: still around?
[19:48] <Saviq> mzanetti, knida
[19:48] <Saviq> kinda, even
[19:48] <mzanetti> Saviq: http://paste.ubuntu.com/5862687/
[19:48] <mzanetti> Saviq: run this and watch your CPU
[19:49] <mzanetti> noticed unity8 going crazy when I left it with a popover opened
[19:49] <Saviq> mzanetti, ah, same issue I believe
[19:50] <mzanetti> ah, the animation?
[19:50] <Saviq> mzanetti, http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/revision/584
[19:52] <Saviq> mzanetti, https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1197801
[19:54] <mzanetti> Saviq: but I only see this when I open a popover, I believe
[19:54] <Saviq> mzanetti, yeah, that's because the popover uses the shape (and is only created when you open it)
[19:54] <Saviq> mzanetti, and destroyed when you close it
[19:54] <mzanetti> Saviq: oh... is it the UbuntuShape that can clip everything, not just images
[19:54] <mzanetti> I see
[19:55] <Saviq> mzanetti, well, Shape itself can, there's an issue with updating the textures
[19:56] <Saviq> mzanetti, I commented on the bug and pinged Kaleo
[19:56] <Saviq> pung?
[19:56] <mzanetti> lol
[20:04] <mterry> tvoss|dinner, poke about meeting
[20:08] <Saviq> dednick_, you still around?
[20:09] <Saviq> dednick_, there's no need for the imports in unity8/__init__.py IIUC?
[22:02] <Saviq> veebers, hey, so I didn't get to getting you the data you requested, but the VM is up and I'm leaving it that way
[22:02] <veebers> excellent, thanks Saviq
[22:06] <veebers> Saviq: if you're still around, I get a connection time out w/ that machine
[22:21] <kgunn_> Saviq: did you want me to try ...https://code.launchpad.net/~saviq/unity8/clean-build-scripts-coding/+merge/173847
[22:22] <kgunn_> sorry just catching up on the todo's
[22:43] <dednick_> Saviq: imports removed


[17:51] <sonicwind2> Client: HexChat 2.14.1 • OS: Ubuntu "bionic" 18.04 • CPU: Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz (1.71GHz) • Memory: Physical: 7.4 GiB Total (6.5 GiB Free) Swap: 953.1 MiB Total (953.1 MiB Free) • Storage: 24.2 GB / 253.2 GB (229.0 GB Free) • VGA: Intel Corporation 3rd Gen Core processor Graphics Controller @ Intel Corporation 3rd Gen Core processor DRAM Controller • Uptime: 4m 27s


[00:02] <Cimi> bratsche: ok?
[10:48] <Cimi> seb128: I might have some patches for qt that fixes qgtkstyle with light-themes
[10:48] <Cimi> seb128: is it too late in your opinion?
[10:49] <seb128> Cimi, not sure, depends of the change
[10:49] <seb128> you can try asking Riddell
[10:49] <seb128> he's on charge of kubuntu
[10:50] <Cimi> seb128:  these two bugs (left fixed, right current) http://i.imgur.com/BlGS6.png http://i.imgur.com/Ez3z3.png
[10:51] <seb128> Cimi, well I meant it depends of the code diff
[10:51] <seb128> we take only things easy to review at this point
[10:51] <seb128> ie we will not take code refactoring to fix issues
[10:51] <Cimi> ok
[10:52] <Cimi> seb128: one of the contacts I have is the qt developer behind qgtkstyle
[10:52] <Cimi> seb128: so these patches are quite safe because they come from him :)
[10:53] <Cimi> but I can understand
[10:53] <Cimi> I'll ask him to publish the patches somewhere
[10:54] <Cimi> (he is a friend of mine)
[11:05] <seb128> Cimi, ok, just get the diff on a bug report
[11:05] <seb128> then we can get it reviewed for upload
[11:06] <Cimi> seb128: cool
[11:17] <Cimi> mpt: ping
[11:24] <Cimi> I have just fixed this: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/635208
[11:24] <ubot5`> Launchpad bug 635208 in software-center (Ubuntu) "Unfocused selected item in software list is white on light grey (affected: 1, heat: 12)" [Low,Fix committed]
[11:24] <Cimi> someone please review it and upload!
[11:25] <Cimi> seb128: http://bugreports.qt.nokia.com/browse/QTBUG-13792
[11:31] <seb128> Cimi, ok, I pointed those to mvo and Riddell on #ubuntu-desktop
[11:32] <seb128> the software-center one will be merged and in the next upload
[11:33] <Cimi>  7ok cool
[11:33] <Cimi> thanks seb128
[11:45] <Cimi> seb128: the other qt bug http://bugreports.qt.nokia.com/browse/QTBUG-14161
[11:46] <seb128> Cimi, ok
[11:46] <seb128> you might want to join #ubuntu-desktop and talk to Riddell
[11:48] <Cimi> ok
[12:43] <Cimi> someone please ping me back when davidbarth will come online
[13:06] <davidbarth> Cimi: back (or reconnected in fact)
[13:08] <Cimi> davidbarth: I'm discussing on ubuntu-gesktop
[14:05] <rye_> hello people. I am now facing a very interesting feature/bug with libappmenu - my layout began flickering (i.e. іf i press aaaaaaaaaaa repeatedly it goes фaфaффaaфaaaф or something like this).
[14:05] <rye_> I noticed that gnome-settings-daemon consumed a lot of CPU, after switching to tty i was able to attach to it and i found that libappmenu calls are there.
[14:06] <rye_> I was a victim of this bug once on my netbook but I was not really sure whether this is a hardware fault or not, but now it looks like this is something in libappmenu restarting gnome-settings-daemon
[14:06] <rye_> resetting, not restarting, since it continues running
[14:24] <rye_> here's teh backtrace I get when i resume/interrupt g-s-d now - http://paste.ubuntu.com/503897/, I will keep g-s-d in gdb in case I can fetch more info from that
[14:47] <bratsche> Cimi: Are all these blur implementations really being used in murrine?
[14:47] <Cimi> yes
[14:48] <Cimi> menu and buttons
[14:48] <bratsche> k, just checking.
[14:48] <Cimi> just the exponential I guess
[14:53] <bratsche> Oh really?  It's not using gaussian or stack blurs?
[14:54] <Cimi> it is using the fastest
[15:04] <bratsche> Cimi: Do you mind if I commit the license update to git?  I've already got the patch prepared.
[15:05] <Cimi> no I don't
[15:05] <Cimi> and thanks ;)
[15:05] <Cimi> busy on indicator-,essages
[15:06] <bratsche> Okay, just pushed to git.
[15:06] <bratsche> Thanks!
[15:11] <Cimi> bratsche: did you relicense murrine as well?
[15:12] <bratsche> Yes.
[15:12] <bratsche> I changed COPYING from GPLv2 to LGPLv3 and included a COPYING.2.1
[15:12] <bratsche> Does that sound okay?
[15:13] <Cimi> ok
[16:36] <JanCBorchardt> hey mgunes, can you confirm your Gitorious account at ~muratgunes? The email address was not familiar so I hesitated. ;)
[16:37] <JanCBorchardt> and mpt, if you want repo access just give me your Gitorious account name or open one
[16:38] <mpt> thanks
[16:38] <mgunes> JanCBorchardt, surely it's my account. Gitorious refused to send a confirmartion mail to my ubuntu.com address for some reason.
[16:46] <JanCBorchardt> mgunes, thanks, you're in
[16:51] <mgunes> thanks


[02:29] <iccus> sp?
[02:29] <iccus> there?
[08:37] <slytherin> Is there anyway to run live cd without using cd i.e. from iso?
[08:37] <mikess> what version of alsa in hardy?
[08:38] <slytherin> mikess: 1.0.15
[08:39] <mikess> great it will work on my laptop
[08:39] <jussi01> slytherin: I think so... you mean to install??
[08:39] <mikess> slytherin: cheers,I hope my atheros chip is supported as well
[08:39] <jussi01> !install | slytherin
[08:39] <ubotu> slytherin: Ubuntu can be installed in lots of ways. Please see https://help.ubuntu.com/community/Installation for documentation. Problems during install? See https://wiki.ubuntu.com/CommonProblemsInstall and https://wiki.ubuntu.com/DapperReleaseNotes/UbiquityKnownIssues - Don't want to use a CD? Try http://tinyurl.com/3exghs - See also !automate
[08:39] <mikess> ,,d/loading at the mo
[08:39] <slytherin> jussi01: no, I just want to run live cd.
[08:40] <jussi01> slytherin: oh... well look at that last link - it may help...
[08:40] <jussi01> !info alsa
[08:40] <slytherin> jussi01: i can start alternate cd installer with iso. I was wondering if same is possible with live cd
[08:40] <ubotu> Package alsa does not exist in hardy
[08:40] <jussi01> slytherin: no idea
[08:59] <Jeeves_> Anyone here using firefox 3 in Hardy?
[09:12] <bazhang> is it in the repos?
[09:15] <Tomcat_> !info firefox
[09:15] <ubotu> firefox: lightweight web browser based on Mozilla. In component main, is optional. Version <IP_ADDRESS>+2nobinonly-0ubuntu2 (hardy), package size 8968 kB, installed size 26024 kB
[09:15] <Tomcat_> Nope. ;)
[09:15] <bazhang> well then no, Jeeves_
[09:16] <bazhang> cheers Tomcat_
[09:18] <avatar_> firefox-3.0 is in the repo's voor gutsy and hardy
[09:19] <Tomcat_> !info firefox-3.0
[09:19] <ubotu> firefox-3.0: lightweight web browser based on Mozilla (Development Version). In component universe, is optional. Version 3.0~b1+nobinonly-0ubuntu1 (hardy), package size 1180 kB, installed size 3864 kB
[09:19] <Tomcat_> If I had known the package name... ;)
[09:19] <bazhang> ooh nice--will have to try it. thanks avatar_!
[09:26] <avatar_> firefox-3.0 is very fast at rendering
[09:32] <bazhang> nice
[09:34] <Jeeves_> it is in the repo
[09:34] <Jeeves_> firefox-3.0 is the package
[09:34] <bazhang> will install forthwith
[09:35] <nanonyme> hmm, nobin? that's interestesting
[09:45] <Jeeves_> Anyways, the problem with firefox-3.0
[09:45] <Jeeves_> Is that when you have it enabled as the default gnome browser
[09:46] <Jeeves_> And you open a link, the ff-window moves to the workspace you clicked the link on
[09:46] <Jeeves_> And I don't want that
[09:46] <Jeeves_> But I'm not sure who aranges that, Firefox, X, or the windowmanager
[10:08] <slytherin> avatar_: are you using firefox 3 on gutsy?
[10:09] <avatar_> slytherin: at home i do
[10:09] <avatar_> at work i'm running firefox3 on hardy
[10:10] <slytherin> avatar_: do you think hardy is good enough to upgrade? I mean no kernel issues etc. :-)
[10:12] <avatar_> see tpoic
[10:12] <avatar_> see topic
[10:12] <avatar_> Welcome to #ubuntu+1 "Home of the Hardy Heron" and various breakage
[10:14] <slytherin> avatar_: I already saw that. I had used gutsy also from tribe 1 on home pc. I think I will keep my work machine on gutsy only and upgrade home machine on hardy
[10:14] <avatar_> hardy is atm alpha
[10:15] <avatar_> so expect breakage
[11:36]  * Fujitsu sends persia away again.
[11:37] <persia> Hi.  As expected (and indicated in the topic), hardy is broken for me :)  Specifically, epiphany stopped loading due to an issue with not finding the dbus socket in /tmp.  I'm guessing this is related to new dbus security controls, and would appreciate a pointer to where I should hunt towards a solution.
[11:38]  * Fujitsu finds it to work flawlessly :(
[11:38] <Fujitsu> It's so boring, except for Compiz.
[11:39] <persia> Fujitsu: Until this evening, that was my experience as well.
[11:39] <stgraber> Fujitsu: do we have a bug # for the compiz thing ?
[11:39] <Fujitsu> Hobbsee: Do you know of one?
[11:40] <Hobbsee> no
[11:40] <Hobbsee> i've just been speaking to them over irc
[11:40] <Fujitsu> The correct people know of it, right.
[11:40] <Hobbsee> it appears the drivers are giving out crack, then it breaks
[11:41] <Fujitsu> Doesns't it affect multiple drivers?
[11:43]  * persia doesn't suspect the drivers entirely, or the mice wouldn't keep working: it's an interfacing issue.
[11:45] <Fujitsu> persia: Could be hardware pointer, or Compiz not controlling the pointer. I forget exactly how these things interact.
[11:47] <persia> Fujitsu: It would be a hardware pointer.  The point is that if the hardware is still getting the mouse movement information from X, than the driver isn't trapped (although it may be in an unusable state).  A similar issue was previously exposed in the nVidia drivers when the cairo bindings were first deployed in Edgy.
[11:48] <persia> From what could be detected during that time, it appeared that cairo was not trapping errors being reported by the driver (although they were shown in dmesg), and blithely attempting to continue, waiting indefinitely for the response that would never arrive.  I'm not sure it's the same, but I'd suggest that as a possible avenue for investigation.
[14:54] <humbolto> Will there be significant improofments to the Xen environment in hardy?
[14:55] <humbolto> Will Xen in hardy be stable enought to be good for production environments?
[14:55] <humbolto> I know, nobody can tell the future, but is there actually an intention, a plan, a blueprint, a release goal to achieve this?
[15:23] <h3sp4wn> humbolto: I don't think ubuntu is bothered about Xen (The only blueprint remotely related is to do with kvm)
[15:23] <h3sp4wn> But you can now have an opensolaris dom0 so all is fine - and whatever domU's
[15:25] <rhalff> h3sp4wn, you know where the real source tree of linux-image-2.6.22-14-xen is hanging out ?
[15:25] <h3sp4wn> rhalff: Is it not just a patch against the normal ubuntu kernel sources ?
[15:26] <h3sp4wn> rhalff: Did you check the git trees ?
[15:26] <rhalff> h3sp4wn, I've tried apt-get source linux-image-2.6.22-14-xen, which just gives me the normal source
[15:26] <rhalff> I didn't check the git trees
[15:26] <h3sp4wn> http://kernel.ubuntu.com/git?p=zul/ubuntu-hardy-xen.git;a=summary
[15:27] <h3sp4wn> But that is for 2.6.24 but linux-image-2.6.22-14-xen is not the hardy kernel anyway
[15:27] <rhalff> I have to apply this patch https://bugzilla.redhat.com/attachment.cgi?id=209141
[15:27] <avatar_> xen is stable enough for an production environment
[15:28] <h3sp4wn> But which production enviroment ? Most I have worked in would not dream of Ubuntu on a server
[15:29] <avatar_> we are running Ubuntu on 100+ servers
[15:29] <humbolto> h3sp4wn: what would you recommend as a xen dom0?
[15:29]  * rhalff :-o
[15:29] <avatar_> mostly 6.06 LTS. Few feisty, few gutsy
[15:30] <h3sp4wn> humbolto: Solaris Express
[15:30] <avatar_> we are handling mail a few 1000 domains happily on ubuntu/exim4
[15:30] <h3sp4wn> avatar_: Is your billing database on ubuntu ?
[15:32] <humbolto> I just read this on the ubuntu kernel mailing list: ... in Hardy, as Xen will become first class, being maintained by the server team (with special help from the kernel team to ensure it is well maintained).
[15:32] <h3sp4wn> humbolto: first class by whose standards though
[15:32] <humbolto> h3sp4wn: Any Linux distro as xen dom0?
[15:33] <h3sp4wn> humbolto: Probably I would use RHEL or CentOS if I had to choose
[15:34] <humbolto> h3sp4wn: was thinking about that too.
[15:34] <humbolto> h3sp4wn: have very little solaris knowledge.
[15:34] <avatar_> h3sp4wn: billing is done in an DOS application :)
[15:34] <h3sp4wn> humbolto: But you shouldn't be running anything from the dom0 anyway (except you get zfs)
[15:35] <humbolto> h3sp4wn: true (and true)
[15:36] <avatar_> Ubuntu 6.06 is stable and ready for running production on servers
[15:36] <h3sp4wn> avatar_: If you can get them with the hardware support
[15:36] <avatar_> h3sp4wn: buy sun
[15:36] <h3sp4wn> avatar_: To run ubuntu ? No way
[15:37] <avatar_> h3sp4wn: thats what we do
[15:37] <avatar_> sun x2100/x2200/4100/4200
[15:37] <h3sp4wn> avatar_: Why not Solaris ?
[15:37] <avatar_> why running such an ugly OS as solaris
[15:37] <avatar_> which is not free
[15:38] <h3sp4wn> It is free as in beer and its free as in supported with Sun Hardware (to get the patches)
[15:38] <avatar_> no competent packagemanagement
[15:38] <h3sp4wn> Ah so you cannot make sysv packages ?
[15:38] <avatar_> Sun does support Ubuntu on theire servers
[15:38] <h3sp4wn> Will they send an engineer to debug Ubuntu to you within 4 hours ?
[15:39] <avatar_> i don't want to spend time on making my own packages when i ca use tons of packages from ubuntu repo's
[15:39] <avatar_> if you have the right support contract yes
[15:39] <avatar_> for ubuntu support you would need canonical
[15:40] <h3sp4wn> And they have enough people ?
[15:40] <avatar_> canonical? i suppose yes
[15:41] <h3sp4wn> I thought it was a very tiny company
[15:42] <avatar_> we don't use commercial support from canonical
[15:42] <avatar_> only hardware support from sun
[15:44] <h3sp4wn> Making sysv packages is more difficult than debian ones. But upstart is a complete joke compared to SMF - Solaris has had containers / Fair Scheduler - has Zfs, will be supported for as long as you want (and will pay for), Any scripts if you don't use GNU stuff will port between either. I think the extra hassle to use Solaris is well worth it
[15:45] <h3sp4wn> And there will be Indiana soon
[15:45] <h3sp4wn> (Ubuntu ripoff with Solaris kernel)
[16:01] <xst> Has the Hardy Alpha 1 release xorg 7.3?
[16:03] <pvandewyngaerde> X.Org X Server 1.4.0
[16:03] <kbrooks> h3sp4wn, offtopic!
[16:04] <al-_-Gir> when the next release of ubuntu will be released ?
[16:07] <jorgp2> sometime around April I think
[16:07] <h3sp4wn> kbrooks: It did start off on topic - upstart does suck though compared to what part of what it is supposed to be imitating
[16:08] <al-_-Gir> and kubuntu default desktop will be kde 4 ?
[16:13] <kbrooks> al-_-Gir: not guaranteed
[16:16] <xst> pvandewyngaerde: Does X server 1.4.0 imply xorg7.3?
[16:20] <al-_-Gir> kbrooks , so no one know yet ?
[16:20] <kbrooks> al-_-Gir, it depends on when kde 4 is out
[16:22] <al-_-Gir> aa ok hop soon :)
[16:22] <al-_-Gir> hope*
[16:23] <pvandewyngaerde> al-_-Gir:    next ubuntu/kubuntu is LTS,  no kde4 as default
[16:23] <pvandewyngaerde> kde 4.0 will be released 11 januari
[16:23] <pvandewyngaerde> tomorrow RC2 if i remember
[16:24] <al-_-Gir> so waht if its LTS , why lts can have kde4 ?
[16:24] <pvandewyngaerde> xst:  The current stable release is 1.4.0, released as part of X11R7.3
[16:25] <pvandewyngaerde> because Long term support you dont give on something that is completely new
[16:25] <pvandewyngaerde> it will be avalailable as optional packages
[16:26] <mrtimdog> What's the average (new install) footprint size, roughly? I'm just creating a new hardy partition...
[16:26] <pvandewyngaerde> al-_-Gir:  im currently using kde4, really not for end users or long term support
[16:26] <al-_-Gir> i dont understand even why people need long term ...
[16:26] <al-_-Gir> what is so cool to use old release . . .
[16:27] <pvandewyngaerde> for server security updates it is important
[16:27] <pvandewyngaerde> and production systems
[16:28] <al-_-Gir> lts is 3 years desktop and 5 server right ?
[16:29] <avatar_> right
[16:34] <mikkael> there is a section in synaptic showing the local/outdated packages. what are firefox, thunderbird and several other essential stuff doing there ?
[16:54] <BUGabundo> hy there!
[16:55] <BUGabundo> where's the link for the build queue?
[16:55] <BUGabundo> I can't use kmail until kdebase-kio-plugins is build
[16:57] <BUGabundo> sorry about that. another crash from pidgin. something to do with sound and GStreamer-CRITICAL
[17:03] <BUGabundo> I guess this anwsers my own question: https://edge.launchpad.net/ubuntu/+builds
[17:05] <rhalff> ay cool, hardy works with the 3ware 9550SX if I run the 2.16.9-4 kernel
[17:05] <rhalff> (xen)
[17:15] <BUGabundo> can I simply force the old version o Kmail?
[17:16] <BUGabundo> its better a version conflict then no version at all
[17:32] <Richie> Hi, after about 30 mins of my laptop being on, the sound will stop working. When i go System > Preferences > Sound and clikc test i get the error "audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! gconfaudiosink profile=chat: Internal data flow error." The only way i can fix is restarting the laptop. Is there anyway i can stop this from happening?
[17:32] <Richie> or a quicker way to fix it rather than restarting my laptop
[17:49]  * TuX_Claudiu say haello
[17:54] <LimCore> kipin package is damn old in ubuntu
[17:54] <LimCore> how abut packing a recent version
[18:16] <turbotorben> hey, i'm having a wierd bug using hardy: when i df -h it says i've got 4,3gb in use, but i've got only 1.7gb used on the filesystem (du -h tells me the right usage)
[18:17] <void^> are you sure? "du -h" is in use by files, doesn't include filesystem metadata/reserved blocks
[18:19] <turbotorben> void^, i've had over 2gb free before a reboot and now my disc "seems to be" full
[18:19] <void^> fsck it
[18:20] <turbotorben> done
[18:20] <turbotorben> still the same
[18:20] <pvandewyngaerde> filelight /        and check where your space went
[18:21] <void^> fsck -f it, and umount first ;)
[18:21] <turbotorben> umount? it's my root partition?
[18:22] <void^> switch to a livecd
[18:22] <turbotorben> :/
[18:22] <turbotorben> okay
[18:23] <turbotorben> can't i tell fsck to check it on reboot?
[18:23] <Pici> sudo touch /forcefsck
[18:24] <turbotorben> great, thx
[18:24] <turbotorben> brb
[18:31] <turbotorben> thanks, it's fixed
[18:33] <turbotorben> now i've got about 3gb free disk space. is that enough to compile a 2.6.24 kernel?
[18:33] <void^> yes
[18:34] <turbotorben> great thanks. do i have to undo that touch /checkfsck thing?
[18:34] <void^> it should have removed it, i think? if not, rm it.
[18:35] <turbotorben> ok
[18:38] <void^> uh oh.. it seems i will be doing some fsck'ing myself..
[18:39] <turbotorben> good luck then
[18:44] <void^> internal disk went completely dead while transfering files from an usb disk. lovely. :)
[18:45] <turbotorben> what is to be blamed? hardy or that disc?
[18:46] <void^> i don't know, works fine after a reboot but i have no debug information (things like dmesg didn't work anymore..)
[18:54] <rico> why would it be an inappropriate question to ask about the Hardy repositories?
[19:31] <destroyer> hey all... i'm runnin xubuntu 8.04, but this issue happens for me in 7.10 as well... just wondered if anyone could help me figure out why my cursor size/theme is ignored completely by gtk apps (including xfce) and only displayed correctly over non-gtk apps such as firefox and amarok and such. anyone have any ideas? thanks
[19:35] <destroyer> it's not xfce because this happens for me in gnome as well.. the only common denominators are *buntu and my hardware (specifically nvidia).. only thing i can think of is it's an nvidia thing
[19:35] <holmss> I have shutdown.sh file (shutdown -h now), how to make a schrout to this file and what kind of permissions i need to shut down computer without any confirmation?
[19:36] <h3sp4wn> destroyer: firefox uses gtk
[19:36] <destroyer> hmm, well i do have a firefox theme installed which might make a difference
[19:36] <h3sp4wn> destroyer: How are you setting the theme ?
[19:36] <crdlb> h3sp4wn: not really :)
[19:36] <crdlb> it emulates gtk
[19:36] <h3sp4wn> destroyer: .gtk-2.0rc (or whatever its name is you know the one)
[19:37] <destroyer> i've tried using Xfce 4 mouse settings and i've also tried gcursor
[19:37] <h3sp4wn> crdlb: about:buildconfig implies otherwise
[19:37] <destroyer> i can see that it works because my changes reflect over the non-gtk apps
[19:37] <crdlb> h3sp4wn: it uses GDK, but not GTK
[19:38] <destroyer> specifically firefox and amarok and i assume other qt and non-gtk apps display correctly as well
[19:38] <h3sp4wn> crdlb: Why does it need - libgtk2.0-dev to build then ?
[19:39] <crdlb> h3sp4wn: because GDK is part of gtk, and it does draw sample widgets with gtk that it copies
[19:39] <destroyer> but since my xserver is 2699x1968, the cursor size is directly proportional to my xserver resolution, so it's HUGE!!!
[19:40] <h3sp4wn> crdlb: So it needs gtk (a part of)
[19:40] <crdlb> but it's not a true gtk app
[19:40] <destroyer> you're both right... but either way, it doesn't behave like a normal gtk app
[19:40] <crdlb> exactly :)
[19:41] <destroyer> also, this has nothing to do with my weird offset twinview crazy-sized xserver, since it was an issue before i added a dual monitor
[19:41] <destroyer> it's just an issue now.. since before i didn't mind the default cursors
[19:42] <destroyer> must be my nvidia driver...
[19:42] <h3sp4wn> destroyer: Ah did you disable the hardware cursor ?
[19:43] <destroyer> option "SWCursor"?
[19:43] <h3sp4wn> Option "HWCursor" "0"
[19:44] <destroyer> ah k... what section should i add that under?
[19:44] <h3sp4wn> Where the rest of your nvidia options are
[19:44] <destroyer> alright thanks... i'll brb after i add this and restart x
[19:56] <destroyer> hmm... well i tried a ton of variations, even putting the option in almost every xorg.conf section... nothing made a difference.. =(
[22:01] <mikes1> I have no sound ,,A 200 Toshiba ,IH7 intel high definition sound?
[22:01] <cypherdelic> Watch my new great Background, composed of images from gnome,ubuntu and compiz(beryl) - http://img405.imageshack.us/my.php?image=maniacdebiankl3.jpg - Copyright reversed. Feel free to ask me for different resolutions or the xcf
[22:02] <mikes1> kmix has master and pcm but no way of turning them on?
[22:02] <cypherdelic> Tell me if you like, also different colors available.
[22:26] <ompaul> what kernel is currently in Hardy?
[22:29] <h3sp4wn> 24-1
[22:29] <h3sp4wn> !info linux-image-2.6.24-1 hardy
[22:29] <ubotu> Package linux-image-2.6.24-1 does not exist in hardy
[22:29] <h3sp4wn> !info linux-image-2.6.24-1-686 hardy
[22:29] <ubotu> Package linux-image-2.6.24-1-686 does not exist in hardy
[22:29] <h3sp4wn> You get the idea ^^ my laptop is off atm (and it has the hardy kernel)
[22:31] <ompaul> thanks
[22:31] <ompaul> !info linux-image hardy
[22:31] <ubotu> linux-image: Generic Linux kernel image.. In component main, is optional. Version <IP_ADDRESS>.21 (hardy), package size 24 kB, installed size 52 kB
[22:32] <h3sp4wn> I don't think that has been updated yet (Last time I checked the restricted modules was not yet there)
[22:32] <ompaul> maybe I don't want them ;-)
[22:32] <h3sp4wn> ompaul: No but afaik linux-image (metapackage) is not updated until both exist
[22:33] <ompaul> ack
[22:37] <h3sp4wn> !info linux-image-2.6.24-1-generic
[22:37] <ubotu> linux-image-2.6.24-1-generic: Linux kernel image for version 2.6.24 on x86/x86_64. In component main, is optional. Version 2.6.24-1.2 (hardy), package size 19272 kB, installed size 66196 kB
[22:46] <ompaul> h3sp4wn, thanks
[22:46] <Jordan_U> How likely is it that PulseAudio will be used by default in Hardy?
[22:53] <h3sp4wn> Jordan_U: I would say 100% as its enabled by default now
[22:54] <h3sp4wn> Jordan_U: /usr/bin/esd is a wrapper (or it might be in sbin I forget)
[22:54] <hit_> any ideas why gnome just freezes randomly? music keeps playing and i can hear msn sounds but screen freezes
[22:55] <h3sp4wn> hit_: Non free drivers ? Its pretty stable for me here (other than trackerd is not doing anything useful)
[22:55] <hit> not non-free
[22:56] <h3sp4wn> e.g ?
[22:56] <hit> radeon
[22:56] <h3sp4wn> On what card ?
[22:56] <hit> 9550SE
[22:57] <hit> ah no just ati drivers atm
[22:57] <h3sp4wn> r300 is still officially experimental afaik
[22:57] <hit>         Driver          "ati"
[22:57] <h3sp4wn> ati and radeon are the same driver these days
[22:57] <hit> @ xorg.conf
[22:57] <hit> ok..
[22:58] <hit> just got updates for xorg and stuff and hoped that it'll be fixed but nothing
[22:59] <Jordan_U> h3sp4wn, I thought so, I havn't had a chance ( or any HD space :) to install Hardy yet. Thanks
[23:00] <h3sp4wn> hit: So install the dbg packages and try to get a backtrace
[23:00] <h3sp4wn> easier if you have a null modem (or serial cable you can make one from)
[23:01] <Jordan_U> It's great about Linux that when one distro comes out with a really great feature ( in this case Fedora ) most other large distro's also include it by their next version
[23:01] <hit> h3sp4wn, dbg?
[23:01] <h3sp4wn> !info xserver-xorg-video-ati-dbg
[23:01] <ubotu> xserver-xorg-video-ati-dbg: X.Org X server -- ATI display driver (debugging symbols). In component main, is extra. Version 1:6.7.196-2 (hardy), package size 1715 kB, installed size 3528 kB
[23:01] <hit> ah ok
[23:01] <hit> thx
[23:01] <h3sp4wn> There will be a page on the wiki explaining more about how to do it
[23:02] <hit> btw i don't know if it's related to xorg
[23:02] <hit> i think so
[23:02] <h3sp4wn> hit: You have to start somewhere - or you could try kde or xfce for a bit
[23:02] <hit> h3sp4wn, ok
[23:06] <mikess> Hardy is going ok for such early stages
[23:06] <mikess> just no sound as yet
[23:08] <hit> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/108527
[23:08] <ubotu> Launchpad bug 108527 in xserver-xorg-video-ati "X freezes when compiz is enabled on ATI cards" [High,Confirmed]
[23:08] <hit> something for me i quess
[23:10] <h3sp4wn> Probably - I haven't used compiz for long enough to know if that affects me
[23:19] <mikess> !alsa
[23:19] <ubotu> If you're having problems with sound, first ensure ALSA is selected, by double clicking on the volume control, then File -> Change Device (ALSA Mixer). If that fails, see https://help.ubuntu.com/community/Sound - https://help.ubuntu.com/community/SoundTroubleshooting - http://alsa.opensrc.org/index.php?page=DmixPlugin - For playing audio files, see !Players and !MP3
[23:19] <mikess> !alsaconf
[23:19] <ubotu> Sorry, I don't know anything about alsaconf - try searching on http://ubotu.ubuntu-nl.org/factoids.cgi
[23:21] <Jordan_U> mikess, Those instructions may or may not work with pulseaudio, do applications at least "think" they can output sound, for instance can you run "aplay < /dev/random" without errors?
[23:22] <mikess> Jordan_U, I have no sound on a Tishiba A200
[23:22] <mikess> hda IH7 high definition sound
[23:23] <mikess> It can see it,,pcm and master is in kmix
[23:23] <mikess> Unable to turn them on
[23:23] <Jordan_U> mikess, Can you try running "aplay < /dev/urandom" and pastebin any errors ?
[23:24] <h3sp4wn> mikess: Are you 100% certain they are just not muted ?
[23:24] <mikess> ok will go and boot the lapy 1min  :)
[23:24] <Jordan_U> mikess, I am not sure if kmix is seeing the real hardware ( interacting with alsa directly ) or if it is just seeing pulseaudio mimicking real hardware for alsa compatability ( like fedora does with alsamixer )
[23:27] <mikelapy> ok back :)
[23:27] <mikelapy> What was that command please?
[23:28] <Jordan_U> mikelapy, "aplay < /dev/urandom"
[23:28] <mikelapy> Playing raw data 'stdin' : Unsigned 8 bit, Rate 8000 Hz, Mono
[23:29] <LiMaO> mikess: i can help you, just a sec
[23:29] <mikelapy> awsm :)
[23:29] <LiMaO> mikess: https://help.ubuntu.com/community/HdaIntelSoundHowto
[23:30] <h3sp4wn> mikelapy: Really don't do ^^
[23:30] <LiMaO> mikelapy, mikess, are you there?
[23:30] <mikelapy> yes
[23:30] <LiMaO> mikelapy: do NOT compile anything from source
[23:30] <LiMaO> mikelapy: but read one of the last lines
[23:30] <mikelapy> I have latest alsa installed,,,.15
[23:30] <mikelapy> ok
[23:31] <LiMaO> mikelapy: actually you should add the line 'model=3stack'
[23:31] <LiMaO> to the file /etc/modprobe.d/sound
[23:31] <mikelapy> ok
[23:32] <h3sp4wn> LiMaO: Are you certain that this is not already fixed in the hardy kernel ? 24-1
[23:32] <LiMaO> h3sp4wn: may already be.. but he's already having the problem.. trying this won't hurt =)
[23:33] <h3sp4wn> LiMaO: But the chances are he is still using 22-*
[23:34] <LiMaO> well, actually i didn't have this problem at all using ubuntu, even hardy.. only had this problem with debian.. 2.6.18.. but adding the 'model=3stack' line to the file mentioned above fixed everything and i got sound working
[23:34] <Jordan_U> mikelapy, What is the output of "uname -r" ?
[23:35] <mikelapy> nothing  hmm
[23:35] <mikelapy> ok added ,,,,3stack ,,
[23:35] <mikelapy> reboot?
[23:35] <LiMaO> yes
[23:36] <LiMaO> did you add it on the same line as 'options' ?
[23:36] <mikelapy> yes
[23:36] <LiMaO> reboot =)
[23:36] <LiMaO> also cross your fingers
[23:36] <LiMaO> this is such an important step hehe
[23:36] <mikelapy> 2.6.22-14-generic
[23:36] <mikelapy> ]
[23:36] <mikelapy> brb
[23:40] <mikelapy> ok still no sound
[23:41] <Jordan_U> mikelapy, You didn't cross your fingers did you?
[23:41] <Jordan_U> mikelapy, We can't help you if you don't follow our instructions ;)
[23:41] <mikelapy> hehe
[23:46] <Jordan_U> mikelapy, I'm looking for a way to be sure that the channels in alsa are not simply muted or too low / how to be sure that alsamixer / kmix are actually controlling alsa
[23:46] <mikelapy> ok
[23:48] <Jordan_U> mikelapy, Does kmix look like it's showing the same channels it was in previous Ubuntu versions on the same hardware?
[23:51] <mikelapy> yes
[23:51] <mikelapy> sound did not work in fiesty
[23:51] <mikelapy> needed ,,,.15 alsa
[23:51] <mikelapy> Sidux works fine
[23:52] <h3sp4wn> mikelapy: You could install a sidux kernel if you wanted
[23:53] <mikelapy> h3sp4wn, I was thinking that ,I have sidux installed as well ,I really want to keep kubuntu original :)
[23:53] <h3sp4wn> mikelapy: or just - sudo aptitude install linux-image-2.6.24-1-generic
[23:53] <h3sp4wn> but then you have to deal with any graphics card drivers you have to install
[23:54] <h3sp4wn> or wifi drivers
[23:54] <mikelapy> ok
[23:54] <h3sp4wn> mikelapy: alternatively you could do
[23:54] <mikelapy> mmm
[23:55] <h3sp4wn> sudo aptitude install alsa-source module-assistant && m-a prepare && m-a a-i alsa (but that will not work with 2.6.24-1 iirc)
[23:59] <thompa> howdy, ive upgraded to kernel 2.6.24, wireless intel 4965 is there but nothing in nwm
[23:59] <Jordan_U> h3sp4wn, Does that mean that eventually an update will likely fix his problem?


[08:15] <duflu> tsdgeos: Is the shell's text rendering ubuntu-ui-toolkit or regular Qt stuff?
[08:17] <tsdgeos> duflu: i wouldn't say the ubuntu-ui-toolkit has any own text rendering
[08:17] <tsdgeos> i hope so at least :D
[08:18] <duflu> tsdgeos: Lemme rephrase that: Who calls into FreeType?
[08:18] <tsdgeos> Qt if anyone
[08:18] <tsdgeos> i have the word harbuff inside my mind
[08:18] <tsdgeos> not sure if that replaces freetype or not
[08:19] <duflu> tsdgeos: HarfBuzz?
[08:20] <tsdgeos> duflu: that
[08:21] <duflu> Yay, another fork I didn't know existed
[08:22] <tsdgeos> it's quite old
[08:23] <tsdgeos> afaik gtk is using this too
[08:24] <duflu> Yeah apparently FreeType links to it
[08:28] <tsdgeos> so as said, it may not be "the same thing" as freetype
[08:31] <duflu> tsdgeos: That's OK. My question was who calls the relevant libraries. Not what the libraries are
[14:03] <Saviq> alf_, so I've been thinking, if we manage to get jenkins-job-builder and/or DSL working, no point in having the scripts in the repo separately, the might as well be baked into the jobs if the job definitions are stored in bzr
[14:04] <Saviq> alf_, so I'm gonna look into that instead of putting them into bzr
[14:05] <alf_> Saviq: ok, although one thing that concerns me is that jobs will need to have different defaults depending on project, how will we deal with this?
[14:10] <Saviq> alf_, I'm sure there are ways
[14:10] <Saviq> alf_, like a config file or global env vars
[14:12] <Saviq> alf_, it seems like jenkins-job-builder doesn't even need to run on the jenkins nodes necessarily, as all it does is upload xml via the API
[14:13] <Saviq> alf_, so assuming we can make stuff smart, you'll just set up some config vars and let JJB do its thing
[16:04] <QUESTION> ?
[16:05] <ogra_> 42
[16:05] <QUESTION> what's my nickname?