[01:16] <TheMuso> RAOF: So the notebook arrived yesterday, and now that I have the product recovery data backed up, I've looked at the NVIDIA GPU in Device manager. Its an NVS3100M.
[01:17] <TheMuso> And the nice thing is in the BIOS, I can choose which GPU I want to use, either Intel, NVIDIA, or both.
[01:17] <TheMuso> So I dare say nouveau support is still lacking for that chip.
[01:18] <TheMuso> bryceh: ^^
[01:19] <RAOF> Have you tried it?
[01:19] <RAOF> Yay for bios writers being useful.
[01:20] <bryceh> TheMuso, congratz on new laptop
[01:20] <RAOF> Yeah, that too :)
[01:26] <TheMuso> RAOF: Will try Linux with the nvidia gpu on it in a while.
[01:56] <micahg> robert_ancell: is there a desktop branch for gjs?
[01:56] <robert_ancell> I just used the lp:ubuntu/gjs branch
[01:56] <micahg> robert_ancell: ok, I wanted to update it to use dh_xulrunner instead of adding it manually in debian/control, so I'll just upload then
[01:57] <robert_ancell> cool
[01:57] <micahg> then i'll fwd it over to Debian so we can sync again :)
[01:58] <TheMuso> bryceh, RAOF, ok 2D nouveau works fine, let me get natty installed and I'll see if the experimental dri package does anything for 3D.
[02:01] <TheMuso> Interesting... Nouveau reckons its an NV50 generation card.
[02:03] <RAOF> I think nouveau knows of nv0x, nv2x, nv3x, nv4x and nv5x as card generations.  From what I can gather, everything after >nv50 and <nvc0 is sufficiently similar to consider one generation.
[02:03] <TheMuso> ah ok
[02:03] <TheMuso> lspci mentions G218
[02:04] <RAOF> Since your card has 2D, I'd expect it to also manage 3D with -experimental (but won't do Unity until this mesa is finished building, tested, and uploaded).
[02:04] <TheMuso> ah ok.
[02:04] <RAOF> Your Stability May Vary :)
[02:04]  * TheMuso nods. I can switch to intel if I need stability.
[02:04] <TheMuso> ...or can I... :)
[02:05] <RAOF> :)
[02:05] <bryceh> the infamous Intel stability
[02:06] <TheMuso> I see myself only using NVIDIA if I need GPU grunt for something, which is rather rare for me.
[02:06] <RAOF> Quick quiz: does it use an eDP connection?  Stability/usability depends on the answer being “no” :)
[02:06] <TheMuso> ...and testing.
[02:11] <TheMuso> How do you find that out?
[02:13] <RAOF> xrandr probably tells you.  Or you could switch to intel and see if the laptop panel turns on :)
[02:13] <RAOF> (If it does, you probably don't have an eDP panel ☺)
[02:15] <robert_ancell> kenvandine, are the libindicate GIR bindings supposed to work?
[02:17] <TheMuso> Oh the laptop panel is working with nouveau.
[02:17] <TheMuso> Its not connected to a monitor.
[02:22] <RAOF> It's intel that has problems with eDP; nouveau, as far as I'm aware, handles it.
[02:22] <TheMuso> Oh right, well under intel the panel does turn on.
[02:22] <TheMuso> And unity does load.
[02:23] <RAOF> Hurray!
[02:29] <cyphermox> hey TheMuso
[02:30] <cyphermox> saw your bug about a11y for nm-applet indicator, did you file the same for indicator-network? I looked but couldn't find it, I was certain I had seen an email about that before
[02:31] <TheMuso> cyphermox: No, I 've already done the work for indicator-network, and kvalo has seen and signed off on it.
[02:31] <cyphermox> ah, so that's why
[02:31] <TheMuso> Because indicator-network is a system indicator, whereas network-manager is still an application indicator, so there are still changes that need to be merged into libappindicator for that to happen.
[02:31] <cyphermox> that's already working for libindicator then, just missing the API for libappindicator?
[02:31] <cyphermox> hehe ok :)
[02:32] <TheMuso> The work is done for libappindicator, and its in the merge queue, but its blocking on some KDE related stuff.
[02:32] <TheMuso> Ted knows more about that.
[02:32] <cyphermox> right
[02:32] <cyphermox> I subscribed to your branch so in theory I should get an email as soon as it's merged
[02:32] <TheMuso> Ok cool.
[07:45] <didrocks> good morning
[08:03] <chrisccoulson> good morning everyone
[08:06] <Sweetshark> morning
[08:07] <chrisccoulson> hi Sweetshark, how are you?
[08:15] <Sweetshark> I am fine, thank you. And you?
[08:42] <rodrigo_> morning
[08:44] <seb128> hey rodrigo_, how are you?
[08:47] <huats> moning
[08:47] <huats> hello seb128 !
[08:47] <seb128> lut huats
[08:47] <huats> how are you seb128 ?
[08:49] <rodrigo_> salut seb128
[08:56] <seb128> huats, I'm fine thanks, what about you?
[08:56] <huats> fine too ! working too hard, but I think I get used to that :)
[08:56] <huats> thanks
[08:57]  * didrocks is eager to see "building from branch" to land. That will totally justify our dx workflow
[09:20] <chrisccoulson> hey seb128, how are you?
[09:20] <seb128> hey chrisccoulson, I'm fine thanks, how are you?
[09:20] <chrisccoulson> seb128, i'm not too bad thanks
[09:21] <chrisccoulson> my daughter is not very well this morning though. she's been sick 3 times already :(
[09:40] <ara_> seb128, morning
[09:40] <seb128> hey ara
[09:41] <ara_> seb128, is it only time what it is preventing you from sponsoring checkbox? or do you need any other information?
[09:41] <seb128> ara_, the diff of the merge request was a bit weird so I delayed that until later, like it cleans files and things without having that documented
[09:42] <seb128> ara_, i.e it's was not trivial and I had other things to do so I delayed until I would have time for proper review, I will try to do it today
[09:42] <ara_> seb128, OK, thanks
[09:45] <ara_> seb128, actually, the things removed are from the build folder, that I don't know why it is there in the first place. It may have been added by mistake in a previous upload
[09:46] <seb128> right, I will check on that
[09:47]  * ara_ checks at what point the build folder was uploaded
[09:53] <ara_> seb128, it was in revision 20. I will create a new branch based on cr3's but removing the build folder and I will propose a new merge superseeding this one
[09:54] <fta2> Title: indicator-application-service crashed with SIGABRT in reply_cb()
[09:54] <fta2> UnreportableReason: The program crashed on an assertion failure, but the message could not be retrieved. Apport does not support reporting these crashes.
[09:59] <seb128> ara_, seems great, thanks ;-)
[09:59] <seb128> fta2: open a bug manually and add the stacktrace I guess
[09:59] <seb128> I need to talk to pitti about those...
[10:01] <ara_> seb128, not needed, I have seen that cr3 already deleted all the build files. I have put a comment to the merge request stating that
[10:01] <ara_> seb128, is that enough?
[10:03] <seb128> ara_, should be yes, thank you!
[10:04] <ara_> seb128, thanks to you!
[10:39] <kklimonda> seb128: when we package unstable version of some library (in this case pangomm) how should we bump shver in d/rules?
[10:40] <seb128> kklimonda, if there is some api addition yes
[10:40] <kklimonda> seb128: for stable libraries, we just bump to the $maj.$min.0, should we do the same for unstable ones?
[10:41] <seb128> not sure to understand the question
[10:41] <kklimonda> seb128: it's a good enough answer :)
[10:41] <seb128> the number represent the version which has the current api defined
[10:41] <seb128> so update the number every time they add a function
[10:42] <seb128> or rather that they add a function to the public api
[10:42] <kklimonda> right, so for unstable releases we may have to bump it more often?
[10:43] <seb128> usually for each version yet
[10:43] <seb128> it's cheap, it's just a number
[10:43] <seb128> it's the depends packages building against the lib will get
[10:45] <soren> The purpose of this tracking is to know that if the last time a new function as was added to libfoo was in x.y.z, but you built against x.y.w, you can still get away with a Depends: library (>= x.y.z).
[10:46] <soren> We used to always have to specify Depends: library (>= <the version we built against>).
[10:46] <seb128> better to use .symbols nowadays though
[10:46] <soren> Very true.
[10:46] <seb128> which does the right thing and check what symbols you use and when they were added
[10:47] <soren> Yeah.
[10:53] <kklimonda> seb128: btw, would you be willing to add some comment to my motu application? I'm not really sure how many should I get, but some people have 7+ so I feel weird ;)
[11:31] <chrisccoulson> my laptop battery is now at 60% capacity. that's depressing. time for a new one soon i think
[12:21] <didrocks> rodrigo_: do you know why evolution-couchdb isn't working for me?
[12:22] <didrocks> when clicking on the ubuntu one list contact, I get a message telling me it can't get the contact list
[12:22] <didrocks> (my android phone and the web interface are working though)
[12:25] <rodrigo_> didrocks, kill evo and the e-addressbook-factory process, and start /usr/lib/evolution/e-addressbook-factory on a terminal, and then try to open the addressbook in evo again
[12:25] <rodrigo_> didrocks, and pastebin the output on the terminal
[12:25] <didrocks> rodrigo_: trying
[12:26] <didrocks> grrr, double monitor and global menu :/
[12:26] <didrocks> dual*
[12:27] <didrocks> rodrigo_: hum, it exited
[12:27] <didrocks> rodrigo_: I just get in the GUI: http://paste.ubuntu.com/568155/
[12:28] <rodrigo_> didrocks, did you kill the previous e-addressbook-factory process?
[12:28] <didrocks> rodrigo_: yeah, it was up and running
[12:28] <didrocks> so, trying again
[12:28] <didrocks> starting it
[12:28] <rodrigo_> ok
[12:28] <didrocks> now starting evo
[12:29] <didrocks> ah, core dump this time :)
[12:29] <didrocks> I prefer that to exiting without showing anything
[12:29] <didrocks> rodrigo_: reporting the stacktrace
[12:30] <didrocks> argh, obsolete because of the X stack :/
[12:30] <didrocks> rodrigo_: when I'll have some time over the week-end, can I report it and bug you?
[12:31] <rodrigo_> didrocks, yes, of course :-)
[12:31] <didrocks> thanks :)
[12:31] <rodrigo_> didrocks, just try to get the output from e-a-f, that should be enough
[12:32]  * didrocks is spammed with 1 000 contact adress since he synced android with his gmail account, time to clean that up
[12:32] <didrocks> rodrigo_: ok :)
[14:22] <bcurtiswx> kenvandine, great work with the progress bar in empathy :)
[14:22] <kenvandine> bcurtiswx, thx
[14:23] <seb128> kenvandine, is xchat-gnome supposed to show counts in the launcher or something?
[14:23] <kenvandine> seb128, if you have xchat-gnome-indicator installed
[14:23] <kenvandine> and
[14:23] <kenvandine> you have the plugin enabled
[14:23] <seb128> kenvandine, can you talk to me again there?
[14:34] <om26er> icons in the live cd are set to gnome icon theme and cannot be changed it seems .svg files cannot be opened at all
[14:34] <seb128> reinstall librsvg2-common as a workaround
[14:35] <seb128> the svg loader is not registered
[14:38] <seb128> didrocks, hey
[14:39] <seb128> didrocks, unping
[14:39] <kenvandine> seb128, did you get the count?
[14:39] <seb128> kenvandine, ok, I think it's activated since the messaging menu list pending events
[14:39] <seb128> kenvandine, but the launcher does nothing
[14:39] <seb128> well it turns the arrow blue
[14:39] <seb128> but no count
[14:40] <kenvandine> humm
[14:40] <didrocks> seb128: we should add that to our IRC client, unping support :)
[14:41] <kenvandine> seb128, still no count?
[14:41] <seb128> kenvandine, no
[14:41] <kenvandine> :/
[14:41] <kenvandine> if it is in the indicator, it should be in the launcher...
[14:42] <kenvandine> although, this makes no sense, but bcurtiswx found he had to restart unity sometimes to get things to show up in the launcher
[14:42] <bcurtiswx> thats correct, although this startup everything works OK
[14:43] <bcurtiswx> my laptop is really an alien that looks like a laptop
[14:46] <davmor2> kenvandine: you know what would make that xchat plugin perfect if when you clicked on it, it went to the window with the most pings :)
[14:47] <kenvandine> davmor2, that is a good idea
[14:47] <kenvandine> well, actually people might get annoyed that it changes on them without expecting it
[14:49] <bcurtiswx> i think launchers should completely replace the indicator-applet
[14:50] <bcurtiswx> they can perform the same functions, maybe that should be a blueprint for Natty +1
[14:52] <bcurtiswx> left clicking on a launcher with pending messages could give you the same list that the indicator-applet does
[14:54] <bcurtiswx> if the launcher panel is hidden make the ubuntu logo turn green ;)
[14:58] <seb128> left click is to focus
[14:59] <seb128> right click will give you the list
[14:59] <seb128> it's how it's designed and work in natty
[14:59] <seb128> the unity rendering side is already done, it just doesn't get the list because it lacks some glue
[14:59] <seb128> it will not replace the applet though, for one thing the applet load other indicators which don't make sense in the launcher
[14:59] <seb128> like the session one etc
[15:00] <bcurtiswx> well the one with the mail and empathy and gwibber tho?
[15:01] <seb128> it lists things which are not running
[15:01] <seb128> which the launcher doesn't do if you don't pin those
[15:02] <seb128> not sure it would be nice to clutter the launcher with things which are not running
[15:02] <seb128> it doesn't hurt to have the envelop icon in there and the launcher integration
[15:03] <seb128> it let the choice to use what you prefer
[15:03] <bcurtiswx> yup, can't disagree.  I like that eventually a right click will bring a list of unread messages from the launcher icons
[15:08] <bcurtiswx> just to get more opinion tho, not trying to start a full blown debate, but the launcher can perform the exact same tasks as the envelope icon besides having an easy accessible list of commonly used apps.  But these apps can show up upon clicking the ubuntu icon, and then the launcher would provide the rest of the actions the green envelope does
[15:09] <seb128> well you can open a bug about that, I like the envelop though
[15:10] <seb128> it's always on screen even when the launcher is hidden and it collect infos from all the messaging applications where the launcher you will have to right click on each one
[15:10] <seb128> so when you come back to your computer you can see what happened in one click
[15:10] <seb128> rather than doing a bunch of right clicking in the launcher
[15:11] <bcurtiswx> seeing the amount of pending messages requires no clicking even when the launcher is hidden, then the user can decide which they prefer to check on
[15:12] <seb128> right, but you don't have the details of names, etc
[15:12] <seb128> the indicator is also useful in classic GNOME where is no launcher
[15:13] <seb128> not sure why you want to spare those 20 pixels, just to get extra free space on the unity-panel where you can't add applets anyway?
[15:13] <bcurtiswx> yup, that is correct.  If consistency between the two is what we're going for then I can't really say my ideas would be better
[15:13] <bcurtiswx> seb128, a disclaimer for me would be Im not fully aware of the general idea the desktop team strives for, so I'm just throwing out a few ideas :)
[15:14] <seb128> well unity design is rather ayatana design driven
[15:14] <bcurtiswx> the envelope is ayatana as well?
[15:14] <seb128> so you should better suggest your ideas on bug reports or on their list ;-)
[15:14] <seb128> yes
[15:14] <seb128> unity and the indicators are ayatana projects
[15:15] <bcurtiswx> yeah I figured I'd try to come up with a mockup and bring it to the ayatana team
[15:15] <bcurtiswx> see how my image editing skillz are
[15:15] <seb128> ;-)
[15:30] <seb128> rodrigo_, do you have any clue about how to debug bug #639913?
[15:30] <ubot2> Launchpad bug 639913 in gnome-settings-daemon "gnome-settings-daemon random crash at session start (xorg badmatch error)" [Low,Confirmed] https://launchpad.net/bugs/639913
[15:30] <rodrigo_> seb128, looking..
[15:31] <seb128> rodrigo_, we regularly get bugs about that so it's an annoying issue for our users, not sure how to debug it though
[15:31] <rodrigo_> hmm, I was going to suggest to kill g-s-d and run it on gdb, but if it's random :(
[15:32] <rodrigo_> seb128, but the error message has some info:
[15:32] <rodrigo_> To debug your program, run it with the --sync command line
[15:32] <rodrigo_>    option to change this behavior. You can then get a meaningful
[15:32] <rodrigo_>    backtrace from your debugger if you break on the gdk_x_error()
[15:32] <seb128> rodrigo_, right, the issue is that it seems to happen only at session start
[15:32] <rodrigo_> those are indeed strange errors, I have seen that, for other apps, for years, once in a while
[15:32] <seb128> not easy to ask users to run under gdb at login
[15:32] <rodrigo_> right
[15:33] <rodrigo_> the full .xsession-errors might help
[15:44] <seb128> tedg, mterry, kenvandine: bug #708188 should really be fixed for natty
[15:44] <ubot2> Launchpad bug 708188 in indicator-application "softwares using libappindicator crash with SIGSEGV in theme_changed_cb()" [Medium,Triaged] https://launchpad.net/bugs/708188
[15:44] <seb128> if someone wants to claim it
[15:45] <mterry> seb128, seems bad, agreed.  I'm heads down right now on datetime dialog stuff, but if it's still unclaimed, can grab it
[15:46] <seb128> mterry, I will try to get a valgrind log since polkit-gnome-daemon crashes often when using update-manager
[15:46] <seb128> mterry, thanks
[15:46] <seb128> no hurry to fix it this week it's nothing new
[15:47] <tedg> seb128, Agreed.  It seems people like to change themes ;)
[15:47] <seb128> tedg, it has nothing to do with theme changes
[15:47] <seb128> tedg, I get it every 5 update-manager use here
[15:47] <tedg> Yes, I understand, I was more joking :)
[15:47] <seb128> ok ;-)
[15:49] <seb128> rodrigo_, btw did you talk to gdm upstream about the g-s-d races between login and session?
[15:49] <kenvandine> seb128, i think tedg is going to keep me pretty busy today
[15:50] <seb128> kenvandine, oh, it's not a today thing, it's a natty cycle thing, I was just pointing it for the record
[15:50] <Laney> I just upgraded to natty and it seems my /desktop/gnome/session/required_components/windowmanager setting is no longer respected
[15:50] <htorque> seb128, hello! https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/705498 - i never know which status to set in such situations? fix released/invalid?
[15:50] <ubot2> Ubuntu bug 705498 in compiz "Notifications should not show up on the unlock screen" [Low,New]
[15:50] <Laney> where did it move to?
[15:50] <seb128> htorque, there is no strong rules, if you know what fixed it fix released with a comment about it, otherwise invalid
[15:51] <seb128> Laney, it's using /usr/share/gnome-session/sessions
[15:51] <htorque> seb128, don't know what exactly fixed it, so setting it to invalid - thanks! :-)
[15:52] <Laney> seb128: how do I select which one to use? from gdm?
[15:52] <seb128> htorque, you're welcome
[15:52] <seb128> Laney, correct
[15:52] <rodrigo_> seb128, yes, but no answer, trying again
[15:52] <seb128> Laney, well gdm uses /usr/share/xsessions
[15:53] <seb128> Laney, which call gnome-session --session=<...>
[15:53] <seb128> Laney, where the ... is in the /usr/share/gnome-session/sessions
[15:53] <Laney> ah OK
[15:53] <Laney> looks like I can just copy 2d-gnome and change Required-windowmanager
[15:56] <Laney> is this an Ubuntu change or can I ask Debian to provide the file?
[15:56] <rodrigo_> seb128, just reassigned the upstream bug to gdm, forgot to that last time
[15:56] <seb128> rodrigo_, thanks
[15:56] <seb128> Laney, it's a GNOME3 thing upstream that didrocks backported to our current GNOME
[15:57] <seb128> Laney, so wait for debian to get GNOME3
[15:57] <Laney> sure
[16:02] <seb128> tedg, is the stacktrace on bug #720337 enough to work on the issue?
[16:03] <ubot2> Launchpad bug 720337 in indicator-appmenu "indicator-applet-appmenu crashed with SIGSEGV in dbusmenu_client_send_about_to_show()" [Medium,New] https://launchpad.net/bugs/720337
[16:14] <tedg> seb128, Not really, it seems to be a memory corruption error :(  Probably need valgrind
[16:42] <didrocks> seb128: DSO linking issue with gtk-doc, does it ring a bell?
[16:43] <seb128> didrocks, not really out of the fact that pitti mentioned some before
[16:43] <didrocks> before, like recently?
[16:45] <seb128> didrocks, like end of january but I don't think that was the same issue
[16:45] <didrocks> hum…
[16:47] <seb128> didrocks, what source is that?
[16:47] <didrocks> seb128: libunity-misc, trying to make dist with --enable-documentation
[16:47] <seb128> didrocks, http://launchpadlibrarian.net/62449433/libunity-misc_0.1.1-0ubuntu3_0.1.1-0ubuntu4.diff.gz
[16:47] <seb128> didrocks, did you get doko's patch?
[16:47] <seb128> didrocks, he fixed it in natty
[16:47] <didrocks> I don't think so
[16:48] <seb128> ok, so grab the patch from his upload I guess
[16:48] <didrocks> seb128: this one has been fixed by njpatel in trunk
[16:48] <didrocks> already
[16:49] <didrocks> x11
[16:49] <seb128> didrocks, ok, so maybe something similar
[16:49] <didrocks> but yeah, not the GTKDOC one
[16:51] <didrocks> seb128: ok, that should do it, thanks for pointing there :)
[16:52] <didrocks> a shame that it wasn't notified upstream (just checked the bug) though
[16:52] <seb128> didrocks, you're welcome, you got lucky I though that doko fixed some similar issues and ran into the libunity-misc example while trying to find one
[16:52] <seb128> didrocks, which made me think "could be what didrocks is on" ;-)
[16:53] <didrocks> seb128: hehe, yeah, I would have spent time in this Makefile.am :)
[16:53] <didrocks> seb128: btw, so today, I learnt that documentation Makefile is manual
[16:53] <didrocks> I was thinking that gtk-doc was handling everything as m4 macro
[16:53] <didrocks> seb128: works wayyyy better, thanks again :)
[16:54] <seb128> didrocks, yw
[16:54]  * didrocks reopens his book on libtool library versionning when ABI and API break
[17:57] <Sweetshark> 4
[17:58] <highvoltage> 5
[18:10] <chrisccoulson> 6
[18:10] <chrisccoulson> can anyone join in?
[18:10] <chrisccoulson> :)
[18:12] <Sweetshark> auuw, people already made fun of me on #libreoffice for failure to use irssi
[18:13] <Sweetshark> (... correctly)
[18:13] <chrisccoulson> heh :
[18:13] <chrisccoulson> )
[18:13] <chrisccoulson> hmmm, my zero key is failing
[18:14] <chrisccoulson> or it's got food stuck under it
[18:14] <chrisccoulson> most likely to be the latter
[18:14] <Sweetshark> chrisccoulson: ibm model m ftw!
[20:58] <chrisccoulson> w00t - http://hg.mozilla.org/mozilla-central/rev/ed3437b7c12b
[20:59] <chrisccoulson> that's going to rock on ambiance
[22:47] <robert_ancell> Does anyone happen to know what package provides the broadcast icon in the messaging indicator?
[23:52] <robert_ancell> TheMuso, should we update to the latest espeak?
[23:53] <TheMuso> robert_ancell: its on my to do list for this next few days.
[23:53] <TheMuso> I have a git branch for ubuntu in the debian pkg-a11y repo, so will do the work there.