[01:36] <bschaefer> thumper, ping! I think the new char comp merge broke the ibus support. As well as using the ctrl for shortcuts...
[02:01] <bschaefer> thomi, do you happen to have the unity trunk running?
[02:05] <thomi> bschaefer: no, but I could shortly. what's up?
[02:05] <bschaefer> thomi, well I want to double check for a possible regression
[02:05] <bschaefer> on all ctrl shortcuts and ibus in the dash
[02:05] <thomi> sure, I'll just build latest
[02:06] <bschaefer> thomi, thanks, I checked jenkins and it failed
[02:06] <thomi> bschaefer: well, jenkins is rather broken today
[02:07] <bschaefer> thomi, ok, that would explain the failures
[02:07] <thomi> ok, I'm running trunk
[02:07] <thomi> what should I test?
[02:08] <bschaefer> the dash clipboard to start
[02:08] <bschaefer> o
[02:08] <bschaefer> or
[02:08] <bschaefer> just type some stuff into the dash
[02:08] <bschaefer> and try to copy and paste it
[02:08] <bschaefer> or ctrl+a
[02:08] <thomi> yep - that's broked
[02:08] <bschaefer> shit
[02:08] <thomi> who did that?
[02:08] <bschaefer> jay
[02:09] <thomi> ahh, the composition character test
[02:09] <bschaefer> and njpatel, when they were pushing changes to IMTextEntry for comp char
[02:09] <bschaefer> yeah
[02:09] <thomi> didn't run the tests before they merged huh? :)
[02:09] <bschaefer> njpatel said it passed all the test
[02:09] <thomi> well, at least jenkins caught it
[02:09] <thomi> bschaefer: he probably just ran the unit tests
[02:09] <bschaefer> yeah haha
[02:10] <bschaefer> thomi, yeah
[02:10] <bschaefer> thomi, well looks I have a fun night ahead of me :)
[02:10] <bschaefer> thomi, thanks for confirming
[02:10] <thomi> no problem
[02:45] <jalcine> Anyone knows the PPA to add HUD?
[02:45] <jalcine> Or should I just test out Precise?
[02:45] <Daekdroom> There is no PPA for HUD for Oneiric, if that's what you're wondering.
[02:48] <mhall119> jalcine: yeah, you'll need to test Precise to try HUD
[07:36] <thevinci> wasn't the groove shark lens/scope installed by default on 12.04?
[07:37] <thevinci> I feel like i didn't have to install it before, but i just did a clean install of 12.04, and it wasn't there anymore
[08:58] <mhr3> angeloc, ping?
[09:00] <angeloc> mhr3: pong
[09:02] <mhr3> angeloc, i added a comment on https://code.launchpad.net/~angelo-compagnucci/unity-lens-files/fix-for-773841/+merge/96100/comments/207975
[09:04] <angeloc> mhr3: ok. i'm doing it!
[09:04] <mhr3> angeloc, thx, it'll be ready to go once done
[09:04] <mhr3> nice tautology :P
[09:05] <angeloc> mh3r: yes! for prerequisite branch I'm trying to get acquainted with pipelines
[09:07] <mhr3> angeloc, prereq branch is just a field in launchpad, i dont think it's integrated with bzr itself... though i might be wrong
[09:09] <angeloc> mhr3: ops... the only doc I found online about prereq branch is there http://wiki.bazaar.canonical.com/BzrPipeline. I'm really happy of your info, pipeline seems a big mess tome!
[09:10] <mhr3> not just to you :)
[09:10] <mhr3> angeloc, just click the resubmit proposal button on top of the merge request, and there's the source + target + prereq fields
[09:11] <angeloc> mhr3:gret!
[09:11] <angeloc> mhr3:great!
[09:13] <Andy80> 'morning guys :)
[09:14] <angeloc> mhr3: done!
[09:15] <angeloc> mhr3:done also prereq!
[09:18] <angeloc> mhr3: launchpad totally rocks! It' really the best software project management tool out there!
[09:22] <mhr3> glad you like it ;)
[09:48] <angeloc> mhr3: so now to include my branche we have to wait that your branch will be merged cause is a prereq, right?
[09:49] <loremattei> MacSlow: hi!
[09:49] <mhr3> angeloc, right, but we're frozen now anyway, so nothing gets it right now
[09:50] <angeloc> mhr3: frozen for 12.04? so changes will be included in 12.06 right?
[09:50] <MacSlow> hey loremattei
[09:52] <loremattei> MacSlow: hello! Thanks for the review of my patch to unity. Sorry for the missings, I'm new to unity development.
[09:53] <mhr3> angeloc, no, fixes can still get in, but we want to release 5.6, so trunks are frozen...
[09:53] <MacSlow> loremattei, no worries... that's what we're here for :)
[09:53] <MacSlow> loremattei, just ask anything while you're going along the learning process
[09:54] <loremattei> MacSlow: Thanks. The paperwork is now done. I'm going to write down the autopilot tests, but I actually have some troubles with running it.
[09:54] <loremattei> MacSlow: I've found this link: https://wiki.ubuntu.com/Unity/QA/Autopilot
[09:54] <MacSlow> loremattei, got to be on a meeting any moment... but I can help out in ~15 min.
[09:55] <loremattei> MacSlow: ok! thank you!
[09:55] <angeloc> ok, so new fixes will be in unity 5.8!
[10:43] <davidcalle> mhr3, ping
[10:43] <mhr3> davidcalle, pong
[10:44] <angeloc> mhr3: there is bug 770126 that is like something i fixed
[10:44] <angeloc> mhr3: where to look for alt-f2?
[10:45] <davidcalle> mhr3, would you have the time to do to the music lens what you did to the gwibber one? I'm looking at the TreeIndex merge and I'm a bit overwhelmed by the complexity of it.
[10:47] <mhr3> angeloc, it's in the applications lens (runner.vala)
[10:48] <angeloc> mhr3: thank you! the bug is assigned, I think I can fix it, I reassing it to me?
[10:48] <mhr3> davidcalle, yea, i can do it at some point, could you do at least a simple substring search for the time being?
[10:48] <davidcalle> mhr3, already done.
[10:49] <davidcalle> mhr3, thanks
[10:49] <mhr3> angeloc, feel free to work on it, seems like it was never finished
[10:50] <angeloc> mhr3, i tkink so
[10:50] <mhr3> davidcalle, can you open a bug about it and assign to me?
[10:50] <davidcalle> mhr3, sure
[10:50] <mhr3> davidcalle, thx
[11:03] <mhr3> davidcalle, btw if the rb scope is now mostly working and can even search, y u no mp it? :)
[11:04] <bmoez> hi, can any one tell me if there is a scripting language to tweak unity, if yes, please where can i found documentation about it?
[11:06] <davidcalle> mhr3, right. :)
[11:07] <angeloc> mhr3: there is something wrong with my code, i modified the regex concatenating string + TLD_REGEX + string
[11:08] <angeloc> mhr3: now c compiler (after valac) cannot compile because TLD_REGEXP is not expanded and gcc cannot compile
[11:08] <angeloc> mhr3: _tmp8_ = g_regex_new ("(http[s]{0,1}://.+){0,1}" "[a-zA-Z0-9\\-\\.]+\\." TLD_REGEX "$", G_REGEX_OPTIMIZE, 0, &_inner_error_);
[11:09] <mhr3> angeloc, how did you define TLD_REGEX?
[11:09] <angeloc> const string = "..."
[11:10] <mhr3> angeloc, pastebin the diff pls
[11:13] <angeloc> mhr3: http://pastebin.com/TX50euF3
[11:14] <mhr3> angeloc, you need to define consts outside of methods
[11:14] <angeloc> mhr3:generally i'm not so stupid ...
[11:15] <mhr3> angeloc, it's actually a bug in vala...
[11:15] <angeloc> mhr3: fiuuu :)
[11:16] <mhr3> angeloc, also the idea is to use fewer lines now that you dont need to align it with the method call params ;)
[11:17] <angeloc> mhr3: you don't like string wrapping? I can remove in istants!
[11:17] <angeloc> mhr3: i think it's more readeable
[11:19] <mhr3> angeloc, no, i do, but it limited you to like ~40 chars
[11:19] <mhr3> now you can use ~70 per line ;)
[11:19] <angeloc> ok!
[11:22] <angeloc> mhr3: done!
[11:22] <angeloc> mhr3: going to eat something, bye
[11:38] <chrisccoulson> hi API. you're Alejandro, aren't you?
[11:57] <API> chrisccoulson, hi again, sorry network problems
[11:57] <chrisccoulson> hi API. not sure if you saw that i subscribed you to mozilla bug 733712 ;)
[11:59] <API> uh, no, I missed it
[11:59] <API> thanks
[11:59] <API> well, it seems that I will need to revert that change
[12:00] <chrisccoulson> API, yeah, we did that in ubuntu already just to unbreak firefox for now
[12:00] <API> at least initially to solve this
[12:00] <chrisccoulson> thanks
[12:00] <API> well yes, but if firefox is affected probably others will be
[12:00] <API> so probably it would be better to just revert that change
[12:00] <API> and then think on something
[12:01] <API> not sure if I'm in time to make a new release
[12:01] <chrisccoulson> cool, thank you :)
[12:01] <API> at least for 3.3.91
[12:01] <API> I will ask on gnome #release-team
[12:05] <Velmont> JanC: So I actually managed to make dconf + lockdown/disable-lock-screen  work. When I set it using   dconf disable-lock-screen true  on the command line, my own user actually can't lock screen anymore. But the buttons are still there, which threw me off the trail.
[12:05] <Velmont> JanC: So that means that the important code is actually there, -- but not the "hide when disabled" part.
[12:06] <API> chrisccoulson, it seems that I'm in time to make a new release
[12:06] <API> so alghouth alexander proposed to add a reentrance guard
[12:06] <Velmont> JanC: And also, I need to understand how dconf works, -- because I have to explicitly set it in the session in order to work. So need to find out how to do systemwide dconf settings (actually, for all the computers), and have it have it disabled there.
[12:06] <API> I think that I will just revert the change
[12:07] <API> to ensure that the change will be in this release
[12:07] <chrisccoulson> excellent, thanks :)
[12:13] <rye> umm... has somebody fixed bug #932906 ? can't reproduce on 5.4.0+bzr2057ubuntu0+654
[12:15] <didrocks> rye: yeah, it's fixed in trunk :)
[12:15] <rye> didrocks, sweeeeeeeeeet.
[12:17] <rye> i start to see the value of hud - virt-manager indicator - open machines
[12:17] <didrocks> rye: changing the milestones, thanks for the highlight btw :)
[12:17] <rye> didrocks, you are very welcome, and thank you very much!
[12:49] <API> chrisccoulson, I have just made a 2.3.93 ATK release
[12:49] <chrisccoulson> API, thanks for that
[12:49] <API> chrisccoulson, thanks to you, for pinging me
[13:02] <mhall119> Cimi: ping
[13:02] <Cimi> mhall119, pong
[13:03] <mhall119> Cimi: do developers have control over whether or not to use ayatana-scrollbars in their app?
[13:03] <Cimi> mhall119, yes
[13:03] <Cimi> mhall119, they could set the environmental variable at the startup of their app to 0
[13:03] <mhall119> Cimi: do we have some documentation explaining how to use them/not use them
[13:04] <Cimi> g_setenv ("LIBOVERLAY_SCROLLBAR", "0", TRUE);
[13:04] <mhall119> is that all?
[13:04] <Cimi> yep
[13:04] <mhall119> they can't change things on a per-scrollarea basis
[13:04] <Cimi> just after gtk_init I'd say
[13:04] <Cimi> mhall119, no
[13:04] <mhall119> ok, thanks
[13:05] <mhall119> MacSlow|lunch: ping
[13:05] <Cimi> mhall119, but you could in theory
[13:05] <Cimi> mhall119, call g_object_new instead gtk_scrollbar_new
[13:05] <Cimi> and get the OBJECT you want
[13:05] <mhall119> Cimi: if that's not a method we want to promote, then I'm not going to include it in our docs
[13:06] <Cimi> no then
[13:06] <mhall119> ok, thanks
[13:08] <Daekdroom> Huh.. I can't seem to use the mouse scroll wheel in Gnome-terminal and gwibber anymore.
[13:37] <MacSlow> mhall119, what's up?
[13:38] <mhall119> MacSlow: hey, just wanted to check if https://wiki.ubuntu.com/NotificationDevelopmentGuidelines was still up to date
[13:38] <mhall119> and if http://www.galago-project.org/specs/notification/0.9/ was still the proper API to follow for app developers to use notify-osd
[13:38] <MacSlow> mhall119, basically yes...
[13:39] <mhall119> any caveats that I should be aware of before we copy/paste them to developer.u.c?
[13:40] <MacSlow> mhall119, regarding the fdo/glago spec... it still applies minus our different handling of timeouts (ignoring them, just n-osd controlled) and actions (not allowed by n-osd)
[13:41] <rye> Daekdroom, interesting, me too - gnome-terminal is not scrolling with trackpad scrolling feature. Is that what gtk change for smooth scrolling was about?
[13:42] <Daekdroom> Well, both gnome-terminal and gwibber do not use smooth scrolling.
[13:42] <mhall119> MacSlow: thanks for the update
[13:43] <Daekdroom> At first I thought it was a overlay-scrollbar issue. Hence why I mentioned it here, but it might be GTK indeed.
[13:52] <rye> Daekdroom, there was something about this yesterday here
[13:54] <rye> no, can't find it
[13:55] <rye> and: re bug for the windows not appearing in alt tab - that's 937898
[13:59] <seb128> Daekdroom, rye: scrolling is known to be broken on gtk3,i386 xorg input driver bug
[13:59] <seb128> it's being worked
[13:59] <seb128> well "mouse wheel scrolling" (and likely equivalent pad scrolling)
[14:00] <seb128> you can use page up,down on the keyboard or scrollbars
[14:00] <tokarbol> Not sure if it's the right place to ask, but - is it possible to define multiple default keyboard layouts to unity-greeter? Config or somewhere in source?
[14:00] <rye> seb128, hm, i am on x86-64
[14:00]  * rye checks
[14:01] <seb128> rye, is scrolling broken in all gtk3 apps?
[14:01] <Daekdroom> I'm on AMD64 too.
[14:01] <seb128> weird
[14:01] <Daekdroom> For me it's only broken in Gwibber and Terminal.
[14:01] <rye> seb128, well, gnome-terminal is broken, nautilus is ok
[14:01] <seb128> can you guys do a "xinput list <device_you_use_number>
[14:01] <seb128> xinput list
[14:02] <seb128> then figure the number for your mouse,pad,whatever
[14:02] <seb128> xinput list that and grep for increment
[14:02] <seb128> what is the increment value?
[14:02] <Daekdroom> For master pointer, right?
[14:02] <rye> seb128, http://paste.ubuntu.com/873031/ - no increment
[14:03] <rye> sorry
[14:03] <Daekdroom> Oops. I mean, master keyboard.
[14:03] <seb128> rye, you picked the wrong device
[14:03] <Daekdroom> Wait.
[14:03] <seb128> "Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]"
[14:03] <seb128> that's not a real device
[14:03] <Daekdroom> Hm. I should get some sleep later.
[14:04] <Daekdroom> ⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
[14:04] <Daekdroom> Is that it?
[14:04] <seb128> no
[14:04] <seb128> can you pastebin "xinput list"
[14:04] <rye> seb128, http://paste.ubuntu.com/873036/
[14:04] <seb128> rye, ok, yours is a different issue
[14:04] <seb128> so maybe g-t,vte needs an update to deal with the new gtk
[14:04] <rye> siny!
[14:04] <rye> shiny!
[14:04] <seb128> I couldn't test here
[14:04] <seb128> scrolling is just broken on i386
[14:05] <seb128> in any gtk3 app
[14:05] <seb128> the driver return a buggy increment
[14:05] <Daekdroom> http://paste.ubuntu.com/873040/
[14:06] <seb128> yeah, ok, you guys have a different bug
[14:09] <rye> bug #948612 - filed yesterday
[14:10] <rye> also, the menu part is true too - can't hover the menus
[14:11] <rye> the global menu i mean - the menu gets open, but browsing through it does not change anything
[14:22] <Daekdroom> rye, I don't think that's the bug that's affecting me.
[14:22] <Daekdroom> I can scroll up in gnome-terminal by clicking the overlay scrollbar, and global menu is working fine for me too
[14:24] <rye> Daekdroom, i can't grab the overlay scrollbar thumb in gnome-terminal o_O
[14:26] <seb128> rye, I doubt that bug is a gtk one
[14:26] <seb128> rye, like g-t or vte needs updating for the g-t issue, dunno about menus
[14:27] <rye> seb128, will ass gnome-terminal to the bug too then
[14:28] <seb128> rye, no, please just reassign
[14:28] <seb128> rye, having several components on a bug is making them annoying to work with
[14:28] <rye> seb128, checking w/o overlay scrollbars first, ok, understood
[14:35] <rye> erm, was the LIBOVERLAY_SCROLLBAR=0 env var handling removed?
[14:41] <seb128> rye, no
[14:42] <rye> ok, cool, it is overlay-scrollbar-independent
[15:01] <rye> seb128, this is what i was telling about the menus - https://launchpadlibrarian.net/95763208/out.ogv
[15:01] <rye> talking about
[15:02] <seb128> rye, is that unity-3d?
[15:02] <rye> seb128, yes, bug #948612
[15:02] <rye> umm
[15:02] <rye> no
[15:02] <seb128> ok, weird, I don't get that here
[15:02] <rye> bug https://bugs.launchpad.net/bugs/949029
[15:03] <rye> seb128, are you using trunk unity?
[15:03] <seb128> yes
[15:03] <rye> oh, i wil need to test this in unity2d too then
[15:03] <rye> aha
[15:03] <rye> buttons don't highlight too
[15:03] <rye> in gtk3 apps
[15:04] <seb128> rye, weird
[15:06] <mhr3> angeloc, why still so much free space when defining the const string?
[15:06] <angeloc> mhr3: to make it enters my low-res monitor...
[15:07] <angeloc> mhr3: how many lines i have to shrink
[15:07] <mhr3> angeloc, i'm all for doing 80 chars per line, but why not just string =\n  "fooo"
[15:08] <mhr3> instead of string =\n                          "fooooo"
[15:08] <mhr3> ie same rules as blocks
[15:09] <angeloc> mhr3: you are right, there is to much blanks before strings ... sometime i'm really stupid!
[15:09] <rye> 100% reproducible, in both unity and unity2d
[15:16] <angeloc> mhr3: done codestyle fixed|!
[15:17] <mhr3> angeloc, now it's awesome, thx! :)
[15:17] <angeloc> mhr3: :)
[15:21] <rye> webm0nk3y, have your gtk3 windows stopped reacting to mouse movements too?
[15:23] <webm0nk3y> rye: yes
[15:23] <webm0nk3y> oh gtk3?
[15:24] <webm0nk3y> rye: terminator works with the mouse
[15:24] <rye> webm0nk3y, well, global menu , like in the video of bug #949029
[15:24] <angeloc> mhr3:thank you very much!
[15:25] <mhr3> angeloc, thank *you*
[15:27] <webm0nk3y> rye: I don't know what the mousewheel behavior is supposed to be in a menu...never used it
[15:28] <angeloc> mhr3:your support was invaluable!
[15:31] <rye> webm0nk3y, that's not the mousewheel, that's just hovering the mouse
[15:32] <webm0nk3y> rye: oh....yes I saw that.. however it started working after i used the keyboard to move the selections up and down,
[15:33] <webm0nk3y> rye: once i used the keyboard once, it kept working for everything...very odd
[16:41] <angeloc> mhr3: I don't know if I made a mistake, but i asked you fro review! https://code.launchpad.net/~angelo-compagnucci/unity-lens-applications/fix-for-770126/+merge/96394
[16:43] <mhr3> angeloc, k, added to todo
[17:05] <loremattei> davidcalle: hi!
[17:05] <davidcalle> loremattei, hey!
[17:07] <loremattei> davidcalle, during past days I played a bit with graphicdesign lens a deviantart scopes porting both to unity 5. Do you agree about pushing them on launchpad?
[17:08] <davidcalle> loremattei, of course! They are currently being proposed for inclusion in Oneiric Software Center. So, it would be a perfect timing.
[17:09] <loremattei> davidcalle, ok! :) So I'll push them and file a merge request.
[17:10] <davidcalle> loremattei, nevertheless, I will make some modifications to them before putting them in the PPA, the scraping part can be improved a lot.
[17:10] <davidcalle> loremattei, thanks a lot :)
[17:12] <davidcalle> mhall119, ping
[17:12] <loremattei> davidcalle, ok. Thank you!
[17:13] <mhall119> davidcalle: pong
[17:15] <davidcalle> mhall119, I've made a small merge prop on singlet, have you looked at it?
[17:16] <mhall119> davidcalle: not yet, I'll check it out though
[17:16] <mhall119> thanks
[17:17] <davidcalle> mhall119, ok. It's just a small thing to handle filters in a better way.
[17:18] <mhall119> ah, good one
[17:35] <PaoloRotolo> Hi all!
[18:59] <hggdh> which package to assign on bugs on the Unity dash?
[18:59] <Daekdroom> hggdh, unity, unless it's specific to a lens/scope.
[18:59] <hggdh> thank you
[21:24] <mhall119> tedg: ping
[21:26] <tedg> mhall119, Howdy
[21:26] <mhall119> hiya tedg, I was wondering when you were going to have a change to write HUD pre-seeding blog/documentation/something
[21:27] <tedg> mhall119, Uhm, honestly, I'm not sure.
[21:28] <mhall119> tedg: is it complicated to do?
[21:28] <mhall119> if not, even just a single paragraph and some sample code will suffice
[21:31] <tedg> mhall119, Well, the 140 character answer is: use HUD, do a hud-dump-application and that's the file you need.  Put it in /usr/share/indicator-appmenu/hud/app-info and you're good :-)
[21:31] <tedg> mhall119, But the instructions so be a bit more verbose than that :-)
[21:32] <mhall119> yeah, something explaining what things in that file are and how they affect HUD would be needed
[23:28] <desrt> bkerensa: hey