=== salem_ is now known as _salem === Mirv_ is now known as Mirv === shiznix_ is now known as Guest17846 === mfisch is now known as Guest95146 === zoktar_ is now known as zoktar === tvoss|errands is now known as tvoss === duflu_ is now known as duflu === popey_ is now known as popey [07:03] veebers, ping [07:14] Saviq: morning [07:14] Saviq: hey, I did a dist-upgrade and autoremove and now my GLX extension doesn't work any more. [07:15] do you know which packages I need (or which I must remove) in order to get it back on an an intel-chip? [07:19] mzanetti, should be xserver-xorg-core [07:19] mzanetti, that's what "dpkg -S /usr/lib/xorg/modules/extensions/libglx.so" is telling me here on my all-intel laptop [07:19] MacSlow: no... I'm only missing the GLX extension, not the whole x server [07:20] MacSlow: yeah... I have this lib [07:20] still, glxinfo says this: Xlib: extension "GLX" missing on display ":1". [07:20] the same does any qml2 app [07:21] weird thing is, I think the glx module tries to load the nvidia chip even though it should use the intel one [07:21] and all howtos regarding bumblebee or vga_switcheroo just don't work [07:21] mzanetti, Optimus-based system? [07:21] MacSlow: no clue what optimus is, but yeah, have a nvidia and a intel chip [07:21] mzanetti, there's an update-alternatives for this I think [07:22] mzanetti, OTOH my Skype fails no finding libGL.so.1 since yesterday, too [07:24] Saviq, since yesterday apt wanted to remove unity and ubuntu-desktop... which I managed to avoid... but now libunityshell.so keeps segfaulting [07:25] mzanetti, $ update-alternatives --list x86_64-linux-gnu_gl_conf ? [07:25] Saviq: [07:25] /usr/lib/nvidia-304-updates/ld.so.conf [07:25] /usr/lib/x86_64-linux-gnu/mesa/ld.so.conf [07:25] Saviq: I just switched it over to the mesa one [07:25] * mzanetti reboots [07:25] brb [07:26] MacSlow, libunityshell.so is the unity compiz plugin/ [07:26] ? [07:26] * Saviq tries to upgrade [07:26] Saviq, I know [07:26] MacSlow, that was a question, not a statement ;) [07:27] Saviq, just saying... since yesterday some odd things happen with regards to the package-db :) [07:27] MacSlow, apt-cache policy unity? says 7.0.1+13.10.20130703-0ubuntu1 [07:27] MacSlow, nothing weird here [07:27] Saviq: Please help reviewing? https://code.launchpad.net/~paulliu/unity8/activate3/+merge/173071 [07:28] paulliu, yes, I saw it, it's in my queue if no one else gets onto it [07:28] Saviq: ok.. thanks. [07:28] paulliu, although if you can get someone else to review, probably gonna be quicker [07:28] Saviq: ok. [07:29] nope :/ [07:29] funny thing is, starting unity8 I get Xlib: extension "NV-GLX" missing on display ":1". [07:29] now that I switched it FROM nvidia TO mesa [07:34] to any autopilot-experts... I keep getting http://pastebin.ubuntu.com/5845923 [07:38] mzanetti, ldconfig -p | grep libGL? [07:38] http://paste.kde.org/789530 [07:38] mzanetti, you might need to `sudo ldconfig` to update the ld database [07:38] Saviq: ^ [07:38] mzanetti, yeah, still finds the nvidia one [07:39] mzanetti, you want to switch i386_, too [07:39] Saviq: right....I did the sudo ldconfig and its gone now [07:39] Saviq: huh? i386? [07:39] mzanetti, libGL.so (libc6) => /usr/lib32/nvidia-304-updates/libGL.so [07:39] Saviq: ah... that line is gone after the sudo ldconfig [07:40] mzanetti, gone completely? [07:40] http://paste.kde.org/789536 [07:40] mzanetti, or just linking to the mesa ones? [07:40] Saviq: gone completely [07:40] ok yeah, that looks good if you don't want i386 [07:40] mzanetti, should be good now, I'd sa [07:40] y [07:40] ok... bbiab [07:46] MacSlow: Pong, re: your paste bin it looks like you're missing: python-ubuntu-platform-api, [07:47] MacSlow: although that gobject error is a new one for me at this stage [07:47] veebers the odd thing is... I don't have that package at all... and a fresh checkout of unity8 does work with all autopilot-tests... so python-ubuntu-platform-api is not needed apparently [07:47] MacSlow: odd [07:48] Saviq: better... Now all desktop effects like wobbly windows etc work again, but when they are enabled, the panels and context menus stay black :/ [07:48] veebers, just when I use self.touch = Touch.create() in my own code I start getting this failure [07:48] mzanetti, man, what did you do [07:48] mzanetti, to get to that state? :) [07:49] Saviq: I had this state already when I initially installed ubuntu [07:49] veebers, and then all other autopilot-test also keep failing [07:49] MacSlow: but the unity8 tests run fine? [07:49] mzanetti, ah, do you have optimus enabled, then? [07:49] Saviq: and I just used XRender in Sept and Oct [07:49] didn't need QtQuick 2.0 back then [07:49] mzanetti, i.e. do you use the nVidia chip or the Intel one? [07:49] Saviq: at some point xrender usage became crashy and I tried openGL. worked fine as of then [07:49] Saviq: I want only the intel one [07:50] veebers, not after I ran my own test... even just selecting one of the other unity8 autopilot-tests has them failing then [07:50] mzanetti, you need to enable Optimus in the BIOS then [07:50] Saviq: whats a bios? :P [07:50] mzanetti, ;) [07:50] no need for that legacy shit [07:50] mzanetti, what do you call it now? ;) [07:50] mzanetti, system setup? [07:51] Saviq: I have an EFI loader. thats it [07:51] veebers, I'm wondering where autopilot maybe writes something to a cache-file in the unity8 directory that could cause this... because a fresh checkout of unity8 makes the tests there work again [07:51] MacSlow: This is on your desktop? [07:51] mzanetti, that's different [07:51] veebers, desktop yes [07:51] mzanetti, I mean the thing where you set up your hardware [07:51] F2 or something [07:51] Saviq: don't have that [07:51] its a mac [07:51] mzanetti, uh, right [07:51] MacSlow: no, autopilot shouldn't write any cache file like that [07:52] mzanetti, and you do have two GPUs there? [07:52] Saviq: yep [07:52] MacSlow: you're on saucy and you've updated recently? (just trying to narrow down possibilities) [07:52] mzanetti, well, it's probably enabled then :) [07:52] veebers, yes... on a saucy system... [07:52] Saviq: in Archlinux vga_switcheroo somewhat worked to power down the nvidia one [07:52] Saviq: never managed to get that working in ubuntu [07:53] veebers, pulling updates (in the hope to fix this by updating packages, since I'm not sure about the cause of the failure) messed up my unity on my main machine... still got the laptpo [07:53] Saviq: oh... and our build -s miserably fails if you don't have qt libs installed [07:53] so does just ./build [07:54] mzanetti, suggests we're missing deps [07:54] mzanetti, but then we'd know [07:54] mzanetti, as it wouldn't build on jenkins [07:54] yeah... well. let me check more exactly [07:54] mzanetti, ./build -c [07:55] Saviq: ah... damn it... [07:55] Saviq: yeah... ofc [07:55] mzanetti, it only installs the build deps if builddir/unity8-build-deps*deb is older than debian/control [07:55] or doesn't exist [07:56] * mzanetti wonders why ./build wants to install nvidia-current-updates [07:58] mzanetti, libgl1-mesa-dev[!armhf] | libgl-dev[!armhf], probably [07:58] mzanetti, but then you should be able to remove all nvidia things [07:58] veebers, I'll have to dig into this myself it seems. [07:58] mzanetti, if you don't want to use it [07:59] Saviq: re what I did to get to this state: I got conflicts because I had some mesa lib from the mir ppa around. [07:59] mzanetti, right [07:59] MacSlow: I'm just doing an update to see if I can reproduce [07:59] Saviq: installing the released version of that package removed my whole kde [07:59] mzanetti, lol [07:59] Saviq: I did that, then dist-upgraded as I had like 500 outdated packages [07:59] Saviq: and then reinstalled kde [08:03] Saviq: FWIW, not only kde... it removed everything with a dependy to X [08:03] dependency [08:04] mzanetti, I'd probably just rinse & reinstall [08:04] that reminds me, I wanted to enable EFI on my laptop [08:04] Saviq: why, you water cooling your laptop now? [08:05] greyback, no, I just switched away from nVidia ;P [08:05] greyback, as it was the GPU that was overheating [08:05] greyback, still need to call a Dell technician in to come and fix it [08:05] Saviq: ah really? Boo [08:05] greyback, when did you last do that with your Mac? [08:05] Saviq: I haven't needed to, strangely enough [08:06] greyback, you just throw away and buy a new one? [08:06] what, call a technician? [08:06] mzanetti, I can't be bothered, I got 4yrs door-to-door warranty [08:06] mzanetti, not even d-t-d [08:06] mzanetti, next business day someone comes over and fixes it [08:06] I had to replace the main board 4 times at my previous one... He didn't come here to my place, but I could watch him while replacing it in his shop in the city center [08:06] replacing the mobo, CPU< whatnot [08:07] but I opened and repaired my gf's macbook 3 days ago... display was flickering... [08:07] they're beautyful even on the inside :D [08:08] enough... need to get productive.. thanks Saviq for the libgl help [08:08] veebers, it has to be some side-effect with introducing pynotify to the autopilot-tests [08:08] veebers, again... did a fresh checkout and ran the test... all went fine... [08:08] mzanetti, ;) [08:09] mzanetti, it's Friday, it's not like you gonna do anything today anyway! :D [08:09] MacSlow: Interesting, the examples I linked you (that I put in the wrong place) worked fine with pynotify [08:09] veebers, I added the smallest bit of code to trigger a notification from it, it fails... [08:09] * Saviq wonders if I can use the efi partition for /boot [08:09] veebers, it's a combination of pynotify and the Touch class... [08:10] Saviq: think EFI has to be FAT{,32} [08:10] greyback, yeah, problem? [08:10] veebers, if I don't to self.touch = Touch.create() it doesn't happen [08:10] greyback, it's not like /boot is anything advanced [08:10] Saviq: no I suppose not [08:10] grub can read it [08:13] veebers, that... or removing all the pynotify-related code and getting rid of the .pyc and re-running test it'll work agian [08:14] MacSlow: can you do something for me, open a terminal and start ipython (or python) and try this: from autopilot.input._uinput import Touch [08:14] then Touch() [08:15] MacSlow: also, are you able to show or pastebin the test file that the error comes from? [08:16] tsdgeos, I like your influence on our test count :D [08:17] :) [08:17] veebers, http://pastebin.ubuntu.com/5845996 http://pastebin.ubuntu.com/5846005 [08:18] pstolowski, I don't like your influence on our coverage, though ;P [08:19] Saviq: mhm. where can I see it? [08:19] pstolowski, http://s-jenkins:8080/job/unity8-autolanding/31/cobertura/ [08:19] pstolowski, that's when activation-and-previews merged [08:20] MacSlow: It's to do with the pynotify module [08:20] pstolowski, hmm we're missing source code, though, for some reason [08:21] pstolowski, but you can `make coverage` locally [08:21] pstolowski, to build the html [08:21] mzanetti, do you have ideas why we're still not seeing source code in our C++ coverage? [08:21] mzanetti, http://s-jenkins:8080/job/unity8-autolanding/36/cobertura/plugins_Unity/genericpreview_h/ [08:22] MacSlow: try this in ipython: from autopilot.input import Mouse, Touch, Pointer <\n> Touch.create() <\n (this works)> import pynotify [08:22] veebers, I need this tough... I would not like to have use DBus directly with python just to fire some notifications [08:22] MacSlow: what's odd is that it seemed to work fine on the device when I was trying it out [08:22] Saviq: yeah... thing is, jenkins gets that from the work dir [08:23] Saviq: so 1st it only works in the qmluitests job [08:23] Saviq: and 2nd, it only works for the last build [08:24] Saviq: only way to improve that would be to modify the jenkins cobertura plugin to copy the work dir to some persistent place [08:24] Cimi, did you have a look at my branch yet? [08:24] Still got barely any idea about the styles. [08:27] Saviq: ok. we'll try to improve it with time. but let's not forget plugins/Unity area didn't have tests at all before that branch :P [08:28] veebers, just tried a very few calls (inside ipython) with plain dbus... that doesn't sefault... [08:28] pstolowski, ;) === Cimi_ is now known as Cimi [08:28] MacSlow: hmm, it seems to be some lowerlevel gobject happening perhaps [08:28] veebers, this is not looking good... in terms of efficency... [08:29] pstolowski, no worries, dednick will have even worse impact with https://jenkins.qa.ubuntu.com/job/unity8-ci/124/cobertura/? ;) [08:29] veebers, I'm not very fluent with plain dbus... even worse if it has to be in python. [08:29] pstolowski, OTOH the Indicators plugin will get under your team jurisdiction soon enough, too :D [08:30] veebers, but I've to go that path as it seems unfortunately [08:31] Saviq: I didn't see that, you're breaking up :P [08:31] lol [08:32] MacSlow: I think there might be a solution to this issue, I'm just having a quick explore [08:32] pstolowski, it's ok, we've moved a lot of the functionality down to QML as compared to lp:indicators-client [08:33] veebers, that would be great, if there's a better/faster workaround... or even fix for it [08:33] or up to QML? [08:34] Cimi, btw, this was your issue with the background color, right https://bugreports.qt-project.org/browse/QTBUG-32238 ? [08:35] Cimi, here's a dirty workaround FYI https://code.launchpad.net/~loic.molinari/ubuntu-ui-toolkit/ubuntu-ui-toolkit-ternary-op-color-fix/+merge/173072 [08:35] veebers, btw... I wonder why pynotify even needs gtk+-2.x at all [08:37] MacSlow: I'm not sure at all. Just a though, I seem to recall that there is a standalone binary that you can use to generate a notification? (just as a stand in for right no, not needing to do raw dbus stuff) [08:37] veebers, you're talking about "notify-send"?! [08:38] MacSlow: that sounds like the one I was thinking of [08:39] veebers, hm... a bit clumsy... but could work... passing hints also works with that... code will look a bit ugly... but sure why not... giving it a try. [08:39] MacSlow: yeah I agree not the nicest, but it should allow you to get tests written now, and once we sort out this issue with pynotify we can swap out the subprocess calls [08:42] veebers, only callbacks (e.g. for interactive or snap-decisions) won't be covered by this [08:45] ooh creepy, my maguro was always displaying just the empty-battery-charging animation... [08:46] but `adb shell` took me straight to Ubuntu running inside :? [08:46] veebers, ok... I just verified that using os.system() with notify-send works [08:48] MacSlow: sweet, although I would probably use: http://docs.python.org/2/library/subprocess.html [08:48] tsdgeos: ping [08:48] smspillaz, hi - bad news - another intolerable regression with window sizes made it into trunk :( [08:48] mzanetti: hi [08:49] MacSlow: it looks like something pynotify is doing with the gi.repository/gobject + static objects [08:49] tsdgeos: did you already create a bug report or submit the patch to gerrit? [08:49] 75% [08:49] why? [08:49] veebers, yeah [08:49] veebers, I'll look into this subprocess call from python then [08:49] tsdgeos: just trying to find a reference for the FIXME in in the comment where I disable the test [08:50] smspillaz, bug #1198000 [08:50] bug 1198000 in Compiz "Regression: r3751 causes unmaxed windows to shrink vertically on each subsequent opening" [High,Triaged] https://launchpad.net/bugs/1198000 [08:50] mzanetti: https://bugreports.qt-project.org/browse/QTBUG-32251 [08:50] tsdgeos: cheers [08:50] MacSlow: cool, I'll fire off an email re: this bug and see if we can get any further with. I need to get going though [08:51] MacSlow: let me know how you get on with the subprocess/notify-send stuff [08:51] veebers, ok... just wanted to let you know... at least we've a way to trigger notifications from the right spot now... [08:51] veebers, I'll see how far I can get with the current examples and moving them over to autopilot [08:51] MacSlow: also, just out of interest, the pynotify stuff will work on the device because the code path it takes doesn't import from the gi.repository stuff [08:52] veebers, perhaps :) [08:52] MacSlow: Ack, Those examples that I put up should be (hopefully) helpful [08:52] veebers, I only know that the stand-alone python-examples work on the device [08:53] veebers, until now I've never seen pynotify crap out like this [08:53] tsdgeos, nice one :) [08:53] mzanetti: the other one you found is https://bugreports.qt-project.org/browse/QTBUG-32258 [08:54] tsdgeos: awesome [08:55] MacSlow: ack, the tests in that branch will check the display outputs of the notifications regardless of how they are generated [08:56] veebers, I'll merge something together... you'll get a summary of the results/branch via eMail by my EOD [08:56] veebers, thanks and have a cool weekend [08:56] MacSlow: awesome [08:58] mzanetti, so if I add indicators_client to http://s-jenkins:8080/job/unity8-ci/124/rebuild/? it should run the two suites? [08:58] Saviq: yep. separated by a space [09:01] let's see :) [09:03] mzanetti, did you see my question about Jenkins not finding the source code in coverage reports? [09:03] Saviq: yep. appears you missed my answer tho :) [09:03] mzanetti, ! [09:03] tsdgeos: FYI: this should be ok now: https://code.launchpad.net/~mzanetti/unity8/launcher-improve-flicking-behavior/+merge/172648 [09:03] [10:22] Saviq: yeah... thing is, jenkins gets that from the work dir [09:04] [10:23] Saviq: so 1st it only works in the qmluitests job [09:04] [10:23] Saviq: and 2nd, it only works for the last build [09:04] [10:24] Saviq: only way to improve that would be to modify the jenkins cobertura plugin to copy the work dir to some persistent place [09:04] mzanetti, :/ [09:04] mzanetti, last build would be fine, since we're most interested in trunk [09:05] Saviq: the bad thing is now that if a new build starts, it discards the old working dir [09:05] mzanetti, but I'm not sure I get the "work dir" issue [09:05] mhm [09:05] how can that ever work, then? [09:06] Saviq: but might be better on the public jenkins as I believe it syncs the work dir there and only updates once a new build is actually finished [09:06] * mzanetti check [09:06] s [09:07] nope.. not there either :/ [09:07] mzanetti, yeah, you would expect it to be in https://jenkins.qa.ubuntu.com/job/unity8-autolanding/lastBuild/cobertura/plugins_Unity/applicationpreview_cpp/ at least [09:08] mzanetti, might it be that we're not really doing anything in the -autolanding jon? [09:08] job [09:08] mzanetti, i.e. the -autolanding doesn't really touch any code [09:08] Saviq: phone... brb === jibel_ is now known as jibel [09:16] mhr3, didrocks, we now have unity-scopes-runner (and all the unity-{lens|scope} things) as part of the touch seed, should we not drop it from the seed and let the recommends take care of it? [09:16] Saviq: re [09:16] Saviq: yeah, good point [09:17] mhr3, didrocks, for unity-scopes-runner the scopes / lenses don't depend on it - they should, right? [09:17] Saviq: mhm... tbh I'm a bit confused why I can't find it at all right now... Each time I asked mmrazik about this he came up with a link where the code was there... but I never find it myself [09:17] Saviq: hum… in fact, some scopes can be installed on the client or server [09:18] maybe better to discuss with mhr3 about it [09:18] didrocks, right [09:18] didrocks, I plan a diff like so to the touch seed http://pastebin.ubuntu.com/5846145/ [09:18] the -runner might need to remain, though [09:19] sec, in a hangout [09:19] Saviq: hah.... its there now: http://s-jenkins:8080/job/unity-phablet-qmluitests-saucy/422/cobertura/tests_mocks_LightDM/Greeter_h/ [09:19] Saviq: the scopes deps on the runner in fact [09:20] mzanetti, yeah, in qmluitests, but not in -ci? [09:20] the python ones [09:20] Saviq: so it should be pulled as needed [09:20] Saviq: yeah... we don't copy the qmluitests work dir to the -ci job [09:20] didrocks, right, the others are not python [09:21] Saviq: the seed diff looks good to me, I'm happy to commit it and generating the touch meta package [09:23] didrocks, https://code.launchpad.net/~saviq/ubuntu-seeds/ubuntu-touch.saucy.clean-unity8/+merge/173162 [09:25] Saviq: the touch image pulls the recommends, right? [09:26] (as those are recommends) [09:28] Saviq: rather than wondering, I'm cheating and trying to regenerate the metapackage using your branch :) [09:28] didrocks, :) [09:29] mzanetti: so the bug about the folded angle was already there, right? not a regression? [09:29] tsdgeos: yeah [09:29] tsdgeos: but until this merge I actually didn't realize its a but in ListView [09:29] s/but/bug/ [09:32] andyrock, hi. How is your testing of Compiz trunk working out ? [09:32] * MCR_ has not seen any new bug reports [09:32] MCR_, good... we need to release compiz 0.9.19 [09:32] *.10 [09:33] yep [09:33] andyrock, we have unfortunately one regression we should not really tolerate [09:33] MCR_, do you have a bug? [09:33] bug #1198000 [09:33] bug 1198000 in Compiz "Regression: r3751 causes unmaxed windows to shrink vertically on each subsequent opening" [High,Triaged] https://launchpad.net/bugs/1198000 [09:35] andyrock, we have several MPs, which have been checked by 4 or more eyes - it would be good to land those... [09:35] MCR_, no please [09:36] it will make my life harder [09:36] andyrock, do you need a PPA to test [09:36] ? [09:36] dednick, "Show password" doesn't seem to work in the new indicators - I get dots all the time [09:36] nic-doffay, can you confirm ↑ when you get to it? [09:36] Fortunately smspillaz was so nice to set them up [09:36] Saviq: it's not that easy to fake though :/ [09:36] MCR_, it's not about that [09:36] (using the seed_base for multiple things) [09:37] Saviq: ah. probably just a bug i introduced changing up the password field [09:37] MCR_, it's about running AutoPilot to check for regression [09:37] andyrock, aha [09:37] andyrock, could you give me an ETA then... ? [09:38] blocking trunk for a long time is not nice for any contributor... [09:38] MCR_, that's why I want to release 0.9.10 [09:38] you "block" 0.9.10 and unblock trunk [09:38] Can I help you ? [09:39] if you want... ;) [09:39] Sure, but I need some instructions [09:39] pete-woods: commented in https://code.launchpad.net/~unity-team/unity8/older-months/+merge/172860 [09:40] or maybe not, my internet is acting funny [09:40] I guess all milestones will have to be changed manually... [09:40] to 0.9.10.2 ? [09:40] dednick, the messaging icon remained blue after I've "used" a missed call entry, that's probably a backend bug? [09:40] Saviq: do you have https://code.launchpad.net/~aacid/unity8/remove28403workarounds/+merge/172608 in your schedule or should i try to trick someone else to review it? [09:40] MCR_, well to be honest I've no idea on how to do it ;) [09:40] MCR_, I'm waiting Sam [09:40] tsdgeos, that's an easy one, harass someone to do it [09:41] Saviq: possibly backend. does it clear it? [09:41] andyrock, I have read some instructions by duflu in the source on how to do it [09:41] dednick, yeah, the message itself is gone [09:41] dednick, but the icon remains blue [09:41] Saviq: and does it clear the blue when you clear all using button at bottom? [09:41] dednick, +1 [09:41] Saviq: probably backend in that case. [09:42] dednick, yeah, it did clear when I replied to a text [09:42] dednick, I mean it cleared the icon [09:44] Saviq: ok [09:45] tsdgeos: I have added some instructions, that hopefully will allow you to try out the fix :) [09:45] tx [09:47] didrocks, Saviq, the scope-runner is for the python scopes atm, so any python scopes should dep on it [09:47] mhr3: yeah, we figured it out and checked, it's fine. Thanks! :) [09:50] pstolowski, paulliu who broke video previews? the image is half-height on the phone [09:53] Saviq: you're testing this branch I presume: https://code.launchpad.net/~paulliu/unity8/activate3/+merge/173071 ? [09:53] pstolowski, no, trunk [09:54] Saviq: hmm, looking. our changes shouldn't take affect then [09:55] pstolowski, ok, will try and pinpoint the revision [09:56] dednick, it worked fine on a freshly flashed manta, didn't work on fresh maguro + your branch - indicators [09:57] Saviq: re broken controls, i'm not sure about that. There's nothing different from the power indicator (ie it uses default page), and the controls seem to work there. [09:57] Saviq: I'll take a look and try see if the commands are getting through [09:57] dednick, yeah I know, investigating now [09:58] dednick, will run your branch against the same setup to see if it affects anything [09:58] * greyback bbiab [10:03] dednick, yeah, it's the sound backend, it's broken bad on the latest image - sound is distorted a lot [10:03] mzanetti, I think I found a bug in the greeter [10:03] mzanetti, I managed to get into typing mode for the Guest user... [10:04] mzanetti, and now there's no greeter at all [10:04] Saviq: hmm... more details please [10:04] mzanetti, manta, I think I dragged the list slightly before tapping on it [10:04] mzanetti, must've went out of "button-mode" [10:05] mzanetti, and it wen't into "password-mode" [10:05] mzanetti, then, when tapped again on the text entry, it unlocked [10:05] mzanetti, and now it doesn't lock back [10:05] * Saviq tries to repro [10:06] Saviq: hmm... seems some LightDM auth issue. Mind reporting to mterry? [10:07] mzanetti, yeah, if only I could reproduce... [10:07] will keep an eye on it [10:07] Saviq, sorting it now. [10:26] Saviq, having the phone's being a pain. [10:26] *the phone's being a pain [10:26] nic-doffay, ? [10:26] Going for a reflash now. === alan_g is now known as alan_g|afk [10:29] Mirv: do you remember me ever filing a bug saying qtgui should links against xcb so dead keys work on qt5? [10:29] i clearly remember it [10:29] but can't find it :-/ [10:33] mzanetti, http://paste.ubuntu.com/5846273/ [10:33] mzanetti, tests seem to pass... [10:33] wondering if it's correct :) [10:34] Cimi: hmm... push stuff to the branch and I'll do a review in a bit [10:34] mzanetti, I think it's missing to rebuffer [10:34] like, I remove items and I should append items on the other side maybe [10:34] Mirv: can you have a look at https://bugs.launchpad.net/ubuntu/+source/qtdoc-opensource-src/+bug/1198131 too ? [10:34] Launchpad bug 1198131 in qtdoc-opensource-src (Ubuntu) "Lots of .qch files missing from qt5-doc" [Undecided,New] [10:35] pete-woods: what provides usermetricsinput ? === alan_g|afk is now known as alan_g [10:35] ah [10:35] can't read [10:36] tsdgeos: ;) [10:38] tsdgeos: yep, I wanted it to be tested on saucy which is about only now possible with the flipping work done https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1163687 [10:38] Launchpad bug 1163687 in Ubuntu UI Toolkit "Impossible to insert any kind of foreign characters with the keyboard" [Critical,Confirmed] [10:38] on saucy device, that is [10:38] Mirv: doesn't even work in my pc [10:38] is that in 5.0.2+dfsg1-7ubuntu1 ? [10:38] tsdgeos: 11981831 is being fixed in all modules [10:38]