[00:00] Yep that they do. [00:01] * TheMuso has left them out of his resistance exercise routine since pulling a muscle a few weeks back. Should probably look at how I was doing them and start doing them again... [00:02] I did a boot-camp style collective execrsise thingy yesterday evening, which included the first pushups I've done in… more than a decade? [00:03] Needless to say, my arms are somewhat surprised. [00:08] RAOF, pushups are supposed to exercise your chest! [00:09] RAOF, robert_ancell, TheMuso ... I've been on the phone for the last 3 hours solid! [00:09] But I've got weedy arms, atrophied after years of being asked to do little more than type :) [00:09] have not had a moment to prepare for the Easter Edition :( [00:09] RAOF, then more pushups!! [00:09] give me 10! [00:09] j/k [00:09] rickspencer3, that's a lot of phoning... [00:10] robert_ancell, want to switch jobs? [00:11] nope [00:12] lol [00:12] RAOF: I actually like that feeling when your limbs have been worked out more than they are used to. [00:14] Eeeh. [00:14] The flaccitude isn't bad; it's the soreness that's not my cup of tea. [00:16] software engineers complaining about exercise [00:16] who would have thought :) [00:16] RAOF, robert_ancell, TheMuso: https://wiki.ubuntu.com/DesktopTeam/Meeting/2010-08-31 [00:16] I added the irc logs to the bottom [00:16] Not just exercise — *unaccustomed* exercise. :P [00:20] heh [00:20] * TheMuso has been exercising regularly for a while now, so doesn't find it difficult to do, and can deal with the discomfort. [00:21] I reckon I could have _run_ for that 45 minutes, no problem. [00:21] Well, jogged. [00:21] I like the bug summary from pedro [00:23] It'd be nice if glib backtraces didn't almost uniformly end in g_closure_invoke () :) [00:23] heh [00:24] looks like Twitter is going to be a mess for users starting tomorrow [00:24] RAOF, can you do me a favor? [00:24] add a section o xorg-xserver to the meeting wiki? [00:25] maybe about mesa? [00:25] Sure thing. [00:25] To the template, as well, or just a one off? [00:25] RAOF: Why is twitter going to be a mess? [00:25] TheMuso: I presume because they've turned off our authentication method. [00:26] oh... [00:26] * TheMuso wonders whether pidgin's microblogging plugin will also be affected. [00:26] * TheMuso uses it for twitter. [00:26] RAOF, adding it to the template would be good [00:26] 10/4 [00:27] TheMuso, yeah, pidgin may be [00:27] (impacted, that is) [00:27] RAOF: I have the latest backported in my PPA [00:27] 0.3 [00:28] RAOF: it's in the changelog for 0.3 that it's fixed, we should probably pull that fix and SRU it [00:28] rickspencer3: I'll find out soon enough. [00:28] oops [00:28] right [00:28] meant to tell TheMuso [00:28] :) [00:29] micahg: Yes we should, or perhaps even get that fix in post beta. [00:29] ok, so, having read the logs, any questions, anything to add? [00:29] Nope. [00:29] TheMuso: version in maverick is fine, Lucid needs an SRU [00:29] There is one nasty audio bug I am trying to get a handle on, which appears to be a race somewhere... Let me fetch the bug number. [00:29] No questions here. [00:29] micahg: oh ok. [00:29] * micahg is sorry for interrupting the meeting :) [00:31] TheMuso: Incidentally, logging on this morning _also_ has the volume set correctly. [00:32] bug 592016 [00:32] Launchpad bug 592016 in pulseaudio (Ubuntu) "[Maverick] Sound is always muted on startup; unmuting makes the volume at lowest level (affects: 27) (dups: 2) (heat: 136)" [Undecided,Confirmed] https://launchpad.net/bugs/592016 [00:33] RAOF: Right, which is why I think its a race somewhere... Another box I have here which is rather new doesn't exhibit the problem. My desktop needs a cleanup/fresh install, which I intend to do today, to see whether the problem still exists. [00:36] But that doesn't help those who upgrade. [00:36] Anyway, investigation is ongoing. [00:43] Well that killed the conversation. :p [00:44] TheMuso: should I try to make that SRU for pidgin-microblog for Lucid? [00:45] micahg: If you like, I am not in a position to test it currently, since I don't have lucid installed. [00:46] TheMuso: I'm on Lucid until Thursday night, but I don't have a twitter account :) [00:46] ah ok [00:46] TheMuso: I can post something on identi.ca calling for testing [00:47] I only raised it since I use pidgin microblogging. [00:47] But sure that sounds reasonable. [00:47] TheMuso: yeah, I have to look into another SRU for zend-framework for the same issue [00:47] ah ok. [00:48] debian had a whole list of related updates a while back for this issue as well [00:48] Ok. [05:49] Hello. Ihave a laptopn - AMD Sempron2800+ .755 GH and 640 RAM. Yeah it's old and XP takes forever to boot. Can I put Ubuntu on this with reasonable performance? Do I use Desktop or Netbook version. Thanks [05:52] matthewopersico: Please go to #ubuntu for support, this channel is used for development discussion. [05:52] thanks [05:53] bye [06:21] TheMuso: the oauth stuff for pidgin-microblog is multiple patches, looks too messy for an SRU unless we can just push the new version [06:21] micahg: right, thats a pain. [06:22] TheMuso: so, what should I do? the app isn't totally useless, just for twitter :-/ [06:22] micahg: Hrm I am not sure at this point. [06:22] * micahg can ask pitti when he comes in [07:18] Good morning [07:18] micahg: what's up? === ara_ is now known as ara [07:19] micahg: pidgin-microblog? it's a leaf package, so regressions in it don't cause trouble in other packages, so if it's currently FUBAR, then a new version sounds fine [07:19] pitti: so, twitter just swithced their auth to oauth and I think they turned off the other authentication, pidgin-microblog in Lucid will not be able to connect to twitter if this is the case, maverick is unaffected since it has a newer version where this was fixed, the SRU would be multiple upstream commits which seems messy [07:20] micahg: right [07:20] pitti: well, it's just twitter, identica and facebook should still work [07:20] pitti: if you think that's worth a new version, I'll file the bug [07:22] micahg: ah, so we need to test those for regressions; how much stuff does the new version touch outside of twitter? [07:24] * micahg is looking [07:30] pitti: most of the fixes are for oauth, the release log mentions changing identity of identi.ca and status.net [07:38] RAOF: Ok, after a fresh install on my desktop, I am no longer getting audio muted after reboot. Something changed somewhere that fixed it, which doesn't seem to be overwritten on upgrades for some reason... Need to test with my laptop which has an install from alpha 2 or so. [07:38] * TheMuso sighs. I hate these kind of bugs. [07:38] Yup. [07:42] * RAOF needs to hunt for another jug-plug to fire up a new buildbox [07:43] jug-plug? [07:43] You know - three-prong, roughly rectagular female AC → device connector. [07:43] IE: power plug. [07:44] Why are there always more power supplies than cables to plug _into_ power supplies? [07:44] “vgapi_tmp.h:386: error: expected declaration specifiers or ‘...’ before ‘VGloat’” [07:44] Hm. That _may_ have been a typo :) [07:45] RAOF: oh yeah I gotcha. I got heaps here. [07:47] Hm. If mesa used autotools, like nature intended, the build process wouldn't have to copy the source tree 6 different times. [07:49] lol [08:01] good morning [08:03] morning everyone [08:07] good morning and471, mvo [08:07] hey didrocks [08:08] hey didrocks and and471! [08:09] hey and471 :) [08:11] and471: stop speaking to yourself :) [08:12] oh damn it... [08:12] hey mvo :) [08:12] thanks didrocks XD [08:13] no worry ;) [08:21] mvo, good morning [08:21] mvo, did you read http://mairin.wordpress.com/2010/09/01/a-story-about-updates-and-people/ ? [08:22] zyga: its a very sensible post :) [08:23] zyga: no, let me do that now [08:23] nigelb, yes, I agree [08:23] I really want that in ubuntu [08:23] Hm. I think the OOM killer just killed my mesa build. Odd. [08:23] as soon as I got to that picture at the end of the post it struck me [08:23] how obvious the message is [08:24] zyga: heh :) funny how close the distros really are. there is a plan of action (and471 is currently working on that) to have the updates presented in a much more condensed form similar to the one outlined here [08:24] :) [08:24] zyga: personally I would rather install the updates in the background and not show a UI at all [08:25] (unless the user wants to see one, I'm sure there are users how do) [08:25] mvo, I somewhat agree but IMHO you _should_ notify the user that "platform upgrade 2010-09-01" was just installed, with optional details to show [08:26] mvo, there are cases where the user will care about an update (such as ff being updated to version 4.0 say in maverick...) [08:27] zyga: not happening :) [08:27] but the ultimate simplicity of "system update to version FOO" vs bazillion of libsexy and other funky names being updated is IMO worthwhile [08:27] 4.1 maybe ;) [08:27] micahg, ok but the point stands [08:27] micahg, but honestly I agree that it's a rather rare event (that the user will care about a particular software being updated) [08:27] right, we need to discuss the presentation of it and whether or not to turn it on by default etc. I have a basic branch here lp:~mvo/unattended-upgrades/minimal-steps-upgrade, it will ensure the system is upgraded in baby steps so that e.g. on shutodwn it just needs to finish a small transaction and not have to wait for the full upgrade to finish [08:28] zyga: I imagine it will be something like a dialog "a update is available\n [x] install in the background automatically from now on\n [install] [cacnel] [08:28] mvo, I heard about that, it's good too, people some people expect the system to update when it's turning off just because windows does that [08:28] mvo, I'd put that in the installer (yay) and never ask the user [08:29] mvo, especially for users who cannot update themselves and just use the account [08:29] good idea [08:29] (and only show the UI you just described if the user rejected the installer opt-in) [08:29] putting it in the installer makes a lot of sense [08:30] we had a long discussion about install on shtudown and it does not make that much sense for all package, for some like ff that break when installed while ff is running maybe, but not for all of them [08:31] mvo, right but mere downloading does not annoy users much, their system misbehaving (ff upgrade, got bit by that myself) and slowing down unexpectedly is something different [08:31] mvo, although laptop use case worries me a little [08:31] mvo, I don't like when my system is updating when I'm on battery and want to just shut down [08:32] yeah, we need policies for all of this, not on battery, add flags to apps that break (like ff and OOo) [08:34] mvo, is it safe to hibernate after a kernel change? [08:34] * zyga reads "10_unattended-upgrades-hibernate" [08:35] zyga: iirc it just halts the shutdown until all the upgrades are installed (or a timeout is reached) [09:09] hey [09:18] morning [09:35] mvo - i'm seeing a lot of bugs like bug 627879, any idea whats happening there? [09:35] Launchpad bug 627879 in ubufox (Ubuntu) "package ubufox (not installed) failed to install/upgrade: no package named `ubufox' is installed, cannot configure (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/627879 [09:35] ubufox is now a transitional package that pulls in xul-ext-ubufox [09:36] and xul-ext-ubufox declares a breaks and replaces on ubufox (<< 0.9~rc2-0ubuntu3) [09:41] chrisccoulson: ok, I have a look. this is maverick, right? [09:42] mvo - yeah, this is on maverick [09:42] thanks [09:43] hey chrisccoulson mvo [09:43] how are you? [09:43] hi seb128, i'm good thanks. how are you? [09:44] I'm fine thank you [09:44] it feels quiet with the beta freeze ;-) [09:44] chrisccoulson: three cheers to dpkg ;) "(Noting disappearance of ubufox, which has been completely replaced.) [09:44] " [09:44] chrisccoulson: that confuses apt slightly - actually apt should nowdays be able to cope [09:45] mvo - nice! should i assign this bug to apt then, or is there something i can do in ubufox? [09:45] chrisccoulson: but apparently it is not. as a workaround, you should keep a single file in the ubufox package so that the package still exists. [09:45] ah, usually the transitional packages still have some documentation, which might be why this hasn't happened before [09:45] chrisccoulson: for a immediate fix I would suggest to change the transitional package to still own a single file and we can clean it up via the uprader and/or computer-janitor [09:46] chrisccoulson: yeah, we had those cases before, but they are rare. a bug task for apt would still be nice as it seems like the code that deals with the condition does not quite work [09:47] mvo - ubufox is still shipping a changelog in /usr/share/doc/ubufox. shouldn't that be enough? [09:51] chrisccoulson: that should be enough, but does xul-ext-ubufox ship the same file maybe? [09:51] seb128: hey! good, thanks :) [09:53] mvo - it doesn't seem so (xul-ext-ubufox ships a changelog in /usr/share/doc/xul-ext-ubufox) [09:53] although the changelog in ubufox is a symlink [09:54] but it still ships its own copyright file too [09:57] chrisccoulson: hm, looking [10:02] didrocks, hi, could you please add a "-" in front of the autoreconf include in d/rules of evolution? [10:02] fta2: why? we haven't done that in any package [10:04] chrisccoulson: the messages not make a lot of sense either, the terminal log does not contain a trace of "xul-ext-ubufox" [10:05] mvo - hmmm, yeah, that is a bit strange [10:06] I run a upgrade test now to see if I can reproduce [10:07] is this the place to discuss indicator-applet bugs or was there a dedicated channel? [10:07] tjaalton, you can use #ayatana [10:07] seb128: thanks [10:08] though most people active on it are on the other side of the atlantic and still sleeping [10:08] meh :) [10:09] it seems that having $HOME on NFS and logging simultaneously from two computers makes the logout applet fail on the second session [10:09] on lucid at least [10:10] so normal users can't log out, or is there another way? [10:10] I guess you should talk to tedg about it when he's online [10:10] yeah, I will [10:11] didrocks, this include is not part of the regular dev packages, it needs a special build-dep, so the "-" prevents unnecessary failures (like if you repack, the clean rule runs, but fails on this missing include, while it's not really needed unless you actually build) [10:11] didrocks, (and i have to repack evo each time there's an update to add some patches) [10:12] fta2, the package build-depends on what is required [10:12] why not just installing the build-depends? [10:13] fta2: it's added to the build-dep, and debian is doing the same [10:14] seb128, on my servers, i have build-essential, but dh-autoreconf is not part of it, and it drags even more deps. otth, it's not really needed to just create a source package [10:14] seb128, didrocks: i'm not saying it's a bug [10:15] seb128, didrocks: just that it could be friendlier with a "-" [10:16] I get what you mean now [10:16] you don't build the package just the source [10:16] I guess you can just scp the file which is include on your server [10:16] included [10:17] it should not run any actual command when building the source [10:17] oh ok, for the building the source, right [10:26] seb128, do you know about bug 539025? I'm doing the gnome-settings-daemon update and the svgs have changed but not due to the upstream bug. I've updated the patch to have the same .svgs as in 2.30 but I'm not sure if we use those ones or the 2.31 ones. Damn svgs don't diff well... [10:26] Launchpad bug 539025 in gnome-settings-daemon (Ubuntu) (and 2 other projects) "Touchpad on/off notification uses icon from one canvas source svg than a 48px icon (affects: 1) (heat: 20)" [Low,Fix released] https://launchpad.net/bugs/539025 [10:26] hey robert_ancell [10:27] robert_ancell, what svg changed? [10:27] touchpad-disabled.svg and touchpad-enabled.svg [10:27] I don't get the bug report, but you did the upload :) [10:28] robert_ancell, oh, the bug is easy [10:29] robert_ancell, get the current source [10:29] robert_ancell, open touchpad-enabled.svg with eog [10:29] the upstream source one [10:29] yup [10:30] robert_ancell, it's not an icon, it's the source canvas [10:30] that doesn't look nice in notify-osd ;-) [10:30] the patch was replacing that by one icon [10:30] ie eog /usr/share/icons/hicolor/scalable/actions/touchpad-enabled.svg [10:31] oh, I see (looked at the old one with all the patches removed). ok, it is fixed then [10:31] robert_ancell, that's fixed in 2.31.6 [10:31] right [10:32] robert_ancell, http://git.gnome.org/browse/gnome-settings-daemon/commit/?h=gnome-2-32&id=671a75847ac2ba918c3905c6f48062c5dd024967 [10:32] robert_ancell, that fixed it [10:33] ah, was looking at that commit, but wasn't sure if it was linked to the bug report [10:33] robert_ancell, btw do you install the new service? or should we just not ship it for this cycle? [10:33] I think we should just not ship it [10:33] it seems we would not win anything to get it [10:33] not ship it [10:33] the new gnome-panel uses it but since we don't do that update [10:33] ok, excellent [10:34] robert_ancell, did you get my email about vte btw? [10:34] oh, I still can't get anjuta to compile properly - if you're interested the libgda4 in bzr works, but I can't compile anjuta from git, there's some gir problem I can't work out [10:34] ok, I will give it a try [10:34] I will also review the brasero update [10:35] did you ask upstream why they hardcode the gsettings backend? [10:35] there were a bunch of srcdir != destdir bugs which are now fixed upstream [10:35] yeah, it was just for debugging, it's been removed now [10:35] ok [10:35] remind me of the vte email [10:35] robert_ancell, bug #626979 [10:35] Launchpad bug 626979 in vte (Ubuntu Maverick) (and 1 other project) "pkg-config --variable=includedir points at /usr/include, not /usr/include/vte-0.0 (affects: 1) (heat: 6)" [High,Fix committed] https://launchpad.net/bugs/626979 [10:36] ups, you fixed it [10:36] seb128, yes, it's fixed [10:36] I'm lagging behind on bug emails [10:36] tell me about it :) [10:36] ;-) [10:36] robert_ancell, great work on the updates btw [10:37] do we have any issues with the latest gnome updates? Do they bypass the UI freeze? (some were late because the 2.31 series was only GNOME3 compatible) [10:37] I've mostly let those to you this week, I'm focussing on getting bugs under control [10:37] sure [10:37] no issue [10:37] it's just that they will only go in after beta [10:37] but there is no need of any freeze exception [10:37] cool [10:38] robert_ancell, you are still there next week right? [10:38] yes, I'm flying out Saturday [10:39] ok [10:39] I guess this week will be busy with updates mostly [10:39] but I will have a buglist built by end of week [10:39] I really started on it yesterday [10:39] I've added maverick tasks for now [10:39] rodrigo_, uploading a new g-c-c just after I update to the last one!! :) [10:40] but I should probably use the topic url again [10:40] robert_ancell, hehe ;-) [10:40] ie using desktop-bugs as well [10:40] robert_ancell, sorry, I should have done it on Monday :) [10:40] seb128, yes, that's where Iook mostly. We have too many bug trackers. We need a "top 100" bugs or something. We need a pedro on the team to keep that updated... [10:41] right [10:41] I got pedro to join our weekly meeting and build some hot bug lists [10:41] that's a start [10:42] yeah, I was reading that, +1 from me! [10:42] but I've difficulties to build an easy list [10:42] between bugs assigned to the team [10:42] bugs assigned to team members [10:42] bugs milestoned [10:42] bugs with a maverick task [10:42] etc [10:44] sure, it's not an easy problem [10:44] I think I will keep abusing desktop-bugs for now [10:45] ideally we would have a way on launchpad to list bugs against the desktop set with a maverick task [10:45] but we don't right now [10:45] why not make desktop-bugs-maverick? [10:46] tags? [10:47] yeah, maybe. I haven't really thought it through. You really want it to be automatic as when we go to N it would be a pain to manage [10:47] no reason to not to, out of the fact that it adds an extra step [10:47] I think we should rather have some script build a webpage [10:47] ie something doing a query of all maverick tasks in the desktop set [10:48] using launchpadlib [10:48] so we would just have to deal with nomination the normal way [10:48] not to deal with extra teams or tags [10:48] LP needs a reports function like bugzilla. That's got to be about the only feature I miss :) [10:48] sort of http://qa.ubuntu.com/reports/ [10:49] ie http://qa.ubuntu.com/reports/team-assigned/canonical-dx-team-assigned-bug-tasks.html [10:49] but that's for a team and it's member [10:49] is that using lplib, or directly accessing the backend? [10:49] but having the same for a desktop, ie desktop bugs, would be nice [10:49] I think those are json queries running in the dc [10:50] (and why not http://qa.ubuntu.com/reports/team-assigned/canonical-desktop-team-assigned-bug-tasks.html ?) [10:50] direct access to the database is required if you don't want to spend a day [10:50] didrocks, what about it? [10:50] didrocks, oh the url? that's the first that showed in my firefox autocompletion, I wanted a random example [10:50] seb128: ok ;) [10:51] anyway, gtg, see you guys later [10:51] robert_ancell, I think the easier would be to build a json query and hand it to qa [10:51] robert_ancell, bye [10:51] robert_ancell, I will try to do that [10:51] robert_ancell, see you tomorrow! === MacSlow is now known as MacSlow|lunch === bilalakhtar_ is now known as bilalakhtar [12:21] seb128: about evolution-mapi, trying to update it to 0.30 (0.32 ask for evolution 2.32). This version asks for libmapi 0.9 (openchange), which depends on new samba4 (we are in alpha8 in universe and we need a newer alpha13) [12:22] seb128: debian experimental has both new openchange and samba4, I'm talking to jelmer about the change and he seems ok regarding stability (it's an alpha against another alpha :-)) [12:23] installed, tried and evo-mapi doesn't compile because of what seems an API breakage in libmapi [12:23] tracking this with jelmer right noww and openchange upstream, but we may not have the latest one finally in maverick [12:24] apart from that, the rest of the new evo stack is ready. Will push later today [12:32] didrocks, ok [12:32] didrocks, you manage to get the pop bug fixed? [12:33] seb128: yeah ;) [12:34] didrocks, what was it? something they fixed in 2.32 since they didn't have the bug? [12:35] seb128: it seems to be fixed in 2.32 because they added a new property for frames in the dialog like "E_PROP_STEP_CONTINUE". I have workaround the issue differently in 2.30 has taking this property made too many files to patch [12:36] ok [12:36] didrocks, great work ;-) [12:36] thanks seb128 :-) [12:56] salut === MacSlow|lunch is now known as MacSlow [13:20] good morning everyone [13:22] hey nessita, feeling better? [13:22] didrocks: yes, a lot, thanks for asking! [13:23] hey nessita [13:23] hey seb128 [13:23] nessita, nice to see that you are better ;-) [13:23] :-) [13:36] kenvandine, ping [13:42] andreasn, pong [13:43] kenvandine, you're a gwibber dev, right? [13:43] (note, this is not a question about twitter, figured that out already ;) ) [13:43] yes [13:43] :) [13:44] I'm getting a bit confused by this dialog: http://www.andreasn.se/diverse/temp/display-notifications-when.png [13:44] when does it display notification exactly? [13:44] yeah, we should hide the second checkbox unless you enable them [13:44] always or for mentions, replies etc? [13:44] always if the second one isn't checked [13:45] if the second one is checked, only for mentions/replies [13:45] right [13:45] or maybe a radiobutton [13:45] i just noticed yesterday that was confusing [13:45] like: [13:45] ( ) display notifications for all messages [13:45] (o) display notifications for mentions, replies etc. [13:45] ( ) don't display notifications [13:46] that would be good [13:46] I think there might be a way to shorten it, let me see if I can find a doc writer [13:46] hehe [13:46] cool [13:46] thx! [13:47] seb128: ping, re #612988 [13:47] bug #612988 [13:47] Launchpad bug 612988 in ubuntuone-client (Ubuntu Maverick) (and 2 other projects) "[nautilus] ubuntu-one ribbon in folders is too obtrusive (affects: 8) (dups: 2) (heat: 58)" [Medium,Triaged] https://launchpad.net/bugs/612988 [13:47] Chipaca, hi ;-) [13:48] seb128: hi! I was about to set it back to "Won't Fix", but it felt too much like a status war, so here I am :) [13:48] Chipaca, see comment #10 [13:48] Chipaca, rickspencer3 made a call there [13:49] mvo - did you have much luck with that ubufox issue? [13:49] seb128: ah! rickspencer3: please comment on the bug then :) [13:49] seb128: I talked with him on IRC, but I guess there's no public record of that. Gotcha. [13:50] Chipaca, I though the agreement was to drop the banner for this cycle [13:50] Chipaca, but yeah, maybe let's sort that when rickspencer3 wakes up [13:50] andreasn, i am surprised nobody has commented about that before, it has been like this for ages... and just last night i couldn't remember what it did and had to look at the source === MacSlow is now known as MacSlow|afk [13:50] which isn't a good sign :) [13:51] seb128, how would you feel about a UI freeze exception for something like a silly, really unclear preference setting? [13:51] Chipaca, kenvandine: btw I think somebody mentioned that having ubuntuone-preference not in the indicator menu was an issue? [13:52] seb128, remember who? [13:52] i think that was driven by design/user testing [13:52] kenvandine, I think that during monday's call? [13:52] I'm not sure now [13:52] i don't think so [13:52] yeah, I think that's a wanted change [13:52] ok [13:52] i'll do it then [13:52] andreasn, could you please file a bug? [13:53] i'll fix it and get the exception filed? [13:53] kenvandine, sorry I was speaking about the indicator change, but yeah seems something to do for gwibber [13:53] kenvandine, of course. Launchpad? [13:53] andreasn, yes please [13:53] seb128: yes, although I'm not sure of the severity of that [13:53] go ahead and assign it to me [13:53] kenvandine, open a bug, email documentation list [13:53] yup [13:53] sweet! thanks for the help! [13:53] Chipaca, seems it's not a bug but a dx design change [13:54] seb128: ubuntu one *was* in the me menu, and was removed at some point [13:54] seb128: it's a regression for us [13:54] right [13:54] kenvandine, ^ [13:54] seb128, yes... dbarth did it [13:54] kenvandine, see they consider it as a bug [13:54] davidbarth, ^ [13:54] davidbarth, ^^ [13:54] i thought they were aware of that, sorry Chipaca [13:55] we did talk about that in one of the integration calls [13:55]