[02:24] <root___> hello all
[06:08] <MCR1> didrocks: Hi :) The merge here failed due to a conflict - it is now fixed - what has to be done to get this merged ?: https://code.launchpad.net/~mc-return/nux/nux.merge-optimize-performance-and-style/+merge/117351
[06:12] <MCR1> Trevinho: Hi :) Here jenkins was having troubles I guess: https://code.launchpad.net/~mc-return/unity/unity.merge-optimize-performance-and-style/+merge/117310 - can you help me with getting this merged ?
[06:14] <MCR1> duflu: Hi :) Could you please take a look at https://code.launchpad.net/~mc-return/compiz/compiz.fix1030473-part1/+merge/117182 and https://code.launchpad.net/~mc-return/compiz/compiz.fix1030473-part2/+merge/117410 ?
[06:14] <duflu> MCR1: Sorry, no time this week :(
[06:15] <MCR1> duflu: :(
[06:15] <MCR1> duflu: But thx anyway...
[06:16] <duflu> MCR1: Maybe in a few hours. I'm not sure :(
[06:17] <didrocks> hey MCR1: yeah, upstream trunks are broken right now. sil2100 is fixing that
[06:18] <MCR1> duflu: Okay thanks, it would be really nice and should be easy and fast to check for you...
[06:19] <MCR1> didrocks: ah, okay - so waiting will automatically fix it, yes ?
[06:19] <didrocks> yeah
[06:19]  * didrocks sees no tests on the compiz MP
[06:19] <didrocks> oh there are sorry
[06:20]  * didrocks takes more coffee :)
[06:20] <MCR1> didrocks: Thx.
[06:21] <jokerdino> hello
[06:22] <jokerdino> isn't bug #1014346 and bug #924472 dupes?
[06:26] <MCR1> didrocks: Should this be fixed, or is it just all WIP ? : https://bugs.launchpad.net/nux/+bug/1032313
[06:27] <MCR1> jokerdino: Looks like those are duplicates indeed...
[06:28] <jokerdino> MCR1: thanks. i was following the other bug and this new one has a fix committed.
[06:28] <jokerdino> i'll mark it as dupe now.
[06:28] <didrocks> MCR1: wait for everything to be merged in, if they are still there, feel free to propose a MR
[06:28] <MCR1> didrocks: ok
[07:18] <thumper> uk morning
[08:35] <didrocks> hey thumper
[09:02] <thumper> hi didrocks
[09:03] <thumper> didrocks: my laptop is busy upgrading to quantal :)
[09:04] <didrocks> thumper: yeah, finally! You asked me last month if it was safe to upgrade and I told you yes. So I guess now you are taking didrocks'advice + a month of security? :p
[09:04] <thumper> didrocks: and the benefit of being in the office
[09:04] <thumper> didrocks: so much, much faster
[09:05] <didrocks> oh yeah, I can imagine ;)
[09:05] <didrocks> thumper: do you like it btw?
[09:05] <thumper> didrocks: the office? yeah, very nice
[09:05] <didrocks> the office looks really great IMHO and I loved the view on the roof while eating (we didn't get that much rain)
[09:06] <thumper> :)
[09:07] <sil2100> True true, we were lucky back then ;)
[09:07] <sil2100> But it was windy!
[09:08] <didrocks> sil2100: well, I prefer wind and no rain than the contrary :)
[09:11] <seb128> thumper, btw did the fix from desrt work? you didn't reply to my email
[09:12] <thumper> seb128: I don't know, it was an issue with the AP stuff, and the quality engineers have been in lexington all week
[09:12] <thumper> I've not had any communication with them
[09:12] <seb128> ok
[09:12] <seb128> well, no news, good news? ;-)
[09:14] <thumper> :)
[09:19] <MCR1> Thanks a lot duflu, even if you're gone ;)
[09:26] <MCR1> Yeah, first of my Compiz speedups has landed 8-)
[09:27] <MCR1> Thx again, duflu :)
[09:33] <didrocks> congrats MCR1 and thanks to you! :)
[09:34] <MCR1> didrocks: np, happy to help :)
[09:35] <MCR1> didrocks: Do you know of any efforts for 12.10 to lower boot times - I think we could do a lot in this segment and would like to help...
[09:35] <didrocks> MCR1: no particularly a target where we have real time to act on. So any contribution you can do in that regard is more than welcomed :)
[09:36] <MCR1> didrocks: Experts got boot time (especially for embedded devices) down to 1 second already... Ubuntu should be faster, too...
[09:36] <MCR1> didrocks: With small optimizations I am booting in 17 seconds here, but there is still a lot of room for improvements...
[09:37] <didrocks> I agree
[09:41] <sil2100> MCR1: 17 seconds? On what hardware?
[09:43] <MCR1> sil2100: Intel Core2Quad@3.16GHz Q8300, A-Data 128GB SSD
[09:44] <MCR1> sil2100: But I think I am still wasting 3 seconds, because the kernel waits 3 seconds for SCSI drives... (sym53c8xx driver)
[09:46] <MCR1> sil2100: http://free-electrons.com/pub/conferences/2011/genivi/boot-time.pdf
[09:48] <MCR1> sil2100: http://elinux.org/Boot_Time
[09:49] <sil2100> Would have to measure how long it takes on my system, but probably longer
[09:51] <MCR1> sil2100: I think we should invest some effort to speed up 12.10 as boot time is the first important perception a new/old user has from his system - a fast boot is simply cool
[09:52] <sil2100> True, I remember how happy I was when my system was booting up and shutting down really fast
[09:52] <sil2100> The shutdown time should be taken into cosideration too
[09:53] <MCR1> sil2100: yes, but shutdown is currently quite fast here without optimization...
[09:54] <MCR1> sil2100: Do you know how to best get in touch with the people responsible for this part of Ubuntu (kernel, boot) ?
[09:57] <sil2100> MCR1: hm, hard to say really - didn't have too much contact with the kernel people to be humble
[09:57] <sil2100> MCR1: but maybe slangasek would know?
[09:57] <MCR1> On systems with HDD e4rat is really great as well (much faster than ureadahead in my experience) - Highly recommended if your boot time is long...
[09:58] <sil2100> Could anyone review https://code.launchpad.net/~sil2100/unity/add_libunity_rpath/+merge/117941 ?
[09:58] <sil2100> Since this is essentially breaking unity-team staging
[09:58] <sil2100> mhr3, Trevinho, andyrock: ^
[09:58] <sil2100> didrocks: ^
[09:58] <sil2100> ;)
[09:59] <sil2100> Excuse my CMake foo btw.
[10:02] <MCR1> sil2100: Are you using SSD too ?
[10:03] <jokerdino> sil2100: https://code.launchpad.net/~barneedhar/unity/lp-937334/+merge/115086 what does it mean?
[10:07] <andyrock> jokerdino, fixed
[10:07] <andyrock> sil2100, will test in an moment
[10:07] <jokerdino> andyrock: thanks. wasn't sure what i should have done earlier.
[10:08] <sil2100> jokerdino: usually, when submitting a merge request, you should also set the merge commit message
[10:08] <sil2100> jokerdino: you can either do it when submitting, or after submitting just click 'Set Commit Message'
[10:08] <jokerdino> sil2100: is it different from bzr commt -m "message"?
[10:09] <sil2100> MCR1: no, I'm using normal hdd
[10:09] <andyrock> jokerdino, yep
[10:09] <andyrock> because a MP can have more commits
[10:09] <sil2100> jokerdino: yes - since commit messages you use in your branch are not taken into account when merging the branch
[10:09] <jokerdino> sil2100: ah, i think i get it now. i probably overlooked some fields in that page.
[10:09] <sil2100> jokerdino: because as andyrock said, you can have more than one commit in a branch that is supposed to be merged
[10:10] <sil2100> jokerdino: it's in some 'additional' tab or something, so it's actually easy to miss ;)
[10:10]  * jokerdino saves this chat log for future reference.
[10:10] <jokerdino> got to love the help i am getting :-)
[10:11] <sil2100> jokerdino: no problem - thanks for noticing and submitting the fix ;)
[10:12] <jokerdino> sil2100:  no problem myself. it was much simpler than i was expecting. both the fix and the bzr stuff.
[10:12] <jokerdino> btw, with talks about adding more default lens, would the shortcut overlay need to be amended?
[10:12] <jokerdino> or consult with the design team?
[10:16] <sil2100> jokerdino: first better consult with the design team, they'll know what to do
[10:17] <jokerdino> i think you guys would take care of it. /me goes back to fixing bitesize bugs.
[10:17] <MCR1> sil2100: I can really recommend to you trying e4rat in this case: http://e4rat.sourceforge.net/
[10:19] <jokerdino> sil2100, andyrock: and well, thanks btw. hoping to bug you all more in the future =)
[10:19] <MCR1> sil2100: The instruction how to use it: https://wiki.archlinux.org/index.php/E4rat
[10:19] <MCR1> sil2100: You will be impressed ;)
[10:20] <sil2100> jokerdino: bitesize bugs are the best for learning the game ;) Hope to see more merges from you soon!
[10:20] <sil2100> MCR1: oh, didn't know about this one - thanks ;) *bookmarking*
[10:21] <jokerdino> Thanks. :-)
[10:21] <MCR1> Yeah, Part 2 also landed in lp:compiz :-D
[10:23] <sil2100> \o/
[10:25] <MCR1> But my Unity merges are somehow not landing, I would be grateful if someone could help me with those: https://code.launchpad.net/~mc-return/unity/unity.merge-optimize-performance-and-style/+merge/117310 https://code.launchpad.net/~mc-return/unity/unity.merge-fix-typos/+merge/116216 https://code.launchpad.net/~mc-return/unity/unity.merge-reduce-png-filesizes/+merge/110978
[10:29] <sil2100> MCR1: I'll approve and get merged at least one of them now ;)
[10:29] <MCR1> sil2100: thx
[10:30] <sil2100> MCR1: since I wanted to approve it before, but well... we had problems with trunk actually ;p
[10:30] <jokerdino> ok hold on. Is Unity-merger a bot or just did rocks ?
[10:30] <sil2100> jokerdino: it's a bot ;)
[10:30] <sil2100> A bot that we sometimes break by accident ;p
[10:31] <jokerdino> haha i see. did rocks uses it at times i suppose?
[10:31] <jokerdino> it seems to make intelligent review comments
[10:33] <jokerdino> ok actually it doesn't. it almost looked like it was.
[10:33] <jokerdino> you can now ignore me for a while. i will get myself busy with other stuff
[10:35] <sil2100> jokerdino: intelligent comments ;)?
[10:35] <sil2100> jokerdino: I only remember getting a few pre-programmed ones always...
[10:35] <sil2100> jokerdino: :)
[10:36] <jokerdino> sil2100: i mean, at first, the jenkins.qa looked like a legit comment. but i see unity merger saying it all over again in other reviews.
[10:36] <sil2100> True true
[10:37] <jokerdino> well, i shouldn't be disturbing you guys anymore :P
[10:37] <jokerdino> this doesn
[10:37] <jokerdino> this doesn't feel right..*
[10:39] <MCR1> sil2100: thx
[10:52] <Trevinho> sil2100: do you still need the review?
[11:20] <MCR1> sil2100: I had to fix a merge conflict here: https://code.launchpad.net/~mc-return/nux/nux.merge-optimize-performance-and-style/+merge/117351 Do I need reapproval now ?
[11:41] <sil2100> MCR1: re-approved
[11:44] <MCR1> sil2100: thx
[11:56] <thumper> hi MCR1
[11:56]  * thumper is matching nics to LP ids
[12:00] <MCR1> Hi thumper :)
[12:43] <MCR1> \o/ I can confirm my Compiz fixes did not break it 8-)
[12:48] <zcoob> Hi, i am trying to change the default fixed width font used by ubuntu. I can change it via a gui tool but i don't want that. I can also change it using gsettings set org.gnome.desktop.interface monospace-font-name "Monospace 11" BUT i need to do that while in X and i don't want that either. any suggestions on how to change that without having to be inside a graphical environment?
[12:50] <Zhenech> you can ship a settings file for that
[12:50] <Zhenech> do not ask exactly how, though,lemme search
[12:50] <zcoob> can you explain?
[12:51] <zcoob> i tried using gconftool-2 -s /desktop/gnome/interface/monospace_font_name --type STRING "Monospace 11" but that doesn't seem to do anything
[12:51] <MCR1> Hmmm, suddenly the Unity-2d-panel is making troubles here - it does not update and hardly reacts to mouse clicks - strange...
[12:52] <Zhenech> zcoob, there is a debhelper script for packages called dh_installgsettings
[12:52] <seb128> MCR1, did you get the new dbus 1.6?
[12:52] <Zhenech> it installs those settings to usr/share/glib-2.0/schemas/
[12:54] <MCR1> seb128: yes - 1.6.4-1ubuntu1~build1
[12:55] <zcoob> thanks that might do it
[12:55] <MCR1> seb128: The clock does not change and indicator-multiload does not update anymore and starting the panel manually throws errors like:
[12:56] <seb128> MCR1, you need https://code.launchpad.net/~seb128/unity/signal-eavedropping-fix/+merge/117931
[12:56] <MCR1> unity-2d-panel: [WARNING] X Error: BadWindow (invalid Window parameter) 3
[12:56] <MCR1>   Major opcode: 18 (X_ChangeProperty)
[12:56] <MCR1>   Resource id:  0x0
[12:56] <seb128> MCR1, it's in quantal, not sure what unity version you use
[12:56] <MCR1> seb128: Unity staging PPA
[12:57] <seb128> MCR1, that's why
[12:57] <seb128> the merge didn't make it there yet
[12:58] <MCR1> seb128: So that means that waiting a bit will probably fix it, yes ?
[12:58] <seb128> correct, waiting and updating
[12:58] <MCR1> seb128: Sure, thx 4 the fast help :)
[12:58] <seb128> yw!
[12:59] <MCR1> gotta leave now - c ya soon with more merge requests from my side ;)
[13:20] <zcoob> hmm Zhenech i just looked into dh_installgsettings and i'm not sure that is what i am looking for
[13:21] <zcoob> thing is, i can't find any "Ubuntu Mono 13" anywhere
[13:21] <zcoob> neither in my home nor in /usr/share/glib2.0/schemas
[13:22] <Zhenech> zcoob, its just a helper for you when you create .debs, the actual setting is done by droping a file in that folder
[13:23] <zcoob> there is a gschemas.compiled file in that folder that probably has the Ubuntu Mono 13 in
[13:23] <zcoob> but that's a binary file
[13:23] <zcoob> i can't believe that there is no simple way to change the default font via command line
[13:27] <sil2100> zcoob: actually, there might be a not-so-easy way of doing that
[13:27] <sil2100> Just give me one moment
[13:27] <sil2100> zcoob: you want to change the default size of monospace font?
[13:28] <zcoob> as i said if i change it via gconftool-2 -s /desktop/gnome/interface/monospace_font_name --type string "Monospace 11" it doesn't work
[13:28] <zcoob> if i change it in X via gsettings set org.gnome.desktop.interface monospace-font-name "Monospace 11" it works
[13:28] <zcoob> but i have to be in X which doesn't make sense to me
[13:28] <zcoob> if i can be in X i can also just do it using a gui
[13:29] <zcoob> i want to change the fixed width font
[13:29] <sil2100> zcoob: so wait, without X calling gsettings set ... doesn't work?
[13:29] <zcoob> it bugs out here
[13:29] <zcoob> yeah
[13:29] <zcoob> one sec
[13:30] <zcoob> ** (process:4519): WARNING **: Command line `dbus-launch --autolaunch=14aa918c48b2c82031b42f69000000e2 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n
[13:30] <sil2100> zcoob: not sure if this will work, but try maybe this:
[13:31] <popey> grrrrr
[13:31] <sil2100> dconf write /org/gnome/desktop/interface/monospace-font-name "Ubuntu Mono 10"
[13:31] <sil2100> Or Monospace 11 as you wish
[13:33] <zcoob> "doesn't work"
[13:33] <zcoob> it either resets everytime i relog
[13:33] <zcoob> or it just doesn't work
[13:34] <sil2100> zcoob: ok, another try then ;p
[13:34] <zcoob> this is seriously the most annoying problem i encountered so far
[13:35] <sil2100> zcoob: dbus-launch gsettings set org.gnome.desktop.interface monospace-font-name "Monospace 11"
[13:35] <zcoob> gsettings already runs exactly that
[13:36] <zcoob> gsettings get org.gnome.desktop.interface monospace-font-name
[13:36] <zcoob> always returns "Ubuntu Mono 13"
[13:37] <zcoob> fuck
[13:37] <zcoob> that at least didnt put out an error
[13:37] <zcoob> one sec i'll check if that actually worked
[13:37] <zcoob> man thanks sil2100
[13:37] <sil2100> zcoob: it works?
[13:37] <zcoob> yes
[13:38] <sil2100> zcoob: phew, good to hear that - glad to be of some help ;)
[13:38] <zcoob> seriously the weirdest problem i had so far
[13:39] <sil2100> zcoob: I recently started working with gsettings/dconf/gconf, and usually it's full of problems like this - always something problematic
[13:40] <zcoob> in my opinion it would be easier to just leave that stuff as transparent as it gets
[13:40] <zcoob> i wouldn't even mind xml files
[13:42] <sil2100> I played around with various configuration systems in the past, and usually simple is 'not enough' - since settings can have depenedencies, migrations, deprecations, default values and different schema manipulations
[13:42] <sil2100> To make a working configuration system, sadly, you _have_ to make it complex ;/
[13:53] <zcoob> :(
[13:53] <zcoob> i still don't like it :)
[13:53] <zcoob> makes my job harder lol
[13:55] <sil2100> We all suffer because of it ;p
[14:36] <sil2100> brb, storm
[15:05] <jaytaoko1> sil2100: ping
[15:14] <sil2100> jaytaoko1: pong!
[15:15] <sil2100> jaytaoko1: seems like staging is still broken...
[15:15] <jaytaoko1> sil2100:  what is it? failure to build?
[15:22] <sil2100> jaytaoko1: no, actually it's all fine - just the build didn't publish yet ;)
[15:22] <sil2100> jaytaoko1: \o/
[15:23] <jaytaoko1> sil2100: cool
[15:23] <jaytaoko1> sil2100: so I have a small branch I would like to push in nux. Is there a chance I can to it now?
[15:24] <sil2100> jaytaoko1: could you point me to it? Is it very important?
[15:24] <jaytaoko1> sil2100: https://code.launchpad.net/~unity-team/nux/nux.libgeis-optional-package/+merge/117942
[15:25] <jaytaoko1> sil2100: since the new geis is not available on precise, this branch allows to compile nux trunk on precise even if geis is not available
[15:25] <sil2100> jaytaoko1: is this tested? Will it really not complain when built on precise?
[15:25] <jaytaoko1> sil2100: yes it is
[15:26] <sil2100> jaytaoko1: then, let's merge it in ;)
[15:26] <jaytaoko1> sil2100: Quantal has Geis will Precise doesn't. this will only affect precise builds
[15:26] <jaytaoko1> sil2100: thanks! doing it now
[17:52] <MCR1> seb128: Probably you already know, but still I confirm the dbus fix. Unity-2d-panel fully functional again :)
[19:37] <lynchseanm> Revision 639 in the Nux trunk breaks the Unity build for me because it can't find NuxGraphics/GestureEvent.h. I think this is because I have libutouch-geis on my system instead of libgeis and HAVE_GEIS gets set to false in the Nux config.
[19:37] <lynchseanm> Can I just remove libutouch-geis and install geis from source to fix this?
[23:22] <bilal> Anyone else having trouble building Unity from trunk, with error: ‘GestureEvent’ in namespace ‘nux’ does not name a type
[23:23]  * bilal is updating his GCC right now so that might probably fix it
[23:29] <bilal> alright, fixed. Had to re-build Nux with gesture support enabled