/srv/irclogs.ubuntu.com/2013/06/28/#ubuntu-desktop.txt

Sweetsharkhttp://lists.debian.org/debian-devel/2013/06/msg00720.html scary. 1200 exploitable bugs in wheezy.00:33
lifelesswell00:36
lifelessits not clear that there are 1200 bugs00:36
lifelessthey're reporting the same library crash in every consuming application.00:36
lifelessIt might be 5 bugs.00:36
lifelessdunno yet.00:36
Sweetsharklifeless: given the number of different packages, that would have to be 5 glibc bugs then though, which would hardly make it any better.00:43
lifelesssure00:48
=== alex_abreu is now known as alex-abreu
sarnoldthey aren't all in libraries, here's one that was well and truly our fault: https://lists.ubuntu.com/archives/apparmor/2013-June/003927.html01:01
=== asac` is now known as asac
pittiGood morning04:36
pittiattente: I noticed missing menus in gtimelog and my pygtk test application04:37
RAOFpitti: Good morning.04:45
RAOFpitti: I presume the reason umockdev doesn't have a testbed_add_from_file because no-one's wanted it yet? :)04:55
pittiRAOF: by and large, yes; I was using add_from_string()04:56
RAOFThat's what I'll do. But I'll probably read it from a file, because it's quite big :)05:05
pittiRAOF: yeah, and umockdev-run does just that05:09
pittiRAOF: if it's more convenient, I'm happy to add an add_from_file, which will then just pass along any errors as GError05:10
RAOFYeah, it'd be more convenient.05:10
RAOFWe're highly likely to be adding significant numbers of significantly-attributed mock udev devices.05:11
pittiRAOF: mostly for input, I presume? or do you mock anything else?05:28
RAOFdrm, too.05:29
RAOFDevice detection, monitor hotplug.05:30
RAOFAlthough the tense is wrong; *currently* we don't mock anything :)05:30
pittiRAOF: I filed https://github.com/martinpitt/umockdev/issues/15 as a reminder05:49
RAOFAwesomesauce.05:50
RAOFpitti: Hm. There's no way to destroy a umockdev object from C?06:27
RAOFThe Vala class has a destructor; I'm surprised that doesn't get translated to something C-callable.06:27
pittiRAOF: it's a normal GObject, so you just g_object_unref() it06:30
pittiRAOF: the destructor gets translated into a normal GObject _dispose() (or maybe _finalize())06:30
RAOFAh, that makes sense.06:30
pittibut one usually doesn't call those directly06:31
darkxstRAOF, will gdm work under XMir?07:13
RAOFdarkxst: Not without patches, but that's because gdm isn't really under X now.07:16
darkxstRAOF, well the rendering side of things is...07:17
RAOFBut XMir *is* X, so gdm will happily start X as normal.07:17
RAOFdarkxst: Oh, yeah.07:17
RAOFSo, the answer to ‘will my $X11 client work under XMir’ is “yes”.07:18
didrocksRAOF: btw, do you think that we can expect this patched Xorg going quickly to saucy once we resolved the minor issues around Mir to enter distro?07:18
mlankhorstRAOF: if you can nuke the separate mir thread xmir would  become a lot more acceptable :-)07:18
RAOFmlankhorst: Oh, I'd *love* libmirclient to give me an fd. I think we might be doing that, too.07:18
darkxstRAOF, so when gdm tries to launch a new X server, is it launching X or Xmir07:18
darkxstI assume the latter would require patches?07:19
RAOFdarkxst: If it doesn't pass -mir $SESSION_ID to /usr/bin/Xorg, it's starting X.07:19
RAOFTechnically, even if it *does* pass07:19
RAOFTechnically, even if it *does* pass -mir $SESSION_ID to /usr/bin/Xorg it's starting X :)07:19
mlankhorstRAOF: I don't think it does atm, though07:20
RAOFmlankhorst: Right. At the moment we're all threads, all the time. I think tvoss_ is amenable to also exporting an eventfd, which should get rid of the annoying thread-to-eventloop hack.07:21
mlankhorst\o/07:22
mlankhorstRAOF: I was thinking something like pulse mainloop07:22
mlankhorstit may not be perfect, but it's understood07:22
RAOFdarkxst: Correct. If you wanted to use XMir+unity-system-compositor from gdm you'd need to patch gdm to (a) start unity-system-compositor, (b) pass the appropriate arguments to X, and (c) send session-switching commands to unity-system-compositor.07:22
mlankhorstand if you don't want a separate thread you don't need to, afaik07:22
tvoss_RAOF, yup, but it will take until next week, my plate is kinda full at this point07:22
mlankhorstit was awesome for wine, where I do need a separate thread, but I need to create the thread in wine itself07:23
tvoss_mlankhorst, the idea is to expose run, run_one, poll, poll_one and have an fd that signals when there is work to do07:24
mlankhorsttvoss_: yeah pulseaudio does something like that07:25
tvoss_mlankhorst, ack, will look into it beginning of next week07:25
didrocksRAOF: ignoring me? :p07:32
darkxstRAOF, ok, that doesnt seem really bad.... but I also guess it wouldnt actually end up being that straight forward07:32
RAOFdidrocks: ?07:32
didrocks09:18:18      didrocks | RAOF: btw, do you think that we can expect this patched Xorg going quickly to saucy once we resolved the minor issues around Mir to enter distro?07:32
RAOFOh! Yes07:33
RAOFbaby07:33
darkxstRAOF, what about further down the track though, when gnome moves to wayland. Would it be possible to have Mir system compositor and Wayland Session Compositor in harmony?07:33
RAOFdidrocks: Yes. You don't need anything from me for that to happen except an upload of a patched xserver to the archive, right?07:39
RAOFdarkxst: That's less clear; basically what it requires is for GNOME's compositor to have a Mir backend.07:39
darkxstRAOF, that won't happen07:40
seb128good morning desktopers07:40
darkxsthi seb12807:40
seb128I like how opensource dev keep stating that things won't happen07:40
didrocksRAOF: that's my understanding for now. I do expect surprises of course, but I trust at least your side ;)07:40
seb128when anyone can come and make them happen07:40
didrockssalut seb12807:40
tvossRAOF, or to be more clear, a wayland backend rendering to Mir07:40
RAOFdarkxst: No. I don't mean for GNOME's compositor to be built on Mir; I mean for GNOME's compositor to be able to run under Mir. Like how Weston can currently run under Weston.07:40
seb128hey didrocks, tvoss, RAOF, darkxst07:41
tvossseb128, hey07:41
RAOFtvoss: Except of course that's a misunderstanding of what Wayland *is*07:41
tvossRAOF, exactly ;)07:41
RAOFThere are no ‘Wayland backends’, because Wayland is not a display server.07:41
tvossRAOF, for sure07:41
tvossdarkxst, I'm curious, do you see any technical issue preventing the GNOME compositor from talking to Mir?07:42
* RAOF wonders if we could come up with a nomenclature that accurately described the state of things07:43
darkxsttvoss, I don't know a whole lot about the deeper workings of mutter07:43
tvossdarkxst, ah, okay, I thought you were referring to a technical issue when saying that it won't happen07:43
RAOFdarkxst: AIUI mutter builds on clutter, which already has a perfectly servicable pluggable backend system.07:43
darkxstbut as I understand it, Wayland+X is enough of a pain, that its really unlikely they would add Mir into the mix07:44
seb128so much of those comments a just direct reaction against change/something different that some people planned...07:44
RAOFEh. Almost all the pain is in having the abstraction in the first place. Adding an extra target, while certainly annoying, is only incrementally annoying.07:44
tvossRAOF, +1, and the exercise of adding another target helps in shaping the abstraction layer07:45
tvossI think the pain in switching away from X is that everything is entangled there for historic reasons07:45
seb128not sure how realistic it will get to run GNOME on !GNOME-OS over time anyway07:45
didrocksRAOF: diagrams generally help by experience, people can dive to the level they want07:45
seb128they hard depends on their login manager, they increasingly depends on systemd, they are going to depends on wayland07:45
tvossdidrocks, but RAOF is right, the nomenclature is emphasiizing misunderstandings07:46
seb128swapping desktops easily is becoming a thing of the past07:46
didrockstvoss: not disagreeing with this :)07:46
seb128when your desktop is tied to an init system, a login manager, a display server, etc ... and different desktops pick different techs for all of those you actually end up have distro specific desktops07:46
didrocksok, just one MIR remaining (liborcus) for Sweetshark, that will wait some hours :p07:47
* didrocks adds to the confusion on purpose, it's Friday! ;)07:47
darkxstseb128, it actually sounded like they weren't entirely against getting lightdm working with gnome-shell07:49
* tvoss wonders why a session has to make assumptions from where it was started07:50
seb128tvoss, it doesn't, until it uses the greeter from the login manager as lock screen...07:50
darkxsttvoss, under gnome, authentication for lock screens etc, is piped to gdm07:50
tvossdarkxst, seb128 wouldn't that be solved more elegantly with a common interface implemented by both gdm and lightdm?07:51
seb128it would, robert_ancell tried to add a gdm compatible greeter to lightdm07:51
seb128but I'm not sure he finished, he got busy with Mir :p07:51
tvossseb128, where is the interface defined?07:52
seb128tvoss, I'm not sure, the GNOME guys didn't really spec it or made it public/documented ... robert_ancell would know better, I think he just looked a the gdm07:55
tvossseb128, interesting07:55
seb128tvoss, https://github.com/robert-ancell/gnome-shell-lightdm07:57
tvossseb128, okay07:57
tvossseb128, thx07:57
seb128yw07:57
tvossseb128, are you aware of any attempts to standardize the dbus interfaces here?07:58
seb128no07:58
seb128I think everyone has been focussing on making their desktop work with the components they picked07:58
seb128and nobody went out of the way to spend time trying to standardize things or making them swappable07:58
darkxstsure, but the main issue is the authentication channel, gnome-shell renders the lock screen07:59
Laneyhey, happy friday08:01
darkxstin fact gnome-shell also renders the gdm login screen, but that is largely irrelavant for the lightdm use case.08:01
seb128Laney, hey, happy friday to you too!08:02
darkxstLaney, hi, I am up to happy weekend here :)08:02
Laney:P08:02
Laneybut you have unhappy monday before me so ;-)08:03
darkxstLaney, usually that is tired monday.... but oh well!08:04
Laneybtw I finally fell off my bike the other day :(08:05
Laneywhile trying to look at the map I forgot I was clipped in and tried to put my foot on the floor08:05
Laneybad idea08:05
darkxstLaney, I fell too, in the dark..... huge bruised and a bit of lost skin... but ready for another weekend!08:06
darkxstMTB in the dark is probably a little dangerous ;(08:07
Laneyyes, yes indeed08:07
darkxstalthough we don't have much choice, its getting dark by about 5.30pm now08:08
=== vrruiz_ is now known as rvr
seb128oh10:05
seb128since when does launchpad automatically adds packages/lines to bugs when you use "lp: #nnn" to an upload?10:07
seb128e.g https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/119484410:07
ubot2`Ubuntu bug 1194844 in Ubuntu UI Toolkit "[ListItem.SingleControl] Does not respect the default inner margins" [Medium,Confirmed]10:07
seb128didrocks, is that launchpad or your daily release magic?10:07
seb128comment #4 and #510:07
seb128it's a bit funny, that's a toolkit bug10:08
seb128I just add "  *until bug ... is fixed in the ui toolkit" for reference to my comment10:08
seb128the daily magic added the lp # reference for that bug10:08
seb128then something added the sources to the bug10:09
seb128too much magic ;-)10:09
didrocksseb128: that's launchpad :)10:10
didrockshum10:10
didrocksubuntu-system-settings-online-accounts and ubuntu-system-settings10:10
seb128it's quite nice, we got bitten quite often by bugs don't getting closed because of component mismatches between source uploaded and bug10:10
didrocks2 different packages?10:10
seb128yes10:10
seb128online-account is a standalone source10:11
didrocksah10:11
didrocksyou wrote:10:11
didrocks(until bug10:11
didrocks    #1194844 is fixed in the ui toolkit)10:11
didrocksso it's been detected as a bug10:11
didrocksand added LP: …10:11
seb128right10:11
didrockssee the FAQ ;)10:11
seb128yeah, I got that part10:11
seb128what confuses me is that something did "also affect ubuntu-system-settings-online-accounts" on the bug10:11
seb128and set that to fix released on upload10:12
seb128where in the past uploads on the wrong source would just go to /dev/null10:12
didrocksah, the also affect is daily release :p10:12
didrocksif it detects bugs to close10:12
didrocksit's opened the components10:12
seb128ok, so not launchpad10:12
didrocksopening*10:12
seb128I see ;-)10:12
didrocksyep10:12
seb128didrocks, thanks10:12
didrocksas a lot of upstreams just opens the upstream bugs10:12
didrocksmakes things easier to track10:12
seb128that makes sense10:12
=== MacSlow is now known as MacSlow|lunch
Laneyhttp://forums.mozillazine.org/viewtopic.php?f=23&t=272249311:54
* Laney sniggers11:54
seb128Laney, O_o11:59
* xnox likes the 2015 design a lot12:02
Laneylet's vendor patch it in now to be ahead of the curve12:02
Laneychrisccoulson: ^ make it so12:03
ogra_ubuntu - flatter than apple !12:03
jbichadoes 'signon' need to do an automatic snapshot every day?12:20
seb128nothing needs to12:21
seb128but that's the purpose of daily releases12:21
seb128if there is a commit it's released12:21
seb128that's try for the whole unity stack12:21
seb128why?12:21
jbichabut there aren't commits AFAIK https://code.launchpad.net/~online-accounts/signon/trunk12:21
jbichaI don't mind daily releases when minor things change12:22
seb128seems like a bug12:22
seb128didrocks, ^12:22
seb128oh12:22
seb128ignore the "oh"12:23
xnoxseems like it think it's own changes are the changes to release again.12:23
Laneylooks like that has been happening a lot!12:23
attentepitti, hi12:24
attentepitti, which menus are missing from gtimelog?12:24
seb128yeah, there is a bug somewhere which leads it to think there is a new change to land when there is none12:24
pittiattente: there is no global menu for it, it has an integrated menu12:25
pittiattente: hey, how are you?12:25
LaneyI get a global menu for it here but it suffers from the same bug as virt-manager12:26
attentepitti, i'm good, and you?12:26
attentepitti, my experience is the same as Laney12:26
pittiattente: I'm well, thanks12:26
pittiattente: I don't think it's just me, fginther noticed the same12:27
seb128pitti, do you have integrated menus for any gtk2 app? e.g inkscape or xchat?12:27
pittiattente: or rather, autopilot-gtk has a test which assumes that the GtkMenuItems are visible12:27
seb128pitti, you guys maybe don't have the -gtk2 installed?12:27
Laneyyeah maybe you miss unity-gtk2-module12:27
pittiattente: and it succeeds on saucy, but fails on raring because global menu was working there12:27
pittiattente, seb128: gtimelog and my test program are both gtk3 and GI12:28
pittilet's not worry about old gtk2 stuff12:28
seb128oh, I though that was still gtk212:28
seb128pitti, do you test on raring?12:28
seb128(don't do that)12:28
pittiseb128: test what?12:28
pittiseb128: global menus were working fine on raring, yes12:28
seb128"it succeeds on saucy, but fails on raring b"12:28
seb128saucy works?12:28
pittiseb128: that was my ap-gtk test case which assumed builtin menus12:29
pittiI fixed the test now to use UBUNTU_MENUPROXY=012:29
seb128can you summarize what work where?12:29
pittibut that's just how I noticed it, and that it's not just me12:29
pittiso the summary is:12:29
pitti- gtimelog had a global menu until raring12:29
pitti- gtimelog has an integrated (non-global) menu in saucy12:29
pittiand that looks like a regression to me12:29
pittiunless there was some policy change or so12:29
seb128should not12:30
seb128it works for me (but with the quit item labeled "gtk-quit")12:30
attenteis u-g-m even available under raring?12:30
seb128no, ignore raring, I think he's saying that it was working with dbusmenu there12:30
pittiyes, it was12:31
seb128the issue is that saucy doesn't work for him12:31
attenteah, sorry12:31
seb128which I can't confirm (out of the "quit" item being wrong labelled)12:31
pittithe regression in saucy is that some programs don't have a global menu any more, with gtimelog being one example12:31
desrtgood morn, pitti, seb12812:31
pittihey desrt12:31
seb128desrt, hey, happy friday to you!12:31
desrtfriday :D12:31
desrtthat calls for a coffee to celebrate12:32
pittiattente, seb128: so maybe fginther and I both have some new package not installed?12:32
seb128pitti, could be, but it wouldn't be working for any gtk3 app if that was the case12:32
pittiI guess the underlying mechanics have changed for the global menu?12:32
seb128right, it's a .so loaded by gtk12:32
seb128which relies on the env to list it12:32
seb128but that's true for any app12:33
seb128that wouldn't explain some apps working and some not12:33
desrtmaybe someone is scrubbing the env?12:33
desrtchpe tried to do this....12:33
seb128well, the same software works for Laney or I12:33
desrthuh12:33
attentei've got the global menu as well..12:33
seb128debugging required I guess...12:34
desrtmaybe they got crafty and added exceptions for the usernames who were likely to be packaging it :)12:34
attentehaha12:34
seb128pitti, you have the issue on your box, where other gtk3 apps work fine and starting apps the same way?12:34
pittiseb128: yes12:34
pittiactually, no12:34
desrtpitti: does it hide the local menu bar, or is it still shown?12:34
pittiif I launch gedit from a termina, it also has a builtin menu12:34
seb128pitti, env | grep GTK12:35
pitti$ env|grep GTK12:35
pittiGTK_MODULES=overlay-scrollbar12:35
seb128buggy12:35
desrtpitti never logs out/in :)12:35
desrtso he misses the new envvar :p12:35
attenteah...12:35
pittiseb128: but when I launch gedit from dash, I also get a builtin menu12:35
desrtOH12:35
pittiso gedit and gtimelog both have the bug, regardless of whether I launch from dash or terminal12:35
desrtthis _is_ chpe's fault12:35
seb128pitti, see /etc/X11/Xsession.d/80...12:35
pittidesrt: I boot my machine every day12:35
desrtgnome-terminal at some point was scrubbing those environment variables12:36
pittiit's not related to g-t12:36
desrtand of course anything you launch from the terminal is a subprocess of the terminal12:36
pittifor i in /usr/lib/*/gtk-2.0/2.10.0/menuproxies/libappmenu.so12:36
pittiseb128: ^ that looks gtk2 specific12:36
seb128pitti, that's deprecated12:36
desrtpitti: ah sorry.  i misread your previous statement about the dash12:36
Laneypitti: what's $UBUNTU_MENUPROXY?12:37
pitti$ echo $UBUNTU_MENUPROXY12:37
pittilibappmenu.so12:37
seb128that's wrong12:37
seb128you seems to be missing the conffile for the new unity menus12:37
pittigrep -r UBUNTU_MENUPROXY /etc/12:37
pitti/etc/X11/Xsession.d/80appmenu-gtk3:export UBUNTU_MENUPROXY="libappmenu.so"12:37
LaneyI think maybe 80unity-gtk-module is wrong12:37
Laneyit should just overwrite it12:37
seb128it seems like he doesn't have it installed...12:38
pitti$ dpkg -S /etc/X11/Xsession.d/80appmenu-gtk312:38
pittiappmenu-gtk3:amd64: /etc/X11/Xsession.d/80appmenu-gtk312:38
seb128pitti, that's the old stuff, that's deprecated12:38
Laneydid it depend on some unity/gtk thing which got removed?12:38
seb128pitti, do you have the file Laney just mentioned?12:38
Laneylook /in/ the file12:38
Laneyah, wait, it should do that right12:39
seb128Laney, it seems like he's missing the conffile12:39
seb128or the -common package that includes it12:39
Laneyyeah12:39
seb128but that's weird, why would menu work from unity then?12:39
pittino, I don't have that12:39
seb128pitti, dpkg -l | grep unity-gtk12:40
pittiseb128: perhaps that's still using the old dbusmenu stuff?12:40
pittiwhich package ships that file?12:40
seb128pitti, I made gtk2/3 conflict on the old stuff12:40
seb128pitti, dpkg -l | grep unity-gtk12:40
Laneyindicator-appmenu Recommends them12:40
attenteunity-gtk-module-common12:40
Laneyso ... you could easily not have gotten it12:40
pittiseb128: nothing12:40
seb128pitti, that's your issue, recommends didn't get installed12:41
seb128pitti, does apt-get --fix-recommends (or whatever that option is called) try to install them?12:41
* seb128 googles12:41
Laney--fix-policy --install-recommends12:41
seb128pitti, ^12:41
=== MacSlow|lunch is now known as MacSlow
pittithat wants to remove appmenu-gtk appmenu-gtk3 and install a gazillion packages12:42
seb128great12:42
attentei thought we had a hard Depends on unity-gtk-module-common?12:42
seb128"we"?12:42
seb128no, unity recommends the menu stuff12:42
seb128because some people want to opt out12:42
pittiseb128: installing unity-gtk-module-common doesn't remove the appmenu stuff, though12:43
seb128so we let them uninstall those without removing unity12:43
seb128pitti, that's ok, it has a conffile that override the appmenu one12:43
LaneyI don't think it matters if it's not removed as u-g-m will take over12:43
attentebut shouldn't installing unity-gtk23-module force the installation of the -common?12:43
seb128pitti, we needed that anyway because uninstall != purge12:43
Laneyattente: he didn't have any of it12:43
jbichaif there was an easier way for users to opt out of the global menu then you could make it a depends12:43
seb128there is an easy way12:44
seb128change the env variable12:44
pittidone12:44
Laneydoes gtk ignore not found GTK_MODULES?12:44
seb128not sure, it might throw warning at those12:44
Laneyseems you get a warning ... that file ought to check if the libraries exist then12:44
pittiLaney: yes, you only get a warning12:44
jbichawell I think dconf is more user-friendly (because it can be a GUI) than messing with environment variables12:45
seb128right, we should probably add that12:45
Laneyyeah, doesn't seem like u-g-m has any bad dependencies12:45
Laneyfile a bug? :)12:45
jbichalike overlay scrollbars have a dconf key :)12:46
seb128gsettings12:46
seb128but yeah12:46
seb128we can maybe add it to gsettings-desktop-schemas :p12:47
* seb128 hides12:47
attentelol12:47
jbichalol12:47
* jbicha adds goa dependencies everywhere12:48
ogra_dont forget ubuntu touch !12:49
ogra_:P12:49
seb128ogra_, oh, he started there, don't worry12:50
ogra_ah, phew12:50
ogra_:)12:50
seb128ogra_, GNOMers are eager to get GTK on the device ;-)12:50
ogra_hehe12:50
seb128(even if it can't get to the screen (yet))12:50
ogra_XMir might help12:50
seb128yep12:50
ogra_and who wouldnt want to run evolution on a 4" screen !12:51
ogra_(in desktop mode at 1080p resolution indeed(12:52
Laneysounds like the converged way12:52
jbichaneeds more whitespace padding :)12:53
desrtseb128: you said that debian has super-up-to-date gnome these days....12:55
desrti'm seeing only 3.4?12:55
seb128desrt, http://www.0d.be/debian/debian-gnome-3.8-status.html12:56
seb128desrt, do you run debian stable? ;-)12:56
desrtis that sid?12:56
desrtseb128: i don't run debian anything... was just looking into your claims the other day12:56
seb128desrt, http://packages.qa.debian.org/nautilus12:57
jbichatechnically saucy has more GNOME 3.8 than sid because Debian has transitions that take weeks12:57
didrocksseb128: jbicha: I would say there is a diff between trunk and the source package, ken should investigate I guess (and looking at those :p)12:57
seb128desrt, experimental for 3.8 atm, though they are moving pieces to unstable12:57
seb128didrocks, is that flagged somewhere? shouldn't the stack be blocked with manual approval required for those?12:58
* desrt always gets confused with stable kinda-stable (next), unstable (sid), super-unstable (experimental?), ultra-mega-unstable (testing?)12:58
Laneywhat's next?12:58
seb128desrt, well, experimental was used as an unstable because debian was frozen for 6 months for their release12:58
seb128desrt, they are getting stuff back to unstable but didn't go too crazy, they do transition decoupled and in order12:58
didrocksseb128: hum, why? the diff means "something changed", it's how it detects there is something to release12:58
seb128desrt, so it takes a bit of time12:58
didrocksbut in that case, it seems that the source package produced by bzr bd -S and trunk is different12:59
desrtseb128: and where does testing fit in?12:59
seb128didrocks, I though "packaging changes" would block the publishing for review?12:59
didrocksand that's a packaging bug12:59
didrocksseb128: there is no packaging change, right?12:59
LaneyI thought you diffed the to-be-uploaded source package and the archive12:59
seb128didrocks, sorry, I misread your "diff between trunk and the source package"12:59
didrocksLaney: no, we diff trunk with the archive12:59
didrocksLaney: I thought this week we can do a 2 stage thing, but we'll have in that case bugs like this spawning13:00
Laneymmm13:00
seb128desrt, testing is a transitionnal pocket ... but before release they freeze unstable mostly and transition bits ready from that small set13:00
desrtseb128: so experimental is the most-unstable one13:01
desrtthanks :)13:01
Laneyexperimental is optional13:01
seb128desrt, yes stable < testing < unstable < experimental13:01
Laneyfor both developers and users13:01
Laneyyou don't even get packages from it automatically if you enable it13:01
didrocksLaney: creating the source package needs a pbuilder chroot to be cleaned, it's not something we can do for the 233 components right now without killing the machine13:01
didrockshence the diff between trunk (ignoring .bzr*/ + diff we ignore) and the archive source13:02
seb128desrt, stable is like ubuntu stable, testing is like the unstable release nowadays (with extra delay), unstable is like unstable-proposed (where stuff get uploaded, they migrate to testing if they are not breaking the world), experimental is sort of ppa land13:02
* desrt really likes the ppa model13:02
Laneydebian's getting something like that13:03
desrtlovely!13:03
Laneyeven with 'official' PPAs13:03
Laneywhich will be cool13:03
desrtPPAs are perhaps the coolest of the canonical inventions13:03
Laneyand I think semi-automatic migration from them to the archive13:03
seb128I wish debian would get ddebs :p13:03
desrtin terms of launchpad features....13:03
Laneyi'm sure it can if someone does the work :P13:03
* seb128 is tired of all those -dbg flowing in through debian13:03
desrtspeaking of which13:04
desrtpitti: did you do any looking at that minidebug stuff?13:04
didrocksLaney: I have an idea (while having my shower)!13:13
didrocksso, still having this diff between trunk and the archive source13:13
Laneygosh!13:13
didrocksif diff -> use cowbuilder to build the source package13:13
seb128kenvandine, starting your day with reviews?13:13
didrocksthen, rediffing against between the 2 sources13:13
LaneyI've never built source packages in a clean environment13:13
* seb128 was just looking at Laney's work and noticed the comments flowing13:13
Laneyhas it been a problem for you?13:13
didrocksLaney: force with python2, all the dh_* things called on debian/rules clean13:14
didrocksthat I don't want to install on the machine :)13:14
didrocksif the second diff has:13:14
didrocks- only changes in debian/changelog13:14
didrocks- less or equals than 6 new lines in it13:14
kenvandineseb128, yup :)13:14
Laneybuild with -nc; there shouldn't be stuff to clean up in a fresh checkout13:14
didrocks-> no upload13:14
didrocksbut put the job in warning13:15
seb128kenvandine, I see how your ignored the harder one with signals though :p13:15
didrocksLaney: doesn't work even with -nc, some rules includes some .mk files13:15
Laneyah well I have things like that installed13:15
didrocksand it failed :p13:15
didrocksyep, not on the host13:15
kenvandineseb128, still reviewing :)13:15
didrocksknowing that we always have some of those helpers evolving13:15
kenvandinei got side tracked by fixing things that didn't match the design :)13:15
didrocksand just one machine on an old release that is shared with other stuff :p13:16
didrockskenvandine: hey! before that, there are some stuff to fix on online-accounts :)13:16
Laneyget yourself a nice container or do it in ... the ... cloud!13:16
Laneyanyway, the 'if diff' wouldn't have triggered in this case would it?13:16
didrocksLaney: the container is cowbuilder :p13:16
kenvandinedidrocks, i'll look at those in a few13:17
LaneyI mean one you can reuse13:17
Laneyif the expense is reconstructing everything all the time13:17
didrockskenvandine: like another source you had, there are a diff between the packaging and archive (so generated source) isn't empty13:17
didrockskenvandine: so it triggers dailies… daily :p13:17
didrocksLaney: well, cowbuilder is something like that13:17
didrocksLaney: but when you build webapps, you have 30 sources at the same time13:17
didrocksand installing all the build-deps/refreshing them takes time13:17
didrocksso better to ensure we do it as clean as possible13:18
Laneyyou can have one with the 'clean' build-deps installed13:18
didrocksLaney: you still have to update them13:18
Laneyyeah, but not every time you build a package13:18
didrocksI think the current system at least doesn't need "setup"13:18
LaneyI don't think most developers do that13:18
didrocksyep, but we raise the quality bar :p13:18
Laneya *source* package13:18
didrocksLaney: so, the double diffing can works and prevent that13:19
didrocksturning the job in a warning13:19
LaneyI don't think I understand the part where you decide whether to do the second diff13:19
didrocksif the diff shows there is something to build13:20
didrocks(between trunk and the archive source)13:20
didrocksso, we fire up our cowbuilder13:20
didrockscollect commits, and so on…13:20
didrocksthen build our source package13:20
didrocksand do that second diff between archive and source package13:21
Laneyah13:21
Laneyso why the line count thing?13:21
didrocksif we just have changes in debian/changelog (and less or equals than 6 lines), it means that the diff is useless13:21
LaneyCan't you just say "only changes in debian/changelog -> ignore"13:21
didrocksLaney: because maybe you want to force a rebuild?13:21
didrockslike bumping the version13:21
LaneyI thought that was done in the machinery13:21
Laneywith some force flag that would bypass such checks anyway13:21
didrocksLaney: that's planned, not the case yet, but in that case, it will add some line13:22
didrocksLaney: but sometimes, upstream just want to bump the version13:22
didrocksin that case, the contract is bump the version + a line like "* bump version" (or whatever)13:22
didrocksso, we'll have 7 lines with the "automatic snapshot from rev…"13:23
didrockskenvandine: http://bazaar.launchpad.net/~online-accounts/signon/trunk/revision/591 FYI13:23
didrocksLaney: would you be that kind to open a bug? :)13:23
didrocksI'll deal with this on Monday I guess13:23
didrocks(finishing building Mir on the nexus 4)13:24
Laneydidrocks: OK, what's the component13:24
didrocksLaney: cupstream2distro13:24
didrocksjbicha: btw, just ping me once both cheese and gnome-video-effects are fixed, I'll then promote them13:25
jbichadidrocks: thanks, will do :)13:25
didrocksyw :)13:25
Laneydoing13:26
sil2100eh13:29
sil2100hm13:29
sil2100didrocks: does jenkins work for you?13:29
didrocksoh a sil2100!13:29
* didrocks looks13:30
didrockssil2100: seems so :)13:30
didrockssil2100: try disconnect/reconnect to the VPN13:30
sil2100didrocks: ok, worked13:30
sil2100didrocks: uhoh, the unity check job is running since 4 hours13:31
didrockssil2100: yep, see #ubuntu-unity, just pinged mhr313:31
didrockssil2100: ati results are quite high?13:31
sil2100didrocks: yes, much higher then what we got in the morning ;/ In the morning we had 19/19 failures13:32
didrockssil2100: still higher than the threshold though13:32
sil2100Not sure if we can release just the indicator stack though13:33
didrockssil2100: maybe check with upstream & cyphermox?13:33
kenvandinedidrocks, what's up with the webcred stack?  it's all green13:52
kenvandinealthough it was published 5 hours after the build13:52
kenvandineso maybe someone manually did that while i was sleeping :)13:52
didrockskenvandine: look at the uploads for signon :p14:00
didrocksempty uploads14:01
didrocksthat's because trunk is different than bzr bd -S14:01
didrocks(the source package created)14:01
didrocksas for another one you fixed14:01
kenvandineshouldn't prepare had failed?14:03
kenvandineseb128, can you give me an uoa settings review?14:04
kenvandinehttps://code.launchpad.net/~ken-vandine/ubuntu-system-settings-online-accounts/category/+merge/17203914:04
seb128kenvandine, looking14:04
kenvandineeasy one :)14:04
kenvandinethere is nobody else from ~online-accounts for the next week14:04
* kenvandine will be lonely14:05
kenvandine:)14:05
seb128kenvandine, great, approved (but you need to change the mr status, I don't have access)14:05
kenvandinesure14:05
kenvandinethx14:05
jbichaattente: hey, maybe we should just talk here instead of on the MP :)14:14
jbichaattente: I think it's acceptable for Unity to depend on indicator-keyboard instead of gnome-control-center if the indicator-keyboard specific code only runs in Unity14:16
didrockskenvandine: why? there is a diff for it, it's how it detects it :)14:17
didrockskenvandine: I have an idea on how to show the triggering diff automatically in the future, but I would appreciate if you can fix it meanwhile :)14:18
Sweetsharkdidrocks: do we really need the MIR redtape to get libzip-dev into main? We can carefully examine if the source package is suitable for main, but in the end I would guess it is ... as the _source_ package is already in main.14:20
sil2100didrocks: can you ACK some packaging diffs ;) ?14:20
kenvandinedidrocks, will do14:22
didrockssil2100: can you get ken or cyphermox acking them? I have one request every 20s here :p14:22
sil2100;) If their ACKs count as archive admin's ACK, then no problem!14:22
* sil2100 wants to publish indicators14:22
sil2100They're mostly symbol cleanups and dependencies removals14:23
didrocks    libzip | 0.10.1-1.1 | saucy/universe | source14:24
didrocksSweetshark: the source is in universe, not main14:24
didrocksdid you check? ;)14:24
didrockssil2100: it's not an archive admin ack you need, just someone with upload rights for those :)14:24
Sweetsharkdidrocks: well, I did check, but in the maze of lp I didnt notice I was on precise ...14:25
attentejbicha, sure14:26
attenteseb128, you're ok with jbicha's solution?14:27
seb128attente, what solution is that?14:28
attenteto have unity depend on i-keyboard14:28
seb128sure14:28
cyphermoxsil2100: ack for ido14:28
seb128but the reason why I suggested to move the schemas is that you said gnome-settings-daemon needed it IIRC14:28
cyphermoxsil2100: ack for indicator-datetime14:30
sil2100\o/14:31
sil2100cyphermox: thanks!14:31
* sil2100 readies his cu2d-run14:31
Sweetsharkdidrocks: bug 119576114:31
ubot2`Launchpad bug 1195761 in libzip (Ubuntu) "[MIR] libzip" [Undecided,New] https://launchpad.net/bugs/119576114:31
cyphermoxack for indicator-power14:31
attenteseb128, sorry if i did, that was a mistake14:31
didrocksSweetshark: you did check that all build-deps and deps are in main for that one? :)14:31
cyphermoxI'm concerned that all those might not show up in the panel though14:31
seb128attente, ok, no worry, so yeah, unity depending on indicator-keyboard works for me (or Recommends as we do for other indicators)14:32
cyphermoxsil2100: yeah, all ack; but I'd install them locally first to make sure they really show... some indicators were converted to indicator-ng and I'm doubtful :)14:35
Sweetsharkdidrocks: its the same upstream release that was in main in precise. If it needs additional deps, I will club the one who did bring them in with a trout ...14:35
didrocksSweetshark: well, opening a MIR bug is not asking someone else checking the MIR criterias14:36
didrocksSweetshark: it's you doing the check, then someone else acking14:36
xnoxSweetshark: talk to infinity, i wouldn't have thought package requires mir at all, since it's same as in precise and still supported in precise and hasn't been changed.14:38
xnoxused to be a build-dep of kdeutils.14:39
didrockshave a good week-end everyone!14:59
didrockssil2100: enjoy your holidays :)14:59
pittidesrt: minidebug> no, not since we talked; I tracked down the missing ELF headers in coredumps for build IDs, which can help us to improve our debug symbols, but not minimizing existing symbols15:00
pittidesrt: I thought that wasn't necessary any more with your assertion msg changes in glib?15:00
sil2100\o/15:01
sil2100cyphermox: testing and publishing if all ok15:02
sil2100Seems ok, publishiiing!15:03
seb128pitti, did you get your menus to work?15:06
pittiseb128: I haven't rebooted since then, but I guess that was the problem15:07
seb128pitti, ok15:07
seb128sil2100, no no no15:08
seb128sil2100, did you publish indicators?15:08
sil2100seb128: yes...15:24
sil2100...regression?15:24
sil2100(Friday releases are really a bad idea15:25
sil2100)15:26
seb128sil2100, I guess so, did you try those15:27
seb128sil2100, I was just talking to charles and larsu an hour ago because I tried indicator-datetime trunk, custom items don't work in saucy15:27
seb128sil2100, e.g no calendar widget in the menu, no timezone, no color for appointements15:27
sil2100seb128: are there no integration tests for those?15:27
seb128I guess not15:28
seb128the items are there15:28
seb128just the calendar is a text line "[Calendar]"15:28
seb128rather than a calendar widget15:28
charlesseb128: I think all that's missing is a one-liner call to ido_init() so u-p-s will know to look for the custom widgets in IDO15:39
charlesseb128: so even though it looks terrible now, it should look less terrible RSN15:40
seb128charles, hum ok, do you know why that wasn't tested/added before those got merged in trunk?15:40
seb128charles, we just regressed saucy with that landing, going to be an issue and late friday work now for some of us to sort it out :-(15:40
charlesseb128: no I don't, I wasn't the one on that integration15:43
sil2100;/15:44
sil2100I think we need an integration test for that, at least a simple 'click the calendar indicator and check if it's visible'15:45
seb128sil2100, right, ordering of indicator is broken as well with those updates...15:45
sil2100charles, seb128: can we have someone fixing that? We might re-run the stack with the fix and release it today15:52
seb128sil2100, larsu is working on it15:52
desrtseb128: any progress on that gcc issue?15:55
Laneydesrt: doko says it's fixed15:57
desrtnice!15:57
Laneyhttps://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/119412315:57
ubot2`Ubuntu bug 1194123 in gcc-4.8 (Ubuntu) "[gcc-linaro wrong-code regression] gcc 4.8.1-2ubuntu1 to 4.8.1-3ubuntu1 breaks gtk on armhf" [High,New]15:57
seb128desrt, what Laney said15:57
Laneyactually maybe not, and it wasn't doko, but they think they know :P15:57
seb128well the flag they suggested fix it15:58
seb128doko said he was doing a build with the patch included15:58
seb128but he's off today15:58
seb128so we will see on monday15:58
Laneytoday is the day for system-settings MPs16:04
seb128Laney, seems so16:08
thotzHello Desktop-Team!  I would need help with this bug: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1153934 . I have spoken to the Bugsquad team, but they told me to go here... About 90 people are affected by this bug.16:17
ubot2`Ubuntu bug 1153934 in gvfs "Some radio streams which used to play OK don't play after updating to rhythmbox 2.98 or higher due a gvfs bug" [Medium,Confirmed]16:17
desrtseb128: do you want a new systemd-shim release to deal with that suspend-during-shutdown issue?16:43
desrtor are you OK to pick the change off master?16:43
seb128desrt, I'm ok picking the change, and thanks for reminding me16:44
seb128I did suspend my laptop in middle of shutdown again yesterday :p16:44
desrtsounds like an easy-to-reproduce test16:44
desrt:)16:44
seb128yeah, for me it's "shutdown, wait for the session to close, close the lid"16:45
seb128it shutdowns on the plymouth logo almost every time when I do that16:45
seb128it suspends*16:45
* desrt boggles at the fact that people use shutdown on their laptops16:47
desrtseb128: you could quickly confirm my theory about the bug by seeing if closing the lid immediately after shutting down causes a suspend or not16:49
desrtor if it open happens after 10 seconds (or not at all)16:49
seb128desrt, well, I close the lid when the user session close, that's a timeframe of 5-10s17:07
seb128would be easier to say with a 30s timeout :p17:07
seb128I might try to tweak that17:07
desrtseb128: i was wondering what happens if you click shutdown and then immediately close the lid17:07
desrtif you'd get an immediate suspend or not17:07
desrti suspect not17:07
desrtand if you do, there is some other problem here, probably not related to systemd-shim17:07
seb128ok, will try in a bit (doing upgrades and restarting session)17:08
* desrt goes to lunch17:11
sil2100larsu: ping17:11
sil2100larsu: any luck with fixing those indicator regressions?17:11
larsusil2100: yes17:12
larsufixing the ordering right17:12
larsunow17:12
larsuoh, your day is ending, eh?17:12
seb128desrt, enjoy!17:12
Laneyhave a nice weekend!17:21
* Laney is off to climb17:21
Laneyczajkowski: see you tomorrow!17:21
seb128Laney, thanks, you too!17:22
mlankhorstLaney: hah I did my horseback riding today already17:22
mlankhorst:>17:22
sil2100larsu: slowly, yes, but I can do the publishing tomorrow in the morning I guess17:23
larsusil2100: I'm stuck on unity's cmake right now17:23
sil2100larsu: could you send me an e-mail when it's done, informing which branches have those fixes?17:23
* ogra_ wonders if there are other places on a horse to ride on than the back17:24
sil2100larsu: so that I can re-run those17:24
seb128sil2100, larsu: I wouldn't bother about the order fix for today17:24
sil2100larsu: lukasz.zemczak@ubuntu.com17:24
larsuseb128: hm, okay.17:24
sil2100seb128: what about date-time? Is that done already?17:24
seb128sil2100, larsu: maybe just get the ido_init in it17:24
larsusil2100: I'll upload my patch for ido_init right now17:24
sil2100larsu: \o/ awesome17:24
seb128larsu, sil2100: what matters is that the stuff work, if the order changed that's an ok issue to have until next week17:24
sil2100Right17:25
seb128sil2100, the fix is in unity(-panel-service)17:25
larsusil2100: lp:~larsu/unity/call-ido-init17:25
sil2100hm17:27
sil2100That's troublesome then17:27
larsuhow so?17:27
sil2100Since we didn't release unity, as the integration tests aren't passing well enough ;/17:27
sil2100So I guess we won't be able to release that anyway today17:27
sil2100I only released indicators, as those were passing17:27
larsusil2100: the patch is trivial, it most likely apply on the latest released version17:27
seb128it does17:28
seb128I just applied it locally17:28
sil2100So maybe hm, maybe a manual upload with a quilt patch?17:28
seb128inline patch17:28
seb128but yeah17:28
sil2100Let's just merge the changelog entry into lp:unity when doing the manual upload17:29
seb128sil2100, do you want me to do the manual upload?17:34
seb128sil2100, hey?17:36
sil2100seb128: yes, since I have no permissions to do that17:36
sil2100I still don't have any upload rights ;/17:36
sil2100I can only operate scripts17:36
sil2100(jenkins-based)17:36
kenvandineseb128, i think those empty uploads of signon is because of the patch we are applying so we don't use the keyring on armhf17:38
seb128cd ..17:38
seb128ups17:38
kenvandinehehe17:38
seb128kenvandine, merge the patch in trunk?17:38
kenvandineno... that'll break the desktop17:38
* kenvandine has no idea how to deal with this...17:39
seb128kenvandine, I guess I don't understand the issue, the source is the same for all archs in the package for sure?17:40
seb128why would it be different in trunk?17:40
kenvandinebecause we apply a patch to use the keyring on both i386 and amd6417:40
kenvandinebut we use the default on armhf17:40
kenvandinewe could flip it17:40
kenvandinemerge the patch into trunk17:40
seb128oh, I see, yeah...17:41
seb128larsu, sil2100: https://launchpad.net/ubuntu/+source/unity/7.0.0daily13.06.24-0ubuntu217:41
kenvandinethen patch on armhf to disable the keyring17:41
seb128right17:41
larsuseb128: thanks!17:41
kenvandinebut that'll complicate maintaining trunk...17:41
seb128larsu, thank you for the fix!17:41
kenvandinesince LP's trunk for signon isn't upstream17:41
* kenvandine hates that this stuff is on google code17:41
seb128kenvandine, oh, right... wait monday and see with Didier I guess17:41
kenvandineand upstream doesn't want to change the default to keyring17:42
kenvandineyeah...17:42
=== EvilAww is now known as EVILAWW
sil2100seb128: thanks! :)17:50
seb128sil2100, can you take care of merging the diff back in trunk?17:50
seb128sil2100, http://launchpadlibrarian.net/143672596/unity_7.0.0daily13.06.24-0ubuntu1_7.0.0daily13.06.24-0ubuntu2.diff.gz17:51
seb128sil2100, one larsu's merge is approved/in that should be only the changelog entry to merge17:51
sil2100seb128: ok18:13
sil2100Will merge that in18:13
larsuseb128: ordering patch is done, but needs a new libindicator. I guess it's not very urgen, I'll go through the usual MR channels18:20
larsu*urgent18:20
sil2100larsu: did you MR the unity fix?18:24
larsusil2100: I'm doing a last test of everything, will MR in the next 5 minutes18:25
sil2100larsu: ok ;) If anything, my MR question was for the calendar fix (ido one)18:26
larsusil2100: I'll put them both in the same MR, they're small enough18:27
sil2100ok18:35
larsusil2100: https://code.launchpad.net/~larsu/unity/call-ido-init/+merge/17212718:40
=== hggdh_ is now known as hggdh
larsusil2100: don't merge yet though, it depends on a libindicator change (I'll try to get that in asap)18:41
sil2100If this depends on the indicator change, might be good that we change the debian/control dependency too18:42
larsuI did18:42
sil2100Awesome18:42
larsu;)18:42
sil2100I need to pop out now, but I'll be back later and try dealing with that18:42
sil2100Thanks :)!18:42
larsusil2100: enjoy your evening, thanks for sticking around18:42
seb128qengho, there?19:22
qenghoseb128: indeed.19:23
seb128qengho, hey19:23
seb128qengho, I just got the new chromium in saucy today, is it supposed to prompt about webapp on every single website I browse?19:23
seb128(beause it does)19:24
jbichaseb128: bug 119498619:24
ubot2`Launchpad bug 1194986 in chromium-browser (Ubuntu) "Chromium 28.0.1500.52 doesn't auth webapps. "Unity WebApps plugin needs your permission to run"" [Undecided,Confirmed] https://launchpad.net/bugs/119498619:24
mdeslaurseb128: it's to annoy you into switching back to firefox :P19:24
seb128mdeslaur, ;-)19:25
seb128mdeslaur, that has another advantage, I can nag chrisccoulson about my bugs then :p19:25
sarnoldmdeslaur: hunh, and I thought the firefox door-hanger flash annoy-o-tron was to annoy us into switching to chromium...19:25
seb128jbicha, thanks19:25
mdeslaursarnold: hah! the _what_?19:26
qenghoseb128: yes. That is, webapps patches haven't applied lately, and #security wanted to close a bunch of CVEs even if it shows an ugly bar. I am right now working on updates to hide the question bar.19:26
seb128oh, I guess qengho is going to join chrisccoulson on the "hate webapps" line ;-)19:26
chrisccoulsonlol19:26
chrisccoulsonhi ;)19:26
seb128chrisccoulson, hey! how are you?19:26
seb128qengho, oh, also still not menus in chromium in saucy :/19:27
seb128qengho, weren't you supposed to include that tiny patch to unbreak those?19:27
* seb128 does need the menus a lot but they can be handy sometime19:27
seb128doesn't*19:28
sarnoldmdeslaur: visit this: http://git.io/D9wjFQ19:28
sarnoldmdeslaur: note the hateful little doorhanger asking if you want to run flash19:28
mdeslaurhrm, nope19:29
jbichasarnold: what version of Firefox are you on?19:29
chrisccoulsonseb128, yeah, i'm good thanks. how are you?19:29
sarnoldjbicha: 22.019:29
seb128chrisccoulson, tired, it's friday evening, I need a beer! but good otherwise ;-)19:29
qenghoseb128: Yeah, I was.  Let me talk to attente about it.19:29
sarnold22.0+build2-0ubuntu0.13.04.119:29
mdeslaursarnold: I think you have a security issue there...I don't have any flash on that page19:29
jbichasarnold: are you going to install flash then? ;)19:29
sarnoldjbicha: I've been thinking of uninstalling flash, that doorhanger is fscking annoying19:30
chrisccoulsonmdeslaur, i do19:30
attenteqengho, hey, how's it going?19:30
chrisccoulson(note, i'm running nightly, and it tells you when there's flash on a page now, even when you haven't blocked it)19:30
mdeslaurah19:31
chrisccoulsonmdeslaur, https://twitter.com/chrisccoulson/status/35029191402258842119:31
seb128jbicha, read your comment on eds/goa issue ... can you at least upstream a bug report?19:31
sarnoldmdeslaur: do you have click-to-play turned on? I think I read somewhere that it might only show if click-to-play is there...19:31
mdeslaursarnold: since I have no idea what that is, I'm guessing 'no'19:31
qenghoattente: Hey.  Remember the menu-bar patches for chromium.  I'm not sure I can wait any more on The Right Way.19:31
sarnoldmdeslaur: hah. about:config -- plugins.click_to_play19:32
seb128qengho, didn't you guys agree shipping the non-right-way temporary in saucy?19:32
mdeslaursarnold: well, there you go! now you know how to fix your issue :)19:32
jbichaseb128: you want upstream to split the goa part of libgdata into a separate .so right?19:32
sarnoldmdeslaur: before firefox 21 or something click_to_play made the web a far less sucky place. but then around firefox 21 they added the "firefox doorhanger" modal dialog box to piss me off.19:33
seb128jbicha, if that's what we need to make e-d-s+uoa not pull in goa, yes19:33
attenteqengho, i thought we agreed to use that patch until i have time to do The Right Way?19:33
seb128jbicha, what I want is no goa when uoa is used19:33
qenghoseb128: Maybe we did. :\  I'll see what I can do now.19:33
seb128jbicha, you probably want the reverse ... so what we want is a runtime choice between those19:33
jbichaseb128: yeah now you have the opposite of my problem :)19:33
seb128qengho, the patch is trivial, just sneak it into the next saucy upload (only in saucy)19:34
sarnoldmdeslaur: I'm just afraid that I'll just as annoyed once I uninstall flash and all these annoying websites want me to load their plugin for the best browsing experience19:34
chrisccoulsonsarnold, yeah, the idea of click-to-play is that it's only meant to appear for blacklisted plugins19:34
chrisccoulson(ie, everything that isn't the latest version of java or flash)19:34
qenghoattente, seb128, okay, I'm going with what I have.  Thanks.19:34
attenteqengho, thanks19:34
seb128qengho, thanks19:34
AlanBellballoons: I am completely confused by the QA test tracker tool, are there some instructions on how to submit testing results?19:34
jbichachrisccoulson: clicktoplay for even the latest flash was a pretty cool feature though19:35
balloonsAlanBell, yes there's some lovely links in the notice board now for help19:35
balloonshttp://packages.qa.ubuntu.com/19:35
chrisccoulsonsarnold, but there is a new UI in the current nightly to allow you to disable plugins per-page, via an icon that appears on the navigation bar19:35
sarnoldchrisccoulson: WANT!19:35
balloonsAlanBell, specifically it points here: https://wiki.ubuntu.com/Testing/Cadence/Walkthrough19:35
sarnoldchrisccoulson: don't get me wrong, click to play was great, I often knew which of the ten flash things I wanted to run :)19:36
chrisccoulsonsarnold, did you see the twitter link i posted a few minutes ago?19:36
sarnoldchrisccoulson: yeah19:36
chrisccoulson(although, it looks unfinished atm)19:36
sarnoldchrisccoulson: but it was confusing.19:36
balloonsAlanBell, there's video too if you'd like; http://www.youtube.com/watch?v=fw7SrLUzW6U19:36
chrisccoulsonheh19:36
AlanBellballoons: so from this page, http://packages.qa.ubuntu.com/qatracker/milestones/298/builds/47541/testcases/1572/results where do I go? that doesn't look like the stuff in the documentation19:36
balloonsAlanBell, ahh.. you need to login..19:38
balloonsalso it appears that link is linking to the archived result, not the active one; http://packages.qa.ubuntu.com/qatracker/milestones/298/builds/47622/testcases19:38
AlanBellhmm, I am, it says Hello alanbell in the title bar19:38
AlanBellooh, that link has actions :)19:38
balloonsyea, I'm sorry about that. bad link on my part19:39
balloonswhere did you find it.. let me make sure it's fixed :-)19:39
AlanBellbut only passed with no bugs, subscribe and unsubscribe19:39
balloonswell those are quick buttons you can use.. you see Mir has 1 testcase called xMir19:39
balloonsin the future we'll add more19:40
balloonsso more now, click xMir and run through that test19:40
AlanBellhttp://www.theorangenotebook.com/2013/06/mir-joins-cadence-testing.html run through the test cases link19:40
balloonsAlanBell, great ty19:40
AlanBellgot it, thanks19:40
balloonsAlanBell, I updated that hotlink from the blog to take your straight ito the xMir tests so hopefully people aren't as confused :-)19:42
AlanBellgreat19:42
AlanBellhow does one file a bug against it?19:42
AlanBellubuntu-bug xmir won't work as it is in a ppa19:42
balloonshttp://packages.qa.ubuntu.com/qatracker/milestones/298/builds/47622/buginstructions, which appears blank.. let me fix that too :-)19:43
AlanBellyeah, I did look there first ;)19:43
balloonsyou'd think it was friday or something :-)19:43
AlanBellon the plus side I am using xmir right now19:44
AlanBellmultimonitor doesn't work and there are a few input problems19:44
balloonsmind filing a bug for multimonitor?19:46
balloonsthat way others will know it's broken as well and you can link it into the result :-)19:47
AlanBellyeah, will do when I know how :)19:47
balloonsAlanBell, bugs are here: https://bugs.launchpad.net/mir/+bugs19:47
balloonslol, I'm working on that part19:47
balloonshttps://bugs.launchpad.net/mir/+filebug19:47
balloonsok, page is updated.. Many thanks AlanBell for doing a QA on the test itself, haha!19:48
balloonsAlanBell, this might be interesting to you also: https://blueprints.launchpad.net/ubuntu/+spec/client-1310-mir-multimonitor19:49
AlanBellhmm, might be mostly hotplugging monitors that is broken19:49
jbichachrisccoulson: if I enable clicktoplay in about:config, I get an extra Activate Plugins entry in Page Info>Permissions; it shows the GNOME Shell plugin but not Flash; why does Flash get special treatment there?19:49
balloonsAlanBell, thank you for the report and feedback ;-)19:56
balloonsarmed with your knowledge starting at the homepage, http://packages.qa.ubuntu.com/, do you see how to test and report for the other packages we're tracking?19:56
AlanBellballoons: yeah, it makes sense starting from there, just that archive link was kinda confusing20:10
balloonsI wonder if we do more harm than good starting people directly at the test20:10
AlanBellballoons: one thing that is a pain is you can't get from here http://packages.qa.ubuntu.com/qatracker/testcases/1572/info to the form to fill out your results20:12
AlanBellooh, alt-left is bad with xmir20:13
AlanBellwhich doesn't help with the qa tracker as you have to go back from the test details to get to the reporting form :)20:13
balloonsAlanBell, see the toggle where it says testcase?20:16
balloonsclick that.. that's the actual testcase your intended to see20:16
AlanBellnot seeing a toggle20:20
AlanBellah, that bit :)20:20
AlanBellballoons: you might want to add the instructions on how to disable xmir somewhere20:22
balloonsAlanBell, found that bit eh?20:22
balloonsinstall/uninstall should be covered by the link20:22
balloonsthat's straight from the team20:22
balloonshmm.. they don;'t have uninstall up20:23
balloonsOk I'll manually write instructions20:23
balloonsAlanBell, done http://packages.qa.ubuntu.com/qatracker/milestones/298/builds/47541/downloads20:30
=== Amaranthus is now known as Amaranth
AlanBellballoons: I was actually thinking of commenting out type=unity in /etc/lightdm/lightdm.conf.d/10-unity-system-compositor.conf21:10
AlanBellrather than completely uninstalling it21:10
balloonsAlanBell, ahh.. well heh, that's interesting but more complex21:10
AlanBellsee Turning Mir on & off temporarily http://www.olli-ries.com/running-mir/21:10
balloonsOk, hmm.. I'll add that as an option21:11
balloonsty!21:11
ollimhall119, AlanBell https://blueprints.launchpad.net/ubuntu/+spec/client-1310-mir-multimonitor21:30
mhall119thanks olli21:33
AlanBellthanks olli I look forward to further multi monitor testing :)22:31

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!