[00:42] RAOF, how you looking with compositor for getting to robert_ancell this week? still on track? [00:43] jasoncwarner_: Run into an unexpected snag - the xwayland server is a patch series on top of xserver 1.12 (which is fine, we've got a 1.12 PPA and we'll copy that to quantal next week or so), but the whole xserver tree got reindented between 1.12.0 and 1.12.2 (which we'll use). [00:44] So I'm just fixing that up, *then* I can hand off to robert_ancell :) [00:44] cool, sounds like a plan. [00:44] Thanks, man . [02:57] I would like to help you, I have a laptop with sis chipset video mirage 3672, I installed ubuntu 4.12 and the video was 800x600, I found searching on google one. deb file with the drivers sis 672 for version 4.12, installed and managed to resolution 1280x800, was visually more beautiful I can not run any video or the VLC by opening it gives to log out. Anyone know a solution? [02:59] anybody? [03:00] this channel has 127 people who use ubuntu and nobody is manifested [03:00] anyone know? [03:23] manifested? [03:30] RAOF: got a second? [04:01] bigon: what's up? [04:20] robert_ancell: ping [04:21] thumper, hep [04:21] robert_ancell: have you got a few minutes to help thomi out with an X/lightDB thing? [04:21] *lightDM [04:21] lightDM [04:22] * thumper sighs [04:22] sausage fingers [04:22] sure [04:23] robert_ancell: our AP machine isn't booting to lightDM [04:23] but getting to a failsafe [04:23] however if we kill X and restart lightDM, it works [04:23] or something... [04:24] * thumper looks at thomi [04:24] AP? [04:24] autopilot [04:24] one second [04:24] first thing is to look at /var/log/lightdm/lightdm.log [04:25] So there's some background info you may need :) [04:26] We're PXE booting the live precise daily CD, with NFS root FS. We get an error in the X log file, which says: [04:26] [drm] failed to set drm interface version. [04:27] Yesterday RAOF suggested that this may be because the drivers weren't loading [04:27] I confirmed that the drivers *are* in fact loaded, so we formed the hypothesis that maybe there's a race condition between the drivers loading and X starting. [04:27] And rebuilding the initramfs so that the drivers are in there hasn't worked? Bah. [04:27] I've just finished putting the drivers into the boot initrd, but I still get the same issue [04:28] RAOF: yeah :( [04:28] hmm, so sounds like an X issue then [04:28] and/or lightdm is being started before the drm device is ready [04:31] RAOF: any idea how I'd confirm that the modules are in fact being loaded as part of the initrd? I mean, I added them, and it still boots, but I'm not sure how to confirm that I've actually altered anything [04:31] I can see where the drm module is loaded in the dmesg output, I guess that's a good sign [04:31] thomi: You can pass break=mount on the kernel command line; the boot process will then stop in the initramfs, and you should be able to modprobe/lsmod in there. [04:32] RAOF: ahhh, OK, let me try that [04:35] Damnit. When will Debian have ddebs? [04:36] I don't *want* to add a colord-dbg package; that's less-than-pointless busywork that should be handled by the archive tools. [04:37] RAOF: probably some time after they rely only on builds done on buildds [04:42] * micahg sees RAOF writing DEP 12 [04:47] RAOF: OK, this is messing with my mind. The kernel appears to be booting version 3.4.0-3, but the initrd on the CD seems to be for 3.2.0-24 [04:48] That would make things a bit weird :) [04:48] In particular, there's no way those drm modules would work ;) [04:49] RAOF: well, I think it's not even loading the right initrd. I expected it to load /casper/initrd.lz [04:49] * ajmitch wonders what daily image has 3.4.0 [04:49] but the files in that file are totally different to what I see from the busybox prompt [04:50] ajmitch: I thought quantal would [04:50] micahg: right, but thomi said it's a precise image, and 3.2.0-24 is the current kernel revision for precise [04:50] the precise daily live CD seems to [04:50] OK, so I must be doing this wrong [04:50] not according to the manifest [04:51] you're using the image from http://cdimage.ubuntu.com/precise/daily-live/current/ ? [04:52] yes. To be precise (haha): cdimage.ubuntu.com::cdimage/precise/daily-live/current/precise-desktop-i386.iso [04:52] err, that's the rsync source [04:52] so I may have made a few assumptions. [04:52] The FS I see at the busybox prompt is the initrd FS, yes? [04:55] * ajmitch would assume so, but doesn't know for certain [04:56] hmm, it must be loading it from somewhere else then [04:56] because none of my changes are showing up [05:04] RAOF: do you know who I should bug to find out what I'm doing wring with this initrd thing? I can only think that I'm modifying totally the wrong thing. [05:04] thomi: My guess is that slangasek or cjwatson would probably know? [05:05] hey - here's something interesting - I just hit Ctrl+D from the busybox prompt, and it booted straight into the desktop. [05:05] which reinforces my beliefe that this is a race condition somehow [05:06] * thomi tries to repeat [05:09] yup, 2 from 2. maybe I fixed it by thinking at it really hard [05:10] RAOF: OK, if I put ' break=mount ' on the kernel command line and exit from busybox (without doing anything) it works. If I take out the ' break=mount ' then it fails. It also seems that the drm module *is* being loaded as part of the initrd load. [05:11] RAOF: so, any other ideas? ;) [05:12] So you get the initramfs prompt in the screen's native resolution? [05:12] Is this the equivalent of an amazingly, super, awesomely fast hard drive? [05:13] RAOF: uhhh, I don't know - the machine is plugged in to a KVM... let me see if I can detect a screen resolution change [05:13] When you break=mount you should notice the initramfs prompt being at a nice high resolution; (generally) not the BIOS default 320x200/640x480. [05:14] RAOF: yes, it jumps from the BIOS resolution of 720x400 to 1024x768 [05:14] Ok, so it really is loading the drm module in the initramfs. [05:15] seems so. [05:16] Is the boot really amazingly fast? [05:16] uhhh, I wouldn't have said so. [05:18] I wonder what's racing, then. [05:18] RAOF: about 10-12 seconds [05:18] from the busybox prompt to X starting when it works. [05:18] It certainly *seems* like a race, but that should be easily enough for drm to settle down, especially since it's loading so early. [05:18] I can take out the break=mount and count again if you want [05:21] Maybe? I'm not really sure. Perhaps apw would be helpful; he's dealt with drm race conditions from the kernel side before. [05:21] RAOF: OK, A few more hours till he gets online I guess [05:24] RAOF: seems about the same boot time [05:24] That doesn't seem fast enough to be the sort of race I'm thinking about; my systems boot in about that time, too. [05:25] right [05:25] Is there any *other* initialisation that occurs during livecd boot that doesn't occur normally? [05:26] also, this used to work, I'm reasonably sure that I've eliminated anything *I've* done from the mix, which leaves... I dunno - a change in the daily CD maybe? [05:32] Happen to remember *when* this worked? [05:32] I can look it up, one second [05:32] June 7th [05:33] thing is, I was changing things at the time, but as I say, I've spent a couple of days removing all the changes I was making at the time [05:33] Good Morning. [05:34] thomi: You mean the *precise* livecd worked on the 7th of June this year? [05:34] yup [05:34] That surely hasn't changed since 12.04 release! [05:35] I figured maybe we still produce daily CD builds that contain stuff coming in the SRU? [05:35] I guess not [05:39] the cd images are dated later than the 7th, surely they're for 12.04.1? [05:39] good morning [05:40] ajmitch: that makes sense [05:40] hi didrocks [05:40] hey thomi! [05:41] RAOF: I've just re-run a build without *any* customisations - just extract the ISO and go, with the same results. [05:41] so is there a way to see what changes have been made to the CD daily ISOs in terms of packages & changelogs? [05:41] thomi: And does the 12.04 release livecd (still) work? [05:42] RAOF: good idea, I'll check... [05:42] thomi: you can diff the manifests [05:43] trying this one: /releases/precise/release/ubuntu-12.04-dvd-i386.iso [05:48] ...with the same results [05:54] Which suggests that perhaps it's *not* a change in the CDs. [06:46] RAOF: Yeah. I'll try and catch apw this evening and see what he says. [06:46] thomi: It's really strange if your setup used to work with the same CD images. [06:47] indeed [07:51] hey [07:52] hey seb128 [07:52] lut didrocks === tkamppeter_ is now known as tkamppeter [08:00] how does one get more kbd layout options to the unity-greeter? some langsupport packages installed or.. [08:01] tjaalton, the greeter list your user layouts, just add one to your user session [08:02] tjaalton, i.e that's by user, corresponding to the selected user [08:02] seb128: and what if a user has never logged in? [08:02] tjaalton, you get only the system layout [08:02] ok [08:03] and what if it's on a large setup where you first need to enter your username? same thing? [08:04] silly questions i get :) [08:07] guess it's a regression compared to gdm that you can't select the layout from the installed ones [08:07] from the login screen [08:20] tjaalton, sorry, I didn't read the channel for a bit [08:20] tjaalton, regression, design choice, I think the GTK greeter has a language selector [08:21] tjaalton, it's a greeter thing really, not a lightdm thing [08:21] tjaalton, you would like a flat list of over an hundred keymaps? [08:21] tjaalton, we tried that for a bit, the indicator was just impossible to use [08:21] gtk-greeter doesn't have it [08:22] well even a static list of things to choose from, that the admin approves as 'supported' or such [08:22] also this is apparently still true :) https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/917144/comments/8 [08:22] Ubuntu bug 917144 in unity-greeter "Other ... option is missing" [Low,Confirmed] [08:23] unrelated to my question though [08:24] tjaalton, the gtk greeter has a language selector option for sure (it might not be one by default), not sure if that includes keymaps though [08:24] tjaalton, having a "default list of keymaps" or "always listed keymaps" merged with the user list seems a reasonable request [08:24] tjaalton, can you file a request with a described usecase on unity-greeter [08:25] tjaalton, the "other" stuff was an "hot" topic with design, they found in user testing that this entry was confusing lot of desktop users... [08:25] seb128: sure thing, thanks [08:25] tjaalton, not sure what we can do out of having different configs, greeters for desktop cases and corporates ones [08:25] the "other" issue isn't an issue for my friend, apparently they have just "Login" now, so maybe the bug could be closed, dunno [08:27] tjaalton, well, that's a configure think, you get "login" if you hide the users list [08:27] tjaalton, but by default you have the user list and no "other" option [08:27] so if you get non listed users you need to tweak your config to be able to enter an username [08:27] from that bug it would seem that with "greeter-hide-users=true" they got "other" and "guest", but meh [08:29] tjaalton, right, that's what I was trying to say, if you hide the userlist (which is the option you just mentioned) you get the entry [08:37] seb128: let Esko file it, bug 1012560. marked it confirmed/low for now [08:37] Launchpad bug 1012560 in unity-greeter "unity-greeter should offer a configuration option for defining "supported" keymaps for selection" [Low,Confirmed] https://launchpad.net/bugs/1012560 [08:37] tjaalton, thanks [08:38] good morninge veryone [08:38] hey chrisccoulson, how are you? [08:38] seb128, yeah, good thanks. but a bit tired [08:38] how are you? [08:38] moin! [08:39] hey Sweetshark [08:39] chrisccoulson, I'm good thanks [08:39] chrisccoulson, did you do late hacking again? [08:40] seb128, i was investigating this bug quite late [08:40] chrisccoulson, the focus one? [08:40] chrisccoulson, did you find anything? [08:40] seb128, yeah, it's a unity 2d bug :) [08:40] seb128, https://launchpad.net/~chrisccoulson/+archive/ppa/+sourcepub/2505509/+listing-archive-extra fixes it [08:41] the panel sends the wrong timestamp when closing a window [08:41] it sends the system time rather than the X timestamp [08:41] really silly ;) [08:42] chrisccoulson, I knew it! damn unity 2d :p [08:42] thanks to artnay for helping debug this over IRC too :) [08:45] pitti: re consolekit, well I'm trying to figureout when a new session must me started [08:46] and I saw a patch from you in the pam connector === chris_ is now known as Guest73851 [09:05] seb128, it seems that KDE is having some ongoing problems in the archives? [09:05] http://people.canonical.com/~ubuntu-archive/testing/quantal_probs.html [09:05] and I guess calligra is not building at all on ARM? [09:08] rickspencer3, the current version failed to build apparently [09:08] seb128, this has been dangling for some days [09:08] is someone from Kubuntu working on it? [09:16] rickspencer3, I don't know but I will find out ;-) [09:16] seb128, ok, thanks [09:16] the Kubuntu community should be on top of their quality in the archive [09:16] yeah, makes sense [09:16] seb128, feel free to escalate to jasoncwarner_ if you need someone to follow up with them [09:22] rickspencer3, ok [09:22] thanks seb128 [09:23] thanks for pointing the issue ;-) === rickspencer3 is now known as rickspencer3_ === rickspencer3_ is now known as rickspencer3 === MacSlow is now known as MacSlow|lunch [11:40] chrisccoulson, shouldn't you comment on the firefox bug to point them to your test package or reassign to unity-2d or something? === MacSlow|lunch is now known as MacSlow === ralsina is now known as mandels_ring === mandels_ring is now known as ralsina === pitti is now known as pitti_ === pitti_ is now known as pitti === apw is now known as apw_ === apw_ is now known as cafetiere === cafetiere is now known as apw_ === apw_ is now known as cafetiere === cafetiere is now known as apw === MrChrisDruif is now known as ChrisDruif === ChrisDruif is now known as BrokenThumb === BrokenThumb is now known as MrChrisDruif === geser is now known as geser_ === geser_ is now known as geser [13:10] good morning === m_conley_away is now known as m_conley [13:44] mvo, hey, you or glatzor should make the bugs of the aptdaemon SRU which is the queue SRU compliant [13:44] mvo, i.e testcase, regression potential, impact at least [13:51] seb128, yeah, sorry. i've commented and reassigned it now (https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/1010466/comments/22) ;) [13:51] Ubuntu bug 1010466 in unity-2d "dropdown boxes on sites stop working" [Medium,Confirmed] [13:51] chrisccoulson, thanks [13:52] popey, didrocks: ^ we need that SRUed please [13:52] where is sil2100? [13:52] popey: can you pass it on? [13:52] popey, didrocks: chrisccoulson has a patch for it [13:53] anyway, the -2d SRU is still blocked on the C++ case [13:53] chrisccoulson, did you merge request it for lp:unity-2d? [13:53] I thought unity-2d would get dropped? [13:53] seb128, i think we need to handle the SRU, as it has to go through *-security [13:53] * didrocks looks [13:53] (well, micahg needs to handle it) :) [13:53] MrChrisDruif, it will, it's shipped in precise though [13:53] chrisccoulson, why was that not an issue with firefox < 13? [13:54] seb128, there was a change in firefox to use real timestamps in pointer grabs, to fix some other issues [13:54] ok [13:54] Yeah, which wise guy didn't mention this in time for precise? ;-) Now we're stuck with it for 5 years =) [13:54] then there was a whole bunch of changes on top of that which rely on the new behaviour ;) [13:54] popey: can you get unity-2d upstream reviewing the patch, getting it merged today, and then, we cherry-pick? [13:54] else i would have reverted it for a bit [13:55] chrisccoulson, ok [13:56] seb128: indeed, let me work on this next [13:58] mvo, thanks [13:58] mvo, nice to see those bugs fixed btw so kudos to glatzor and you ;-) [13:59] didrocks: yeah, will do, thanks [13:59] popey: this is urgent, we need a patch now [14:00] popey: well, the time for chrisccoulson's patch to get merged by upstream and so on [14:00] then cherry-pick in the current unity-2d package [14:00] ya [14:01] didrocks, sil2100, popey: talk with micahg, that update will need to go through -security according to chrisccoulson since that's where the firefox update got shipped and the fix needs to reach the same set of users [14:01] thanks [14:02] chrisccoulson, did you put a merge request up yet? [14:02] seb128, no, i wasn't sure what the process was for unity-2d :) [14:02] want me to do that? [14:02] chrisccoulson, yes please [14:02] chrisccoulson, process, just do a merge request for lp:unity-2d [14:03] seb128, ok, will do. thanks! [14:03] chrisccoulson, yw [14:05] seb128, didrocks, popey: so that I understand it correctly... this patch needs to be released urgently, without considering the other SRU patches for unity-2d? [14:05] chrisccoulson: there's probably an issue with your patched unity-2d-launcher (launcher doesn't get drawn, can be only triggered with ) - also, the FX bug doesn't happen in unity-3d but it's still valid in unity-2d *and* gnome-shell [14:05] sil2100: indeed [14:05] sil2100: it needs to go through -security [14:05] So just a cherry pick to the current unity-2d version in precise? [14:05] ACK [14:06] sil2100: but still need to be reviewed upstream and merged [14:06] So for now we're waiting for a merge to unity-2d, right? [14:06] artnay, i'm not sure how that could happen, as this is just a one liner to the panel code, which is quite isolated :/ [14:06] sil2100, then it needs to be merged as well in the normal SRU you plan to get out soon [14:06] it doesn't touch anything in the launcher at all [14:06] didrocks, ^ [14:06] seb128: we need to line up -security to look at it though [14:06] are you sure it didn't happen before? [14:06] seb128: ACK [14:06] popey, yeah, get the update ready and talk to micahg to get it out [14:06] chrisccoulson: 100% positive, started to happen only after updating to test1 [14:06] seb128: well, it's a cherry-pick in the packaging branch, not relevant to talk about the normal SRU as it's unity-2d trunk [14:07] hmmm :/ [14:07] seb128: that's why I'm speaking about getting it merged to trunk first [14:07] ok [14:07] seb128: we are not "waiting for a merge", you need to ping upstream and explain they need to review it [14:08] oupss [14:08] sil2100: ^ [14:08] ☺ [14:08] that was for you :) [14:08] ;) [14:08] ETOOMANYs ;) [14:08] Was the MRQ requested already? [14:09] chrisccoulson: ^ [14:09] chrisccoulson: ? [14:09] didrocks, sil2100, not yet. doing it now ;) [14:09] chrisccoulson: ping me once it's setup ;) [14:16] didrocks, sil2100 - https://code.launchpad.net/~chrisccoulson/unity-2d/lp1010466/+merge/110075 [14:16] thanks chrisccoulson [14:20] chrisccoulson: it's getting reviewed [14:20] sil2100, thanks [14:38] hm, where did Chris go? [14:38] I'm right here? [14:38] The other Chris ... ;) [14:39] Ghehe, I figured ;-) [14:43] chrisccoulson: could you check the comment from the unity-2d guys on the MRQ? [14:48] sil2100, he just did [14:49] sil2100, i.e merge request updated [15:01] Approved \o/ [15:12] Waiting for it to get merged and I'll cherry pick it [15:12] didrocks, seb128: how should I give it to the -security team? [15:13] Can I push it to some local branch for them to use for packaging? [15:13] Or should I prepare a source package? [15:16] sil2100, either, like you would give to any packager or sponsor [15:16] micahg, hey, are you there yet? [15:16] I'm pinging him, but I think he's still not around [15:21] sil2100, it might be a bit early for him still [15:22] sil2100: you tested it on your machine as well, right? :) [15:29] hi seb128 [15:29] micahg, hey [15:30] micahg, chrisccoulson got a fix for unity-2d for the tb,firefox grab issue [15:30] micahg, sil2100 has been backporting it and doing a package update, can you work with him to get that uploaded to -security? [15:30] seb128: sure [15:30] micahg, thanks [15:31] sil2100, ^ [15:31] micahg: how would you prefer to get the fix? [15:31] sil2100: bzr branch or debdiff is fine, are there release specific branches or the UDD ones? [15:32] micahg: everything's in one branch [15:32] micahg: the source and distro packaging [15:33] I'll just double test if it's fine and send you the branch :) [15:33] sil2100: we've got 3 unity-2d releases in stable [15:34] micahg: what are the version numbers? [15:34] sil2100: http://paste.ubuntu.com/1039238/, so we need it based on the version in -updates for oneiric and precise [15:34] micahg: since I'm first patching 5.12.0-0ubuntu1 from precise-updates [15:35] sil2100: I can take them as you have them ready and start testing them, do we have a bug with a proper test case as well? [15:35] micahg: but only the versions from -updates, right? i.e. 5.12.0-0ubuntu1 and 4.12.0-0ubuntu1.1 ? [15:35] chrisccoulson: ^^ [15:35] sil2100: right, natty never got an update thusfar, so it'll be based on the release version [15:37] micahg: ACK, will ping you as soon as I set up everything [15:37] sil2100: thanks [15:37] sil2100: what time zone are you in BTW? [15:38] micahg: european, UTC+2 right now iirc [15:38] micahg: but I'll still be around for a while [15:39] didrocks: as the series, should I set precise-security etc.? [15:39] sil2100: indeed [15:41] didrocks: what about the version number? 5.12.0-0ubuntu2 ? (for precise) [15:42] sil2100: can be 1.1 [15:42] 5.12.0-0ubuntu1.1 [15:42] ACK [15:47] didrocks: could you ACK on https://code.launchpad.net/~sil2100/unity-2d/precise-security ? [15:47] I mean, if the changelog is fine [15:47] etc. [15:48] looking [15:49] sil2100: everything looks fine to me, I see no gotcha :) [15:49] didrocks: thanks! Doing the same for the rest now [15:49] great [15:49] micahg: ^ [15:49] (and testing) [15:50] micahg: hmm, there's no 4.12.0-0ubuntu2 for unity-2d on oneiric? [15:51] sil2100: no, there's 1.1 in updates [15:51] Ok, doing it the rough way then [15:52] didrocks: do you maintain post-release branches anywhere (just worrying if I need to modify the changelog) [15:53] micahg: we didn't for unity-2d yet as we didn't diverge, but it should be ~ubuntu-desktop/unity-2d/precise [15:53] didrocks: what about oneiric and natty [15:54] it was still under ~unity-team IIRC, let me check :) [15:55] should be lp:unity-2d/4.0 for oneiric [15:55] and lp:unity-2d/3.0 for natty [15:55] but double checking is wanted [15:56] micahg: as it's quite dead right now, and trunk will be /precise soon, not sure if you want to store an additional maintain branch for precise, it's as you wish [15:56] didrocks: ok, should I push changelog changes there? [15:56] didrocks: I don't need it at all, I have the archive as a Vcs :) [15:56] I just don't want to mess you up [15:56] micahg: no need then, the next SRU (coming soon) is based on trunk and contain the fix already [15:57] I'll just ensure we will have the changelog in it === zyga is now known as zyga-afk [15:57] didrocks: ok, thanks [15:57] yw :) [15:57] didrocks: well, lp:unity-2d/4.0 is for oneiric, but not oneiric-updates [15:58] didrocks: it seems one version got lost somewhere, eh [15:59] sil2100: ah, probably [16:00] didrocks: not a problem though [16:00] great :) [16:01] didrocks: I would need some advice though - since ubuntu1.1 from oneiric-updates uses a quilt patch for introducing the new changes [16:01] didrocks: should I do the same for ubuntu1.2 (our -security changes) ? [16:01] Sweetshark: FWIW, you usually don't want to hijack an actual bug for a huge SRU, the bug is part of what you want to verify [16:02] i.e. adding a quilt patch? Or maybe just include it normally, without using any quilt patches? [16:02] sil2100: it's whatever you prefer, if you want to include it manually, you need to readd the missing upload though [16:02] sil2100: I would say rebase is the best :) [16:03] didrocks: rebase, you mean turning the ubuntu1.1 quilt patch into a bzr commit and then add our -security ubuntu1.2 patch on top of it directly to the source as well? [16:04] And requesting the ubuntu1.1 patch to unity-2d/4.0 ? [16:04] sil2100: exactly [16:04] (by a merge?) [16:04] micahg: I was asked to add the boilerplate there by seb128. I will just file a second bug "update to 3.x.x" next time and have in in the changelog too .. [16:04] Phew, ok - will do [16:04] ;) [16:04] sil2100: merge or push/pull is fine :) [16:04] sil2100: good luck! [16:05] Sweetshark: thanks :), it also saves the people in the bug from seeing all the non-related SRU comments as well :) [16:07] chrisccoulson: should I use the test case that I was give in #ubuntu-mozillateam yesterday for the unity issue or is there a simpler one? [16:09] cool, people are writing articles containing a TODO-list for my prerelease ;) http://www.webupd8.org/2012/06/libreoffice-360-beta-1-released-ubuntu.html === cking_ is now known as cking === mfisch` is now known as mfisch === mfisch is now known as Guest71017 === greyback is now known as greyback|dindins [17:00] * didrocks waves good evening === greyback|dindins is now known as greyback === JanC_ is now known as JanC === Ursinha` is now known as Ursinha === Ursinha is now known as Guest57727 [19:42] chrisccoulson: still wondering about the test case for the unity update when you have a chance [19:43] micahg, yeah, you can just use the case that triggered it yesterday [19:43] chrisccoulson: not being able to right click is the symptom? [19:43] it should be quite trivial to come up with a testcase from my explanation on the bug :) [19:43] yeah [19:43] ok, thans [19:50] popey: I've got 3 symbols dropped from a rebuild of unity-2d (in unity-2d-panel): http://paste.ubuntu.com/1039608/ [19:51] micahg, that seems like qt symbols leaked? [19:52] chrisccoulson, ^ is that a side effect of your change? [19:52] yes it is [19:52] seb128: maybe [19:52] those shouldn't be exposed at all [19:52] yeah, it's a bit weird [19:53] but, well, cpp, you can count for weirdness :p [19:53] * micahg just doesn't want to break someone's panel app [19:53] why are we checking exported ABI of private objects anyway? [19:54] chrisccoulson: we generally run checks on symbols of all libraries, if it's not important, I'll ignore it, just wanted to check [19:54] why do we do that? it seems pretty wasteful to check symbols on a private object that isn't used outside of that package [19:55] it doesn't even have public headers [19:55] that really is a waste of time :) [19:55] chrisccoulson: it's part of the security team's tools, it just checks the symbols of all libs [19:56] not all libs outside of /usr/lib/*/ are private unfortunately, so we can't train the tools to not check them, but as I said if it's not a problem, I'll ignore it [20:57] can any one help me to figure why the shutdown screen popups over and over again [20:57] ? === Guest57727 is now known as Ursinha === Ursinha is now known as Guest2796 === Guest71017 is now known as mfisch [23:35] hey robert_ancell , wanted to follow up on the seb128 comment last night about GTK 3.5 and you unblocking it...how are we looking? [23:35] jasoncwarner_, yeah, I can make it not crash, so I think that's the best solution [23:35] it will look a bit wrong, but that's for ps to fix [23:36] we really can't hold everything up for them [23:36] thanks robert_ancell , do you know if cimi is on it right now? (I'll follow up there anyway) [23:36] agreed [23:36] thanks for unstucking it [23:36] unsticking [23:36] unstucked? [23:36] hi [23:36] hey thumper [23:37] who do we have as a pango fixer? [23:37]