[06:30] <astraljava> pleia2: knome: This Sunday could work fine, yeah.
[06:31] <pleia2> great :)
[06:31] <pleia2> what time UTC is good for you? (keeping in mind that it's 23:30 yesterday right now here ;))
[06:38] <astraljava> pleia2: I should be awake from about 0600 UTC until 2100 UTC, and thus far I'm only watching the ice hockey finals on that day. Well maybe go roller-skating if it's a nice weather. :) But that means, any time of day between those times is fine.
[06:40] <pleia2> ok cool, I'll probably pop on around 17:00 and give you a nudge
[06:41] <astraljava> That's great! Thanks for pushing things. I've been surprisingly busy on this early cycle, so haven't had a chance of getting a control really, yet.
[06:41] <astraljava> I'll try to get up to speed before our meeting.
[08:32] <knome> 17 utc sounds good
[09:55] <ochosi> morning everyone
[09:57] <knome> hey ochosi
[09:57] <ochosi> hi
[10:05] <ochosi> bbl
[11:35] <knome> clearly a troll in #x earlier
[12:03] <astraljava> Obviously.
[12:04] <knome> hai!
[12:04]  * knome has now a few kg's less hair
[12:07] <bluesabre_laptop> ochosi: Fixed and added some stuff to catfish.  Default location is home, search starts when you hit enter.  Locate is now a backup/additional suggestion backend.
[12:30] <bluesabre_laptop> bbl
[12:54] <mr_pouit> ochosi: is blackbird ~usable~? (i.e. can I upload it to quantal, or is it too early?)
[13:08] <ochosi> mr_pouit: well, it's kinda usable, the gtk3 version still sucks though :)
[13:08] <ochosi> mr_pouit: maybe in a similar state as albatross, so the answer is maybe yes ;)
[13:08] <ochosi> bluesabre_laptop: cool, pulling from bzr right now!
[13:10] <ochosi> bluesabre_laptop: works great! btw, it's really funny how the locate/zeitgeist suggestions are fast and the find-search is slow :D
[13:26] <ochosi> bluesabre: not sure you read the messages i posted before
[13:26] <ochosi> bluesabre: anyway, seems to be working great
[13:43] <mr_pouit> ochosi: ok, do you have a short desc for blackbird? (check the description of shimmer-themes if you want to change something too ;-)
[13:43] <ochosi> mr_pouit: you mean the desc in launchpad?
[13:44] <mr_pouit> of the package yeah (I guess it shows up on lp too)
[13:44] <ochosi> for blackbird i'll quickly update the README if that's fine with you
[13:52] <ochosi> mr_pouit: the desc of the package looks ok to me
[13:52] <ochosi> mr_pouit: i'll pastebin you a similar paragraph about blackbird (the readme is really something different)
[14:13] <bluesabre> ochosi, thanks!  Yeah, I wasn't able to see the previous messages
[14:18] <ochosi> bluesabre: ah ok, all i said before that it's funny how the suggestions with locate/zeitgeist are fast and the actual search with find is slow =)
[14:18] <bluesabre> haha
[14:19] <ochosi> is catfish seriously using glade?
[14:19] <bluesabre> yup
[14:19] <bluesabre> well
[14:19] <bluesabre> kinda
[14:20] <ochosi> i thought glade was superseded by something else for gtk3
[14:20] <bluesabre> Kinda
[14:20] <ochosi> mkay
[14:20] <bluesabre> Glade is now done with GtkBuilder
[14:21] <ochosi> ah right, that was it
[14:22] <ochosi> i'm fiddling with the layout now
[14:22] <ochosi> just dropped the "close" button :)
[14:23] <ochosi> is there also a GUI for gtkbuilder like there was for glade?
[14:24] <bluesabre> The newer version of glade
[14:24] <bluesabre> I think there are 2 packages now
[14:24] <bluesabre> glade and glade-gtk2
[14:24] <bluesabre> glade being the newer one
[14:41] <ochosi> bluesabre: quick and dirty :p http://www.zimagez.com/zimage/screenshot-05182012-044051pm.php
[14:41] <ochosi> i mean i could now drop the stuff in the sidebar entirely to get the layout, but then again, doing that without adding a menu is limiting the functionality quite a bit :)
[15:01] <bluesabre> True.  I was investigating how to make a button with a menu, which is easy enough, but to get the darn menu to fall beneath the button (instead of the cursor) seems to be a challenge
[15:02] <ochosi> there is certainly c-code i can point you to that does that
[15:02] <ochosi> i can also offer perl :)
[15:03] <bluesabre> haha
[15:03] <ochosi> whatever seems easier for you
[15:03] <ochosi> or in fact vala, not c
[15:03] <bluesabre> sure, send me something and I can have a look at it
[15:15] <ochosi> bluesabre: check this https://github.com/shimmerproject/gmusicbrowser/blob/4a0644db1f84f6d5f65e3bf50b3af303a8515329/gmusicbrowser_layout.pm#L3841
[15:15] <ochosi> this creates a toggle-button that stays pressed as long as the menu is open and displays a normal gtk-menu below it
[15:15] <ochosi> so pretty much exactly what elementary does in its apps
[15:28] <ochosi> bluesabre: i can also try to dig up the midori code for the popup menu (that would be the vala-example)
[15:36] <bluesabre> that's all right.  I'll figure it out.  The popup function has a pos parameter which you pass to it and its supposed to be a callback function.  Haven't had much luck with that working though.
[15:37] <bluesabre> I'd set it up, and then python would segfault.  I'll ask around to find something out
[15:47] <satop> why a separate audio and video player in xubuntu 12.10 ? lets use vlc for both as i already did
[15:48] <ochosi> satop: vlc is qt and therefore not an option
[15:49] <ochosi> bluesabre: just asked in elementary, seems like this is a python app with the menu-button implemented: http://bazaar.launchpad.net/~elementary-apps/dexter-rolodex/dexter/files
[15:58] <bluesabre> O.o sweet jesus it worked
[15:58] <ochosi> cool!
[15:59] <satop> what has Jesus to do with it
[16:00] <ochosi> bluesabre: have you pushed it already? :)
[16:00] <bluesabre> not yet.  I was just testing it.  Still want the interface to look like this?  http://imagebin.org/212685
[16:02] <ochosi> i'd say so, at least i haven't had any better ideas up to now :)
[16:02] <ochosi> theoretically we could throw a file-type filter somewhere
[16:02] <ochosi> that's also something people might wanna access quickly
[16:03] <ochosi> but anyway, i think cleaning up the interface like this is a good start
[16:03] <ochosi> we can always add new stuff to it
[16:04] <bluesabre> alrighty.  I'll probably get on that here shortly.
[16:04] <ochosi> great!
[16:17] <bluesabre> ochosi: thoughts on limits, filtering, and search method in an "advanced" dialog?
[16:21] <ochosi> bluesabre: we could make the advanced dialog a toolbar underneath the searchbar
[16:21] <ochosi> bluesabre: i'm not 100% happy about the filetype widget, but i have to think of something else first
[16:22] <bluesabre> ochosi: want to have a button to show the advanced toolbar?  if so, have a preference where?
[16:23] <ochosi> i'm wondering whether it's too hidden if we throw it in the menu
[16:23] <ochosi> with a gtk-check "Advanced search options" or something
[16:23] <ochosi> and if it's ticked, the toolbar is there, otherwise it's not (not==default)
[16:24] <bluesabre> that doesn't sound like a bad idea
[16:24] <ochosi> btw, one more thing we should fix at some point is set the window-icon correctly
[16:24] <ochosi> at the moment it's hardcoded in glade
[16:25] <bluesabre> yeah
[16:25] <ochosi> which is why it doesn't show up in xfwm-tabwin (alt+tab)
[16:25] <ochosi> and it's not themeable
[16:25] <ochosi> i can draw a new appicon for it if we want something more fancy than a simple searchglass :)
[16:26] <bluesabre> maybe
[16:27] <ochosi> for the filetypes: maybe we could show a sidebar or something that shows a list of the filetypes
[16:27] <ochosi> that filters the result-set
[16:27] <ochosi> so they wouldn't be just pre-defined but based on the actual result-set
[16:27] <ochosi> (just an idea)
[16:31] <laite> perhaps something similar than what comes in google's imagesearch, the sidebar with a few date/type/etc. options (just an idea :)
[16:32] <ochosi> laite: yeah, probably a sidebar is better than a toolbar for the advanced search stuff
[16:33] <bluesabre> I agree.  The extra toolbar begins to get cluttered with options anyway
[16:34] <ochosi> google might not be the worst source of inspiration for the search :)
[16:36] <ochosi> i'll try to come up with a mockup for the advanced search mode a bit later today/tonight
[16:37] <bluesabre> I might have a rough version of an advanced sidebar sometime within the hour
[16:37] <ochosi> wow nice
[16:38] <bluesabre> glade and python let you do things quickly
[16:38] <bluesabre> sometimes without thinking
[16:38] <ochosi> :)
[16:38] <ochosi> never used glade
[16:38] <ochosi> always did my packing with perl by hand
[16:38] <bluesabre> (which occassionally comes back to bite you in the future)
[16:38] <ochosi> which is fun, but also a bit tedious
[16:39] <ochosi> yeah, maybe if/when there's a vala-port ;)
[16:39] <ochosi> although i'm not sure python would be the bottleneck with this app anyway
[16:39] <ochosi> i mean the interface is minimal
[16:39] <bluesabre> yeah
[16:39] <bluesabre> the app is bottlenecked no matter what you do because it will always rely on system calls
[16:40] <ochosi> mhm
[16:42] <ochosi> i guess at some point we should ask kalikiana whether he minds if we supersede the old catfish with this
[16:42] <ochosi> so that it can get packaged properly (and everywhere)
[16:43] <bluesabre> true
[16:43] <ochosi> (i think he won't mind)
[16:43] <bluesabre> according to his page, he's looking for a new maintainer
[16:52] <ochosi> btw, this also sounds like a good idea "add filter for executables/ desktop files"
[16:52] <bluesabre> yeah
[16:52] <ochosi> and not that hard to do
[16:52] <bluesabre> saw the todo list too, huh?  :D
[16:52] <ochosi> hehe
[16:52] <ochosi> yeah
[16:52] <ochosi> cleaning up my tabs ;)
[16:53] <ochosi> ok folks, i'll be back in a bit
[16:55] <bluesabre> ochosi: glade preview of sidebar: http://imagebin.org/212897
[16:56] <ochosi> very cool!
[16:56] <ochosi> let's really make this look a bit like google-images
[16:56] <bluesabre> good idea
[16:56] <ochosi> maybe a text-only list of types (Image,Video,Music,Application, etc)
[16:57] <ochosi> i'm wondering whether we should swap the combo and the search-entry...
[16:57] <bluesabre> No requests for filtering on color size :P
[16:57] <ochosi> not sure what's the more "logical" place for it
[16:58] <bluesabre> *color
[16:58] <ochosi> hehe
[16:58] <ochosi> well, nothing too image-specific i'd say
[16:58] <ochosi> ok, now i really gotta run
[16:58] <ochosi> bbiab
[17:38] <bluesabre> ochosi:  something a little more like this?  http://imagebin.org/212909
[17:50] <ochosi> not sure the limit-results is needed that much
[17:50] <ochosi> the rest looks very good already!
[17:50] <ochosi> the search method should probably also go somewhere else
[17:51] <ochosi> i'm wondering whether we should use locate-only by default
[17:51] <bluesabre> locate doesn't find new files though
[17:51] <ochosi> and then show an inforbar or something to search with find
[17:51] <bluesabre> you have to update the database, which is either done automatically or by admin
[17:51] <bluesabre> ah
[17:52] <ochosi> i'm thinking like this: first show a quick list of results – then ask the user: did you not find the droid you were looking for? search thoroughly
[17:52] <bluesabre> lol
[17:52] <bluesabre> that might be a good idea
[17:53] <ochosi> just to take the edge of the long wait for search results with find
[17:53] <ochosi> i don't know enough about how you get the result-sets, but another way would be to search with locate and incrementally add results found with find
[17:54] <bluesabre> not a bad idea
[17:54] <ochosi> i mean letting locate and find run in two different threads
[17:54] <ochosi> not sure how easy that is
[17:54] <ochosi> but then the user can always cancel when his files are found
[17:54] <bluesabre> threads can get finicky
[17:55] <ochosi> yeah, maybe the other variant is easier to implement and good enough
[17:55] <bluesabre> I kinda like the idea of a second, super search
[17:55] <ochosi> mhm
[17:55] <ochosi> maybe we could also add a menuitem to update the search-index
[17:57] <ochosi> about the sidebar: let's not use italic headers for that and drop as many labels as we can :) (less work for translators)
[17:57] <ochosi> i think it's intuitively clear what the different items filter on
[17:58] <ochosi> s/Past week/Last week/ (but yeah, up to you, you're the native speaker ;) )
[17:59] <bluesabre> I just copied google
[17:59] <ochosi> ah
[17:59] <ochosi> interesting, didn't notice it there
[17:59] <ochosi> oh noes, my google is german... :)
[17:59] <bluesabre> haha
[18:00] <bluesabre> yeah, this version of the interface will have the sidebar, menu, and infobar
[18:00] <bluesabre> once I can finish putting it together in a little bit
[18:00] <bluesabre> lol
[18:00] <ochosi> hehe
[18:01] <ochosi> so for the sidebar, it should contain only this imo: "Any time|Past week|Other|Custom<Separator/spacer>Documents|Pictures|Music|Videos|Applications|Other|Custom"
[18:02] <ochosi> all the other labels and stuff are kinda too much
[18:05] <bluesabre> I agree.  I think Limit Results might be beneficial to keep around though.
[18:05] <bluesabre> but maybe not
[18:06] <bluesabre> I don't think most tools have any option to limit how many results you get back
[18:07] <ochosi> i'm not sure i see the point of limiting results
[18:07] <ochosi> the search isn't faster
[18:07] <bluesabre> yeah
[18:07] <bluesabre> let's throw it out
[18:08] <bluesabre> then the sidebar is just for filtering
[18:08] <bluesabre> and can be much cleaner
[18:09] <ochosi> mhm
[18:09] <ochosi> we can always put stuff back in
[18:10] <ochosi> but there are maybe other – more useful – filters we might wanna add
[18:13] <ochosi> and let's maybe swap the search-entry and the folder-selector
[18:13] <ochosi> it's somehow more logical in terms of hierarchy
[18:15] <bluesabre> http://imagebin.org/212915
[18:17] <ochosi> let's drop the "filter results" label as well :)
[18:17] <bluesabre> Agreed
[18:18] <ochosi> let's try to drop the other two as well (maybe just comment them out) to see whether it still looks intuitive
[18:20] <bluesabre> maybe  http://imagebin.org/212916
[18:23] <ochosi> looks good
[18:24] <ochosi> maybe a spacer on top of anytime
[18:25] <bluesabre> that helps
[18:32] <bluesabre> oh yeah, the reason for the search method was so you could search with beagle or other backends
[18:32] <bluesabre> but...
[18:32] <bluesabre> does anybody use beagle anymore?
[18:38]  * micahg thought we dropped that from the archive
[18:39] <ochosi> yeah, i think locate and find and zeitgeist are sufficient
[18:39] <micahg> yep, dropped in natty IIRC
[18:39] <ochosi> the only other alternative i know of is tracker
[19:15] <bluesabre> ochosi: it might be a little bit.  the interface is plugged in and shows now, but for some reason my queries no longer work
[19:15] <ochosi> hihi
[19:15] <ochosi> ok
[19:15] <ochosi> no worries
[19:15] <Unit193> ochosi: See me comment on searchmonkeye?
[19:16] <ochosi> Unit193: yeah, haven't looked at it yet
[19:16] <ochosi> bbiab
[19:16] <Unit193> Coolio.
[19:18] <bluesabre> ochosi: nvm, I had exact search on.  A few more tweaks and I'll upload the latest.
[19:20] <bluesabre> http://imagebin.org/212923
[19:23] <ochosi> cool
[19:34] <bluesabre> ochosi: check it out.  filters currently do not work though.
[20:08] <ochosi> bluesabre: will do in one sec, going for a smoke :)
[20:10] <mr_pouit> Xubuntu will be less great because of that smoke! ;P
[20:12] <bluesabre> yes, ochosi, mr_pouit is right.  :D
[20:46] <bluesabre> ochosi: went ahead and committed another change.  bzr commit -m "Find icon changes to cancel icon when running.  Sidebar widgets can now enable/disable custom buttons."
[21:44] <micahg> mr_pouit: I took care of ristretto
[21:47]  * GridCube ponders if he got into the #mafia channel
[22:04] <Unit193> I kinda read it the same as GridCube. ;P
[22:04] <GridCube> ristretto is gone Unit193, its gone, dont think about it anymore
[22:26] <ochosi> mr_pouit: hihi
[22:31] <ochosi> bluesabre_laptop: looks and works great!
[22:32] <ochosi> well, that was a longish cigarette...
[22:53] <micahg> mr_pouit: mousepad done as well


[12:16] <Burgwork> ogra, http://littlewizard.sourceforge.net/ <- have you heard of this? (seems to c or c++ gtk)
[12:16] <ogra> Burgwork, sweet
[12:17] <Burgwork> http://lists.debian.org/debian-devel/2006/02/msg00578.html
[12:17] <Burgwork> already itp'ed
[12:56] <paolob_> Hi guys. I have ubuntu installed. What packages I must install to have edubuntu? thank you1
[12:57] <ogra> paolob_, do you want the edubuntu classrom server or only a edubuntu desktop ?
[12:57] <paolob_> desktop
[12:57] <ogra> then install edubuntu-desktop :)
[12:57] <paolob_> ogra, thank you
[12:58] <paolob_> ogra, what about the content filtering, will it be ready for dapper?
[12:58] <ogra> nope
[12:59] <paolob_> ogra, I can't install edubuntu-desktop, it installs too many packages. What are the edubuntu specific ones?
[12:59] <paolob_> ogra (content filtering) :-( is there any problem?
[01:01] <ogra> yes, for the existing implementations you have to provide regulary updated of black and whitelists ...
[01:01] <ogra> and you have to tweak the packages ...
[01:01] <ogra> since thats no option i looked into different solutions ...
[01:02] <paolob_> will be there a solution with dapper?
[01:02] <ogra> i plan to include the willow conten filter for dapper+1 it works like a spam filter and teaches itself which content is evil
[01:03] <ogra> in dapper there is the one that was in hoary, breezy and warty already ... squidguard and squid ...
[01:03] <paolob_> ogra, but in the meanwhile what can I do in order to have content filtering? squidguard?
[01:03] <ogra> but it has a high maintenance level ... which williw avoids ...
[01:03] <ogra> *willow
[01:04] <ogra> http://www.digitallumber.com/software/willow/
[01:04] <paolob_> ok, now, what package install me the ltsp server in order to get a edubuntu from ubuntu?
[01:04] <ogra> see the ThinClientHowto on the ubuntu wiki
[01:04] <Burgwork> http://users.lichtsnel.nl/~spacey/?p=129 <-- talks about willow and edubuntu
[01:05] <ogra> Burgwork, yes, he's a everyday guest in this channel, you met him at UBZ
[01:06] <ogra> Burgwork, actually he's here :)
[01:06] <Burgwork> hmm, don't remember him (too many new people)
[01:06] <ogra> short curly hair ... hung around with Treenaks ...
[01:06] <Burgwork> ok, rings bells
[01:07] <ogra> from nl
[01:08] <ogra> i'm really sad i didnt have the time for willow this release ...
[01:08] <ogra> its the coolest content filter i've seen so far
[01:08] <Burgwork> does it do any whitelist/blacklist?
[01:09] <Burgwork> one very cool feature is a whitelist, for a fixed function machine
[01:09] <Burgwork> ie, you can only go to one website
[01:09] <ogra> it does white/blacklist if you want to use it ... but the coolest feature is bayesian filtering ...
[01:10] <Burgwork> yes
[01:10] <ogra> it even does pam based user access control if you want
[01:11] <paolob_> ogra, excuse me, I can't find the information about the ltsp server edubuntu packets to install...
[01:12] <ogra> its the ThinClientHowto
[01:12] <ogra> on the wiki
[01:13] <ogra> wiki.ubuntu.com/ThinClientHowto
[01:13] <paolob_> ogra, ok
[01:51] <paolob_> ogra, I'm doing what wiki.ubuntu.com/ThinClientHowto says, but I see that I haven't the i385 dir in /opt/ltsp/  What am I missing?
[03:07] <ogra> phew
[03:15] <signifer123> bah...
[07:24] <lucasvo> ogra: ping
[07:28] <TOZTWO> Will edubuntu use GNOME 2.14?
[07:30] <lucasvo> TOZTWO: it uses whatever ubuntu uses
[07:31] <lucasvo> atm on dapper I have 2.14
[07:31] <lucasvo> eh I mean 2.13
[07:53] <TOZTWO> 2.14 will be released in late March.
[07:53] <TOZTWO> I was wondering if it was planned for inclusion.
[07:54] <TOZTWO> It has some "Groups" settings.
[07:55] <TOZTWO> You can lock down the UI for inexperienced users, and allow hackers full freedoms and abilities.
[02:18] <mhz> re
[02:18] <mhz> hi all
[02:20] <Yagisan> G'day mhz
[02:21] <mhz> Yagisan: my man!!
[02:21] <mhz> Yagisan: how are you doing?
[02:22] <Yagisan> mhz: not good. 2 customers this week have refused to pay. It seems to be a planned thing, as they know each other. 1 even disconnected their phone.
[02:23] <Yagisan> mhz: put me out of pocket $200 AUD
[02:23] <mhz> damn!
[02:23] <Yagisan> mhz: and it's my daughter Kate's birthday on monday
[02:25] <mhz> Yagisan: it seems you are not having a good 2006 start
[02:25] <Yagisan> mhz: nope. quite shit actually
[02:25] <Yagisan> mhz: and yourself ?
[02:26] <mhz> same
[02:26] <mhz> :(
[02:26] <mhz> at least you are not the only one
[02:26] <mhz> hehehe
[02:26] <mhz> or coffee
[02:27] <mhz> Yagisan: maybe the good thing, so far, is that I got a sponsor who will provide the infrastructure I need to make a nice event to promote IT and Education integration
[02:27] <Yagisan> excellent, with that glass of milk coating my stomach, I can consume vast quantities of alcohol tonight ;)
[02:28] <Yagisan> mhz: tha's good new
[02:28] <Yagisan> s/tha's/that's
[02:32] <Yagisan> mhz: saw something amusing on the forums. It was a thread about my private repo
[02:32] <mhz> ohh? the game one?
[02:32] <Yagisan> mhz: yep - that one
[02:34] <Yagisan> mhz: someone wanted to know if it was trustworthy and should they use it.
[02:34] <mhz> Yagisan: is it trustworthy ?
[02:34] <Yagisan> mhz: there are some more cool games in revu
[02:35] <mhz> revu?
[02:37] <Yagisan> mhz: revu - proposed new packages for ubuntu
[02:37] <Yagisan> mhz: trustworthy - they wanted to know if it had viruses etc, would it break their ubuntu
[02:38] <Yagisan> mhz: revu - http://revu.tauware.de/
[02:56] <Yagisan> wow - I just crashed ubuntu
[02:57] <Kamping_Kaiser> nice effort
[02:57] <kenroy_> hello
[02:58] <kenroy_> what does edubuntu offers that the other ubuntus don't
[03:02] <Kamping_Kaiser> a totaly dead channel :0
[03:13] <mhz> kenroy_: basically,.. edubuntu = LTSP + edu applications + themes and background aimed for schools
[03:13] <mhz> Kamping_Kaiser: and maybe you are trying this channel on hours that most of us are either sleeping or eating or in family time :D
[03:14] <kenroy_> nice
[03:14] <kenroy_> get the kids involved in linux
[03:14] <mhz> Kamping_Kaiser: i am sure that during 12 UTC and 22 UTC this is more crowded
[03:14] <Kamping_Kaiser> mhz: quite probably :)
[03:14] <mhz> kenroy_: yup
[03:14] <mhz> Kamping_Kaiser: on working days, not weekends :D
[03:15] <mhz> Kamping_Kaiser: as you can see, I am about having breffast now
[03:15] <mhz> :D
[03:15] <kenroy_> you guys tool the number one spot for bet internet browser from microsoft and now talking away the #1 position for school desktop from them
[03:15] <mhz_food> kenroy_: hehehe, well it was not planned
[03:15] <mhz_food> but cool!
[03:15] <jsgotangco> hrmmm
[03:16] <mhz_food> jsgotangco: hey mon
[03:16] <jsgotangco> mhz_food, what's up man?
[03:16] <mhz_food> about to have breakfast
[03:16] <jsgotangco> i already did my screenshots :P
[03:16] <mhz_food> ohh
[03:16] <jsgotangco> breakfast? and we're about to sleep here!
[03:16] <Kamping_Kaiser> mhz_food: <grin>
[03:17] <mhz_food> jsgotangco: hehehe, IC magic
[03:17] <mhz_food> jsgotangco: hehehe, IRC magic
[03:17] <Kamping_Kaiser> jsgotangco: i was gong to catch you about EdU doc as well.
[03:17] <mhz_food> Yagisan: maybe it was meant to be
[03:17] <mhz_food> :)
[03:17] <kenroy_> but its good
[03:17] <jsgotangco> Kamping_Kaiser, yeah, its me and mhz_food planning for it
[03:17] <kenroy_> i never enjoyed linux until now
[03:17] <Kamping_Kaiser> ok :)
[03:18] <mhz_food> kenroy_: I never enjoyed linux until I quit Apple machines
[03:18] <kenroy_> ok
[03:18] <kenroy_> well i never used a mac
[03:18] <mhz_food> okis guys... wife complaining .. breakfast time!
[03:19] <mhz_food> see ya in a couple of hours or less
[03:22] <Kamping_Kaiser> see you tomorrow mhz_food


[19:14] <belkinsa> akshmakov, hey.  You missed the session but we have the video
[19:14] <akshmakov> UTC messed me up again
[19:14] <akshmakov> sorry about that
[19:14] <belkinsa> It's cool.
[19:15] <akshmakov> Just for introductions Im at UCSF and UCB, and to development on open source projects for my work here
[19:15] <akshmakov> Hence my interest in the scientist group
[19:15] <belkinsa> Cool, maybe you can join the team
[19:16] <akshmakov> Perhaps, depends on what needs to be done
[19:17] <akshmakov> And if I can help with that
[19:17] <akshmakov> what is the best way to get in contact with the group?
[19:18] <belkinsa> The LP team's mailing-list, you need to join
[19:19] <belkinsa> https://launchpad.net/~ubuntu-scientists
[19:20] <akshmakov> Done
[19:21] <belkinsa> Thanks fellow comrade :)
[19:21] <akshmakov> I am both interested in contributing to the project as well as reaching out for inclusion on behalf of our projects here
[19:22] <belkinsa> Cool.
[19:22]  * belkinsa is trying to multitask
[19:22] <belkinsa> I'm in the track summaries Hangout
[19:22] <akshmakov> Its ok, we can migrate discussion to email for less on-the-spot
[19:23] <belkinsa> Sure.
[19:23] <akshmakov> Oh, I can move to the hangout
[19:23] <akshmakov> one sec
[19:24] <akshmakov> a link would be swell
[19:24] <belkinsa> You can't join it, it's only for the leads
[19:24] <belkinsa> http://summit.ubuntu.com/uos-1406/meeting/22309/closing-plenary-and-track-summaries/
[19:24] <akshmakov> Just figured that out, I'm watching the stream
[19:25] <akshmakov> Anyway, selling ubuntu to scientists is something I do daily, I would love to help you guys out
[19:25] <belkinsa> Way cool!
[19:26] <akshmakov> We will keep in touch through the team list, I'll be around.
[19:26] <belkinsa> Alright, thanks again.
[19:27] <akshmakov> coffee time, goodbye, sorry for missing the hangout.
[19:27] <belkinsa> Its' cool.


[17:36] <pavolzetor> "Publish your picture on Facebook"
[17:36] <pavolzetor> where can I translate this string?
[17:36] <pavolzetor> it is in Online accounts


[08:31] <zhangchao> hello,all
[08:31] <zhangchao> it's meeting time
[08:34] <handsome_feng> hi
[08:36] <handsome_feng> @Trevinho @hikiko
[08:45] <zhangchao> hi,willcooke
[08:46] <willcooke> hi zhangchao
[08:49] <zhangchao> marco have not come
[08:51] <zhangchao> so , we  put off  this meeting?
[08:54] <zhangchao> we will send email to Marco to discuss
[08:55] <willcooke> sorry zhangchao, I don't know where he is this morninig
[08:55] <willcooke> I will chase him
[08:55] <willcooke> yeah, please follow up my email
[08:56] <zhangchao> willcooke: OK, sure
[08:58] <handsome_feng> ok, so, communicate by e-mails, bye
[08:59] <zhangchao> thanks,bye
[09:26] <Trevinho> handsome_feng: ohhhhh... Sorry I forgot the meeting :-(
[09:26] <Trevinho> I got no notification
[09:26] <Trevinho> sorrrryyyyyyyyyyyy
[09:27] <Trevinho> willcooke: sorry :-(
[09:28] <hikiko> hey...
[09:28] <hikiko> same here :(
[09:30] <handsome_feng> :) i'm coming
[09:33] <handsome_feng>  I was just writing emails
[09:53] <hikiko> well for some reason
[09:54] <hikiko> I get notifications about the meeting 1 hour later
[09:54] <hikiko> \m/
[10:23] <Trevinho> We did the meeting anyway with handsome_feng. Log at https://wiki.ubuntu.com/Ubuntu Kylin/Meeting/2015/20151203


[02:24] <zul> uh dont you have to be a student?
[07:17] <fabbione> morning
[08:21] <lamont> fabbione: tomorrow I'll push -pa1 for hppa, and roll patches
[08:21] <fabbione> lamont: cool
[08:22] <fabbione> tomorrow might be a good day to upload the kernel
[10:22] <chmj> morning
[02:38] <zul> morning
[02:41] <fabbione> hey zul
[02:42] <zul> hey fabbione
[03:18] <chmj> fabbione: should I try to find the right url base for the drivers ?
[03:18] <fabbione> chmj: yes please
[03:19] <chmj> ok
[03:19] <chmj> just finished reformating it
[03:19] <chmj> how do you feel about tabs ?
[03:19] <fabbione> tabs are fine
[03:19] <chmj> ok
[03:20] <zul> is it in the wiki?
[03:20] <fabbione> zul: debian/external-drivers?
[03:20] <zul> i thought it was on the wiki nm
[04:09] <Mithrandir> fabbione: weren't you supposed to tell me how to debug acx today? :-)
[06:22] <zul> heh now i can buy chucksuperporn.xxx
[06:44] <fabbione> Mithrandir: sorry, but i did completely crashed today
[06:44] <fabbione> zul: eheheh
[06:45] <Mithrandir> fabbione: as would my acx if I had booted your kernel. :-P
[06:46] <fabbione> Mithrandir: gimme 2 minutes to wake up :)
[06:46] <Mithrandir> fabbione: sure.
[06:54] <fabbione> Mithrandir: the driver is already compiled with ACX_DEBUG by default
[06:54] <fabbione> so there is not much that needs to be done there...
[06:54] <fabbione> let see what kind of info we can find
[06:56] <Mithrandir> one problem here is that the whole system just freezes.
[06:58] <fabbione> is there anything in the logs?
[06:59] <Mithrandir> no
[06:59] <fabbione> so the thing is.. if it is loaded before X it crashes
[06:59] <Mithrandir> there's a panic on the screen; I'm going to up the resolution so I can see what it says.
[06:59] <fabbione> otherwise it works
[06:59] <Mithrandir> no, then it works for a while then crashes
[06:59] <fabbione> oh a panic would help
[06:59] <fabbione> if you can hand copy it would be great
[06:59] <fabbione> i need to go now.. so take your time
[07:00] <fabbione> Mithrandir: either stick it in a bug with all the info or send it via email
[07:00] <Mithrandir> I'll see what I can do
[07:00] <fabbione> ok
[07:01] <fabbione> i am off


[03:44] <HappySlappyFace> eyo
[03:44] <HappySlappyFace> was passing by while xubuntu installs on my laptop
[03:44] <HappySlappyFace> hope everyone having a good day
[09:10] <jlj> Hey, yeah, good so far, thanks. Hope the install went well; I'd imagine you would have commented were it otherwise. :-)
[17:10] <fiorelisa> Hello, I’m trying to install xubuntu 20.04 LTS on an old emachines netbook from a flashed USB. Trial version was fine, so I proceeded to remove windows 7 and install. Towards the end of xubuntu installation, an error message says “the system log from your installation contains an error”. Could anyone help me? Thanks a lot!
[17:16] <fiorelisa> Please can anyone help? I don’t know where to start from with system log issues..
[17:18] <Maik> !patience
[17:19] <fiorelisa> OK, thank you
[21:48] <xu-help12w> Hi, is the a pgp key I can check xubuntu 20.04 x64 against?
[21:59] <kotek14> xu-help12w: what is youe goal?
[21:59] <kotek14> Your*
[23:31] <xu-help12w> I guess I don't have one if the the software isn't signed lol
[23:32] <xu-help12w> if it is signed, then I'd hope to verify the signature.


[15:59] <Asuran> hi i got some issue with caught with wavemon on 18.04 with wifi. something seems to loop over my wlan card, even the activity diode blinks. but tcpdump didnt showed  any supisscous. i tried mobile wifi hotspot to see if its my router, but it seems its a ubuntu bug
[15:59] <Asuran> problem is i cant determine what it is
[16:01] <Asuran> it appered after using firefox but it went away. today it continues doing so, it doesnt go away
[16:01] <Asuran> it got triggered when i was using firefox (the installed version of it)
[16:02] <Asuran> in main ubuntu channel i cant get help for this
[16:02] <Asuran> and if its bug you may be interested also in fixing it
[16:04] <Asuran> so basicly i just want to know how i can get the problem inspected. it seems for this i would have to put card into monitor mode? but it seems it comes from ubuntu, maybe some wifi thing which is broken with the driver maybe
[16:04] <Asuran> on other distros this issues wasnt there with this card and card seems to work fine
[16:08] <tomreyn> the channel topic seems to state "Devel of Ubuntu (not support or app devel) [..] #ubuntu for support and discussion of Trusty-Bionic"
[16:09] <Asuran> yea saw that too late
[16:09] <Asuran> i guess it should be fine i dont ask for support like fix my problem, i try to figure out if there even is a problem and the main channel cant help or idk
[16:10] <Asuran> if its bug its definitly devel related
[16:10] <nacc> Asuran: did you file a bug?
[16:10] <Asuran> nope because i dont got any data except wavemon
[16:11] <Asuran> i need more imformation in troublshooting this but i cant do it alone
[16:11] <Asuran> it seems some ubuntu misconfig is maybe present or the driver for rtl2800pci is broken
[16:11] <Asuran> but idk since i cant get any informations due to the fact im not familiar with this kind of troubles
[16:13] <Asuran> if i would open a bug with just: wavemon shows unexpected packets then i would get discussion for nothing
[16:13] <Asuran> and i got already one in main chat which was helpful
[16:13] <Asuran> thats why i even came this far
[16:13] <Asuran> but now it seems to be too low level for me because my card doesnt support monitor mode
[16:13] <nacc> Asuran: you should file a bug, and it should be triaged by someone who can help there
[16:14] <Asuran> and thanks to the wavemon tip it seems something from ubuntu is sending to gateway and prodcues RX
[16:14] <Asuran> can you maybe tell me if you know what i could try to find any informations like a logfile
[16:15] <Asuran> i tried journalctl for networkmanager but it isnt low level enough
[16:15] <rbasak> #ubuntu is the right place to ask that kind of question.
[16:15] <Asuran> definitly no
[16:15] <Asuran> cuz this question is too hard it seems for there
[16:15] <rbasak> That doesn't make this the right place to ask that question.
[16:15]  * Faux winces.
[16:15] <Asuran> i already discussed with them there about this half an hour
[16:16] <rbasak> You might try somewhere that doesn't rely on people being instantly online.
[16:16] <rbasak> Eg. askubuntu.com
[16:16] <Asuran> you are developers who contrinbute to ubuntu?
[16:16] <Asuran> rbasak i dont ask you for find my issue, i asked if you could give me a tip what i should look into
[16:16] <rbasak> See https://community.ubuntu.com/t/community-support/709 for where to go to get help.
[16:16] <Asuran> and i did this cuz i thought devs know this stuff more then in #ubuntu
[16:16] <rbasak> This channel is for development.
[16:17] <rbasak> Some developers also participate in community support channels.
[16:17] <Asuran> rbasak: are you a developer?
[16:17] <rbasak> By asking here, you're eliminating a large number of people who may be able to help.
[16:17] <rbasak> Please use #ubuntu, or any other option listed at https://community.ubuntu.com/t/community-support/709
[16:18] <Asuran> nah i let this bug be then i thought switching to ubuntu but if people dont care bugs its ok to me sorry for bothering
[16:18] <wxl> Asuran: you can go to terminal and file a bug `ubuntu-bug wavemon`, you know.
[16:19] <Asuran> wxl: didnt knew nice
[16:19] <Asuran> but i doubt its useful making such a ticket
[16:19] <Asuran> cuz they will ask whats the problem
[16:19] <wxl> well this discussion certainly isn't any more useful XD
[16:19] <Asuran> and i dont got it cuz in main channel no one could help me further than this
[16:19] <wxl> but that will collect information from your system that could help diagnose the problem
[16:19] <Asuran> and if devs are no willing todo its ok for me no problem
[16:19] <Asuran> before i get banned from here i better be quiet
[16:20] <wxl> no bug report means nothing's going to happen on ANY OPEN SOURCE PROJECT
[16:20] <rbasak> Ubuntu developers usually prioritise bugs that affect many Ubuntu users. Unfortunately we don't have time to fix every bug.
[16:20] <rbasak> But it doesn't even sound like you have a valid bug reoprt.
[16:20] <rbasak> You really want the wider set of Ubuntu community users who might be able to help.
[16:20] <rbasak> I suggest you follow the link I pasted.
[16:21] <nacc> Asuran: i think you are confusing "I didn't get help right now this exact second in #ubuntu" with "I didn't get help"
[16:21] <Asuran> its okay guys let this bug be then there
[16:21] <nacc> Asuran: that is *your* choice, not ours.
[16:21] <Asuran> i dont want to continue this sorry for breaking the rules


[04:54] <mitya57> darkxst: No, I didn't. Maybe will do later today.
[06:50] <darkxst> mitya57, ok, thanks
[13:21] <mitya57> darkxst: uploaded to utopic and trusty
[16:57] <mlankhorst> does the unity7 greeter set the display or not?
[17:01] <mlankhorst> through randr, initially


[08:18] <dholbach> good morning
[08:22] <Kilos> morning dholbach
[08:22] <dholbach> hi Kilos
[08:22] <Kilos> and dpm
[08:28] <dpm> o/
[18:01] <dholbach> hey... could somebody of you imagine joining the Ubuntu membership board?
[18:02] <Kilos> i have applied i think dholbach
[18:02] <wxl> me too
[18:02]  * dholbach hugs Kilos and wxl
[18:02] <dholbach> that's brilliant
[18:02]  * genii makes more coffee
[18:02] <wxl> ☺
[18:02] <dholbach> anyone else?
[18:02] <dholbach> I mean most of you all became Ubuntu members already - we're still looking for somebody to join the team
[18:02] <Kilos> belkinsa  can you fill us in please
[18:03] <dholbach> I used to do it, when the CC was still approving membership
[18:03] <dholbach> and it's actually a lot of fun
[18:03] <dholbach> because you get to know many people from many different parts of the Ubuntu community
[18:03] <Kilos> thats part of the reason i applied dholbach
[18:04] <genii> Is there not enough sitting members on the membership board currently to be effective?
[18:04] <dholbach> Kilos, nice one!
[18:04] <Kilos> im sure there are 7 applications there
[18:04] <dholbach> genii, the nomination period is just right now
[18:04] <wxl> i applied because i saw a need and felt i could contribute without necessarily detracting from my other roles
[18:04] <Kilos> 2 new and 5 older ones
[18:04] <genii> Hm
[18:04] <wxl> meaning i felt i had the necessary skills
[18:04] <dholbach> genii, if you want, you can have a chat with somebody like belkinsa to see how much work it is and if you have other questions
[18:05] <wxl> unfortunately, leadership/management is not easy for everyone
[18:05] <Kilos> only i havent been a member very long
[18:05] <dholbach> if you were approved for membership and have been around for a while and are generally curious, it's a good spot to be in :)
[18:05] <wxl> Kilos: honestly, i don't think that matters. it wouldn't to me if it were my decision.
[18:05] <Kilos> ah well lets hope wxl
[18:06] <wxl> like for example, i have a member on our bug triage team who's a new member and doing so darn good i'm trying to facilitate him to join bug control
[18:06] <wxl> the fact that he's new doesn't matter
[18:06] <wxl> it's his skills, ability, and drive that matters
[18:07] <Kilos> ya but i have no skills man only applied for starters because pleia2  had to extend by 2 weeks
[18:07] <wxl> i have a strong suspicion that your desire to try indicates you're not scared of leadership]
[18:07] <belkinsa> You don't need that many skills, only reporting and knowing what the board is looking for,
[18:07] <wxl> that's a good start :)
[18:07] <wxl> brb
[18:07] <belkinsa> https://wiki.ubuntu.com/Membership/Boards
[18:09] <Kilos> belkinsa  i dont see me anywhere or wxl
[18:10] <Kilos> lol maybe im doing some thing wrong
[18:10] <belkinsa> Kilos, it's done via mailing-list only members of the board can see it
[18:10] <belkinsa> And the CC too.
[18:10] <Kilos> oh ok ty
[18:14] <genii> belkinsa: How much time do you figure you spend per month on Membership duties?
[18:15] <belkinsa> 10 minutes to an hour, depends on how many are applying for which board.
[18:15] <belkinsa> And the reporting and wiki editing takes only a few minutes.
[18:15] <Kilos> is that all?
[18:16] <belkinsa> But only one person does the reporting and editting
[18:16] <belkinsa> Kilos, yup, but lately we haven't received that many applicants.  Only zero to two at a meeting.
[18:16] <Kilos> whew
[18:17] <belkinsa> I think when I applied,  there was like five of us and it took the whole hour.
[18:17] <Kilos> well im here. will  stay up late for the late meets. its only once a month and ill be here for the early meets
[18:18] <Kilos> lol they just mustnt ask me a whole bunch of funny questions
[18:18] <belkinsa> Who is they?  The CC?
[18:18] <Kilos> who evr approves the board
[18:19] <Kilos> ever
[18:20] <Kilos> are the board applications the same as for membership application?
[18:20] <belkinsa> No, the Community Council does.
[18:21] <Kilos> oh so we dont have to attend a meeting for it
[18:21] <belkinsa> pleia2, czajkowski, and dholbach are apart of the CC
[18:21] <belkinsa> Kilos, correct.
[18:22] <Kilos> oh thats cool then i was getting tense already, was a big move for me to apply for membeship
[18:22] <Kilos> kinda nerve wracking
[18:22] <Kilos> hehe
[18:22] <belkinsa> I had that same feeling
[18:22] <Kilos> lol
[18:23] <pleia2> Kilos: it was worse when mark shuttleworth was on the approval board, I was freaking out
[18:23] <pleia2> hehe
[18:23] <Kilos> hahaha
[18:23] <mhall119> I didn't have mark on the board, but I was still freaking out
[18:24] <Kilos> if any of you see peeps from africa visit here for help please point them to #ubuntu-africa
[18:24] <Kilos> yeah its a big thing to be an ubuntu member imo
[18:24] <belkinsa> Sure thing.
[18:26] <Kilos> but i am very happy i applied and was so well supported by our team
[21:16] <Kilos> night all


[00:19] <Sarvatt> cnd: also you'll need to no change rebuild your video driver, xorg-edgers has newer versions than in the xorg-testing one
[00:40] <m3ga> i have an un-recognised usb device that according to lsusb -v is a mouse. how do i get X to use it?
[00:42] <RAOF> You need to get the kernel to present it as an input device; once that's happened, the evdev X driver will pick it up.
[00:46] <m3ga> there's not shortcut for testing? its a touchscreen device btw
[00:48] <RAOF> I _think_ you'll need to get the kernel to recognise it before anything interesting will happen.
[01:53] <m3ga> RAOF: Xorg.0.log is here http://pastebin.org/336855 . avago mouse is detected, but i get not pointer on screen and no mouse like behaviour when i touch the screen (this is a touchscreen device)
[02:01] <RAOF> Hm.  That looks like it's getting picked up by X correctly.  I'm not sure what the problem is - I've not got much experience with touchscreens.
[02:02] <m3ga> most touchscreens don't pretend to be a mouse device.
[02:06] <RAOF> I'm not sure how true that is; from what I can remember, bryceh's touchscreen used kernel uinput + the evdev driver.
[03:55] <ScottK> It looks to me like GL headers moved from /usr/include/GL to /usr/include/ (e.g. /usr/include/GL/gl.h is now found in /usr/include/gl.h)
[03:55] <ScottK> Was that on purpose?
[03:57] <RAOF> ScottK: Not on purpose, and fixed in 7.8.1-3ubuntu2
[03:57] <ScottK> RAOF: Thanks.
[03:58] <ScottK> I'll update and try again.
[04:00] <ScottK> RAOF: Thanks again.  Updating solved the problem.  Way easier than hand editing includes in libqt4-opengl-dev to make a test build work.
[05:40] <Sarvatt> jcristau: any reason we dont enable composite support in xdpyinfo? just needs a libxcomposite-dev build dep to enable it
[05:44] <Sarvatt> menus dont work in any of the x apps :(
[09:34] <jcristau> Sarvatt: go ahead and add it
[11:05] <Sarvatt> dang, digging through the chrome source leads to some interesting finds, they have a glx and gles rendering backends in the works and a ton of switches http://src.chromium.org/svn/trunk/src/chrome/common/chrome_switches.cc
[11:05] <Sarvatt> --enable-accelerated-compositing looks interesting :)
[11:06] <RAOF> gles?  Not openvg?
[11:37] <tseliot> Sarvatt: what's missing in the nvidia package in x-updates?
[12:07] <Sarvatt> tseliot: nvidia_supported doesn't work anymore so i hardcoded the modaliases from the last one that worked, the headers all go in /usr/include/nvida-current/whatever so nothing can find them, and the 32 bit compat install is installing all libs instead of just specific ones
[12:09] <Sarvatt>  dh_install -p$(PKG_driver)  "$(dirname_x86)/*.so*"  "$(PKG_libdir32)" is wrong in it, all .so's are in $(dirname_x86) toplevel now
[12:11] <Sarvatt> it's probably installing links it doesn't need to too
[12:15] <tseliot> Sarvatt: as regards the headers, we cannot let each nvidia driver install the same headers in the same place
[12:15] <Sarvatt> can't just make the directory an alternative either, ah well
[12:16] <tseliot> right
[12:16] <Sarvatt> by can't I mean please please please please please don't of course :)
[12:16] <tseliot> things such as openCL headers should be packaged separately
[12:16] <tseliot> as they're not specific to nvidia
[12:17] <Sarvatt> i think you're the only one that can follow the nvidia packaging these days :)
[12:18] <tseliot> heh
[12:18] <tseliot> unfortunately ;)
[12:18] <Sarvatt> i get so lost keeping track which of the 50+ variables in the rules to use in all of the .in's
[12:19] <tseliot> those variables make sure that we don't have to update each file manually but of course you have to see what they stand for
[12:20] <tseliot> the work that you did on the package was a big help, I hope to complete it soon
[12:23] <Sarvatt> what do you think about moving libGL back to /usr/lib? I have nvidia-current, nvidia-173 and mesa all in there with the libGL.so.1 symlink the only thing conflicting. can we just have every package providing it set up an alternative with different priorities?
[12:25] <Sarvatt> just trying to figure out how to get rid of some of the complexity in the packaging, and drivers direct from the manufacturers would work again :)
[12:25] <tseliot> yes, that would be fine. libGL.so.1 can be made a slave link of the alternative, I guess
[12:26] <tseliot> well, "work again" after some effort would be more realistic ;)
[12:27] <Sarvatt> oh, forgot to ask, but this is bogus isnt it? - update-alternatives --remove gl_conf /usr/lib/GL/ld.so.conf
[12:27] <Sarvatt> it's in the mesa prerm's
[12:27] <Sarvatt> there's no /usr/lib/GL
[12:28] <Sarvatt> http://git.debian.org/?p=pkg-xorg/lib/mesa.git;a=blob;f=debian/libgl1-mesa-swx11.prerm;h=36830024245fe6255621ed9be2099f57f01b6b82;hb=refs/heads/ubuntu
[12:29] <tseliot> no, it's not bogus, it simply tells it to remove the alternative
[12:29] <tseliot> I think that should be /usr/lib/mesa/ld.so.conf though
[12:29] <tseliot> I'll check that later
[12:30] <Sarvatt> yeah thats why I was confused
[12:30]  * tseliot -> lunch
[12:30] <Sarvatt> i think we used /usr/lib/GL when you first started doing it
[12:30] <tseliot> that's likely
[12:30] <tseliot> bbl
[12:30] <Sarvatt> see ya
[12:40] <Kangarooo> Sarvatt: ive put more xcrashes :) https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/587710
[12:40] <Kangarooo> theres 2 post now with them maybe somwthing new comes up
[13:32] <Sarvatt> darn, sysprof swears every debug file has a wrong crc, and the 8 I've checked so far are all fine
[18:05] <Sarvatt> anyone using an up to date edgers that has chromium or chrome installed?
[18:07] <Sarvatt> i just want to know if opening like 20 or so tabs makes them disappear
[19:17] <Kangarooo> Sarvatt: will x4500 hdtv interl work on ubuntu?
[19:17] <Kangarooo>  intel
[19:26] <Sarvatt> yep it will
[19:26] <Sarvatt> (famous last words)
[19:26] <Sarvatt> wow freetype's build system is crazy
[19:29] <Kangarooo> Sarvatt: did u checked https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/587710 ? i have there added 2 times 5 crashes total 10 and nothing new in ppa. im now looking for new comp. sad that i need to also check if drivers will work since something not right with even more videos since i understand they are beeing removed.. ?
[20:04] <Sarvatt> your system is just plain messed up Kangarooo, both nvidia and nouveau are crashing the same way
[22:39] <Sarvatt> argh, darn docbook/sgml stuff!
[22:39] <Sarvatt> docbook-to-man /opt/source/freetype-2.3.12/debian/freetype-config.man.sgml > /opt/source/freetype-2.3.12/debian/freetype-config.man
[22:39] <Sarvatt> /usr/bin/nsgmls:/usr/share/sgml/docbook/dtd/4.1/dbcent.mod:53:65:W: cannot generate system identifier for public text "ISO 8879:1986//ENTITIES Added Math Symbols: Arrow Relations//EN"
[22:39]  * Sarvatt has no idea how to fix that, i have it as far back as 4.2 but no 4.1
[22:41] <Sarvatt> it's cursing me, couldn't get xorg-docs building a few days ago either :)
[23:14] <Ng> Sarvatt: istr you asked me if I still see the flickering on intel - yes, it was happening earlier


[04:51] <pitti> Good morning
[07:52] <dholbach> good morning
[08:16] <mlankhorst> morning
[08:51] <Tribaal> hi all. Quick question -sorry if it's the wrong place to ask, but how can I add my "pin" to the ubuntu memebers map shown on https://wiki.ubuntu.com/Membership (I'm a recent Ubuntu member)
[08:51] <ogra_> urgh, what added all the GL deps to the touch image ??
[08:52] <darkxst> Tribaal, many ubuntu members seem to live in the ocean according to that map!
[08:53] <Tribaal> darkxst: yes, yes, privacy, I know. But I'd like to add mine nonetheless :)
[08:53] <Tribaal> darkxst: I'm one of the very few Ubuntu members living in Africa - I might as well send the message that we're around :)
[08:55] <darkxst> Tribaal, there may be better ways to do that than a broken map ;)
[08:56] <TJ-> Is there a way to force apt to ignore Conflicts|Replaces in order to keep 2 packages installed simultaneously?
[08:58] <darkxst> TJ Conflicts are not arbitrary, they are there for a reason
[09:00] <TJ-> darkxst: I know; and in my case the reason is in the way of work. Currently I use a script to manually fix-up the package lists and dpkg status, but I'd rather do it through an apt configuration option
[09:01] <darkxst> TJ-, if you want help breaking your system, there are probably better channels than this!
[09:02] <darkxst> TJ-, this channel is really for ubuntu development
[09:02] <ogra_> Laney, can we drop the x86 build deps on armhf for https://launchpad.net/ubuntu/+source/gst-plugins-bad1.0/1.4.0-1ubuntu1 ? ... it results in http://people.canonical.com/~ogra/touch-image-stats/208.changes
[09:03] <ogra_> Laney, referring to "- Build-depend on libgl1-mesa-dev and libglu1-mesa-dev."
[09:03] <TJ-> darkxst: Which is what I am doing
[09:04] <ogra_> seb128, is Laney at debconf this week ?
[09:04] <seb128> ogra_, yes
[09:04] <darkxst> TJ-, ignoring conflicts is a bad idea!
[09:04] <ogra_> damned
[09:04] <ogra_> k, thanks
[09:04] <seb128> yw!
[09:05] <TJ-> darkxst: Having the option to do so is a good idea. I hoped there'd be  a pre-existing configuration item that is hidden away, but if not, I'll patch apt to have one
[09:06] <darkxst> TJ-, sure go ahead, but you are playing with fire!
[09:10] <TJ-> darkxst: Fire is fine, I know what I'm doing, I just want to avoid having to run a hook-script. My case is developing GRUB, and needing grub-pc and grub-efi installed alongside each other
[10:51] <Mirv> if a core-dev _or_ MOTU (in this case) would be available for reviewing/acking packaging changes for a CI Train upload, please see https://ci-train.ubuntu.com/job/ubuntu-landing-012-2-publish/14/
[10:52] <Mirv> ok sil2100 is back so he'll check that out
[10:54]  * sil2100 is in meeting spree
[10:54] <sil2100> But yeah, I have a moment now :)
[13:35] <sergiusens> pitti: any idea how to solve this? http://paste.ubuntu.com/8149970/
[13:35] <sergiusens> it's a chroot
[13:36] <ogra_> do we now always need policy-rc.d mangling ?
[13:40] <jamin> has anyone successfully used the text based oem-config in 14.04?
[13:41] <ogra_> probably someone in #ubuntu-server
[13:41] <ogra_> (sounds more like the place where you would use it)
[13:42] <jamin> https://bugs.launchpad.net/ubuntu/+source/oem-config/+bug/1361595
[13:42] <jamin> I don't think it's possible
[13:44] <pitti> sergiusens: yes, it's bug 1320534
[13:44] <pitti> sergiusens: I did the merge with Debian a month or so ago, but it's blocked on reviewing
[13:45] <pitti> sergiusens: I guess I could try and upload that in isolation though
[13:45] <pitti> I already cherry-picked some other bug fixes this morning
[13:47] <pitti> sergiusens: the update-rc.d warning should be fixed with this morning's sysvinit, I suppose you didn't get that yet?
[13:47] <ogra_> we didnt have an image build yet
[13:47] <ogra_> (so he wont)
[13:48] <pitti> oh, I thought that was from some local/recent deboostrap run
[13:48] <pitti> err, apt-get install, I mean
[13:48] <pitti> (see first line)
[13:48] <pitti> probably missing a dist-upgrade in his schroot
[13:48] <ogra_> ah, right
[13:49] <ogra_> (sorry, didnt mean to rip that out of context)
[13:50] <sergiusens> pitti: yeah
[13:50] <sergiusens> pitti: wrt ogra_'s comment, it's related to not being able to dpkg -i from a chroot in our recovery image
[14:25] <Riddell> seb128: do we have the Adwaita gtk theme in utopic?
[14:27] <seb128> Riddell, it's default since GNOME3, so we have it since precise or something
[14:28] <seb128> not sure to understand the question
[14:28] <Riddell> seb128: hmm I'm still seeing the ugly default theme for evince and the gtk-selector in kde doesn't list adwaita
[14:30] <seb128> Riddell, do you have gnome-themes-standard installed?
[14:31]  * Riddell installs
[14:33] <Riddell> seb128: ah yes that does it, thanks
[14:33] <seb128> Riddell, yw
[14:44] <pitti> sergiusens: I couldn't reproduce it with my schroots, but xnox got it somehow; where did you see that exactly?
[14:44] <pitti> sergiusens: reproduction steps would be appreciated in that bug, so I could verify the fix
[14:46] <sergiusens> pitti: ah, it's a complicated chroot created with crouton for the chromebook
[14:46] <sergiusens> it's my armhf builder
[14:47] <pitti> sergiusens: if you have an easy way to check, could you upgrade to the binaries in http://people.canonical.com/~pitti/tmp/sysvinit-merge/ ?
[14:47] <pitti> sergiusens: it has amd64 and armhf
[14:47] <sergiusens> pitti: yeah, I can check
[14:53] <sergiusens> pitti: it gets a bit further, no it doesn't start with invoke.rc.d: initscript ssh, action "start" failed
[14:54] <sergiusens> pitti: ah, it's the same error
[14:56] <sergiusens> pitti: this is crouton btw https://github.com/dnschneid/crouton
[14:56] <pitti> sergiusens: ah, no idea about /var/run/utmp; that might just not work in a chroot; the bug above is about a missing /run/shm/
[14:56] <sergiusens> pitti: yeah, I manually created the dir and the complaints ended for utmp
[14:57] <pitti> -rw-rw-r-- 1 root utmp 0 May  7  2013 /run/utmp
[14:57] <pitti> sergiusens: I have that in my sid chroot
[14:57] <pitti> sergiusens: and /var/run is a symlink to /run
[14:57] <pitti> same in utopic
[14:59] <pitti> sergiusens: so mabe your case isn't about /run/shm/ at all then, and xnox' situation was different
[14:59] <sergiusens> so it's not that bug :-)
[15:00] <pitti> sergiusens: for building a chroot you probably want a policy-rc.d?
[15:00] <sergiusens> pitti: I don't know how that chroot is built; I just use it; but if you say so, I'll look into it
[15:01] <pitti> sergiusens: which of the two is missing OOI, /var/run symlink, or /run/utmp ?
[15:03] <sergiusens> pitti: /var/run is not a symlink here
[15:03] <sergiusens> that may be it
[15:03] <sergiusens> nah, ls'ed wrong; it's a link to /run
[15:04] <sergiusens> pitti: /run/utmp is missing though
[15:04] <pitti> sergiusens: not sure what creates that; perhaps debootstrap itself
[15:04] <pitti> ah no, apparenlty base-files:
[15:05] <pitti> base-files.postinst:  if [ ! -f /var/run/utmp ]; then
[15:05] <pitti> base-files.postinst:    echo -n>/var/run/utmp
[15:05] <pitti> so perhaps that didn't get configured properly in your schroot?
[15:05]  * pitti -> bbiab
[15:46] <caribou> Is it acceptable to have two names listed in the Maintainer field of a package ?
[15:46] <pitti> caribou: yes, with comma separation as usual
[15:46] <pitti> caribou: ah sorry, no
[15:47] <pitti> caribou: that'd be Uploaders:
[15:47] <pitti> caribou: not that it matters at all in Ubuntu; ubuntu specific packages should usually be owned by Ubuntu Developers<EMAIL_ADDRESS>[15:50] <caribou> pitti: thanks, that's for a Debian package
[15:50] <pitti> caribou: so put the primary dev or a team (pkg-*@alioth ML or so) into Maintainer:, and the others into Uploaders:
[15:51] <caribou> pitti: good idea, thanks for the quick answer
[16:07] <tedg> stgraber, talking to hallyn he thought that you had the race nailed down.
[16:11] <stgraber> tedg: oh right, sorry, blurry memory and all. So I think we figured that the race was lightdm spawning the user session before cgmanager was actually started.
[16:12] <stgraber> tedg: in a perfect world we'd be able to get systemd-shim to depend on cgmanager but since that one is dbus activated, that's not quite possible
[16:12] <stgraber> tedg: so an ugly way to avoid the race would be to override the dbus start condition to be whatever start condition it currently has + cgmanager-ready
[16:14] <tedg> stgraber, Does it make sense to start lightdm before cgmanager in general? Or it just works because we're not using cgroups in any system jobs?
[16:14] <pitti> stgraber, hallyn: could we alternatively make cgmanager dbus activatable?
[16:14] <hallyn> tedg: the problem is that not everyone running lightdm will have cgmanager installed
[16:14] <stgraber> pitti: no we can't
[16:14] <stgraber> pitti: cgmanager doesn't listen on the system bus
[16:15] <pitti> ah right, ignore me :)
[16:15] <tedg> hallyn, cgmanager could be start on starting dbus ?
[16:15] <hallyn> dbus isn't always installed
[16:15] <tedg> "That's crazy!" says the client guy
[16:16] <stgraber> tedg: jodh suggested that but that's plain wrong since cgmanager doesn't need the dbus daemon :)
[16:16] <hallyn> cgmanager does start as early as possible 9afaik)
[16:17] <tedg> stgraber, Well, it doesn't need it, but it should start before it.
[16:17] <stgraber> tedg: sure, but there's no way to describe "if service X is around, then wait for it" in upstart jobs :)
[16:17] <hallyn> i suppose we could have a essentials upstart job that emits "cgmanager-not-needed", which gets overridden by cgmangaer
[16:18] <stgraber> otherwise the right thing to do would be to have dbus.conf wait until cgmanager is ready if cgmanager is installed
[16:18] <stgraber> hallyn: that seems rather ugly :)
[16:18] <hallyn> i thought it elegant :)
[16:19] <stgraber> if we want a blocking behavior (and we said that maybe we don't want that to avoid hanging the whole system when something goes wrong), systemd-shim ought to be the one blocking requests until the cgmanager socket is available
[16:19] <tedg> I guess I'm kinda surprised that cgmanager startup is the problem. *a lot* has to start before we run applications, do we know why cgmanager is taking so long?
[16:21] <hallyn> tedg: oh, it's bc yo uneed the cgproxy i think
[16:21] <hallyn> if yo uhad a newer kernel yo uwouldn't have this issue
[16:21] <hallyn> so you run cgproxy, start cgmanager, then run a new cgproxy that talks dbus to cgmanager. then you're finally ready
[16:22] <tedg> Can we make the session upstart startup block on cgmanager being ready?
[16:23] <tedg> I think we get an event for that no?
[16:23] <stgraber> no
[16:23] <stgraber> you need to block before you switch to the phablet user
[16:23] <stgraber> cgmanager needs to be started before logind sets up your user session
[16:23] <tedg> Oh
[16:26] <tedg> How about having systemd-login dbus activate a shell script that blocks until cgmanager is ready?
[16:27] <stgraber> if we are going in that direction, I'd rather we just make systemd-shim itself wait for cgmanager, no point in using a wrapper when we can have the real thing do it properly
[16:28] <stgraber> the obvious problem with that and the reason why it wasn't done that way to begin with is that if cgmanager fails to start, then you won't be able to login
[16:30] <hallyn> well it could have a sane timeout, 10s
[16:30] <hallyn> and a config file to override
[16:31] <popey> Why is mencoder not in utopic? http://packages.ubuntu.com/search?keywords=mencoder
[16:32] <ogra_> popey, probably fallout of the libav transition
[16:32] <popey> oh ugh
[16:33] <ogra_> (just guessing)
[16:33] <tedg> stgraber, So that works for me, is that something you're going to work on a patch for?
[16:34] <LocutusOfBorg1> sil2100, please remove lucene++ from mentors
[16:34] <LocutusOfBorg1> :)
[16:34] <LocutusOfBorg1> it has been uploaded
[16:34] <stgraber> tedg: I haven't done any work on systemd-shim, so that's more a pitti or hallyn question
[16:35] <hallyn> really a q for desrt|pdx - if he's ok with it
[16:35] <pitti> tedg, hallyn, stgraber: what's so wrong about having lightdm start ".. and started cgmanager"?
[16:35] <pitti> under upstart we always need it now anyway, and under systemd the upstart job won't be used
[16:36] <hallyn> on the phablet, probably nothing
[16:43] <tedg> hallyn, Are you suggesting an override on the phablet then?
[16:43] <hallyn> tedg: i was, but maybe pitt's right and we can just do it everywhere
[16:44] <tedg> We'd then need to add a dependency in the binary package, no?
[16:44] <ogra_> tedg, how much boot time will that cost us ?
[16:45] <tedg> ogra_, Not sure, perhaps hallyn knows. It should be the same amount of tasks, just change ordering slightly.
[16:45] <tedg> Depends if it creates a bubble in the boot chart.
[16:45] <ogra_> it does today
[16:45] <tedg> What does? CGManager?
[16:46] <ogra_> (well, i didnt do charts for a while, but cgmanager definitely has its own PID and shows up)
[16:46] <ogra_> everything with a PID has a bootchart entry
[16:46] <tedg> Sure, I'm more saying if it blocks things so that CPU/IO isn't used. Overall we should use the same amount of CPU/IO, just ordering could change.
[16:46] <ogra_> ok
[16:47] <pitti> ogra_, tedg: well, considering that lightdm starting before cgmanager is currently broken, and it just happens to work most of the time, it hardly is a boot time problem at all?
[16:47] <tedg> Honestly, from the UTAH testing it gets the right order 95% of the time anyway :-)
[16:48] <ogra_> tedg, the utah bootchart testing is totally wrong and broken
[16:48] <ogra_> better use phablet-bootchart locally
[16:48] <ogra_> (they test on a device that has a ton of test stuff installed before creating the chart)
[16:48] <tedg> ogra_, I mean the autopilot testing, where we start to see failures when turning on cgroups.
[16:48] <ogra_> ah
[16:49] <ogra_> pitti, how does that breakage manifest ?
[16:49] <tedg> ogra_, Intermittent failures of application startup. They can't create the Upstart jobs for the apps.
[16:49] <ogra_> lightdm depends on the container being started
[16:49] <ogra_> and the container depends on cgmanager being started
[16:49] <sil2100> LocutusOfBorg1: \o/ Thanks!
[16:49] <pitti> I don't know, I haven't seen it myself; I was just catching on to the discussion here that lightdm needs cgmanager so that it can create cgroups for the user sessions (and its own session)
[16:50] <ogra_> right, but so does lxc
[16:50] <sil2100> LocutusOfBorg1: I'm somehow sooo busy recently that I need to find a free time jiffy to do that
[16:50] <ogra_> and lxc comes far before lightdm in the boot process
[16:51] <tedg> Hmm, that's interesting. Wonder how cgmanager isn't started.
[16:51] <ogra_> does cgmanager have semi-ready states it announces via upstart or some such ?
[16:51] <tedg> Perhaps then it's the cgproxy stuff that's confusing Upstart?
[16:52] <ogra_> hmm, could be
[16:52] <hallyn> yes both will send the cgmanage-rready event
[16:52] <tedg> hallyn, But it seems that cgproxy sends it in pre-start instead of post-start?
[16:52] <tedg> Oh, wait, both.
[16:53] <hallyn> yeah, the cgproxy one isn't right
[16:53] <hallyn> i forget, who wrote that bit?
[16:53] <ogra_> so you would actually have to wait for cgproxy, not cgmanager
[16:53] <tedg> Heh, it seems like you should tell Upstart that you exist before everything is signaled ready.
[16:54] <tedg> ogra_, Seems we should be waiting on cgmanager-ready
[16:54] <ogra_> well, which is essentially the same, but yeah :)
[16:54] <hallyn> ogra_: right, cgmanager upstart job shoul dkeep state to know that it started cgproxy and then not send the ready signal
[16:54] <hallyn> i think jodh wrote those bits, hm
[16:55] <tedg> ogra_, the lxc-android-config job is waiting on that event.
[16:55] <ogra_> phablet@ubuntu-phablet:~$ grep cgmanager /etc/init/lxc-android-config.conf
[16:55] <ogra_> start on cgmanager-ready
[16:55] <ogra_> phablet@ubuntu-phablet:~$ grep android /etc/init/lightdm.override
[16:55] <ogra_>            and android)
[16:55] <ogra_> phablet@ubuntu-phablet:~$
[16:56] <ogra_> tedg, right and lightdm is waiting for the android event thats fired after the container is 100% up
[16:56] <hallyn> so who knows where an upstart job could keep that state?  use /var/run?
[16:56] <hallyn> hm, so you're saying this race isn't really possible bc the container wouldn't start?
[16:56] <ogra_> tedg, so you should actually already have a big delay between your session and cgmanager
[16:56] <ogra_> right
[16:57] <tedg> Hmm, stgraber how were you guys seeing the race?
[16:57] <ogra_> container wiats for cgmanager-ready and then emits android once the container is ready
[16:57] <ogra_> and lightdm starts on android
[16:58] <stgraber> tedg: I never saw the race, we did the debugging solely based on feedback from jodh
[16:59] <hallyn> it's still possible,
[17:01] <tedg> stgraber, Do you know what behavior he was looking for to conclude that?
[17:02] <stgraber> tedg: he made cgmanager start on dbus and that solved it for him which suggested some race between something dbus related and cgmanager, with the obvious candidate being shim+logind
[17:05] <tedg> So could logind be started before cgmanager-ready by something else?
[17:06] <tedg> Would it handle cgmanager starting after it already started?
[17:08] <ogra_> Laney, poke
[17:10] <pitti> stgraber, tedg: oh, indeed -- appending "or starting dbus" sounds like a nice (and mostly correct) way for cgmanager.conf's start condition, and doesn't introduce new dependencies
[17:11] <Laney> hi ogra, will look later on
[17:11] <pitti> and will sort itself before dbus
[17:11]  * ogra_ hugs Laney
[17:11] <tedg> pitti, Apparent hallyn was saying that there are systems with cgmanager but not dbus.
[17:11] <ogra_> Laney, thanks, just wanted to make sure the ping didnt get lost :)
[17:11] <pitti> tedg: that's totally fine -- it's an "or" condition
[17:11] <Laney> nope
[17:11] <pitti> tedg: that more or less just says "if dbus is there, start it after cgmanager"
[17:12] <hallyn> right now cgmanager starts on mounted /sys/fs/cgroup or virtual-filesystems
[17:12] <hallyn> that really should beat dbus
[17:13] <hallyn> unless mounted /sys/fs/cgroup never happens bc it's mounted in initramfs?
[17:13] <hallyn> so yeah that sounds fine
[17:13] <pitti> start on local-filesystems
[17:13] <ogra_> <ou would notice that on the phone ...
[17:13] <pitti> that's dbus, so also very early on
[17:13] <ogra_> the container fully depends on cgmanager-ready
[17:13] <pitti> local-filessystems is almost always satisfied right after initramfs, if you don't have any extra /usr or similar mounts
[17:13] <ogra_> without container, no graphics ...
[17:14] <ogra_> (or lightdm ... or session)
[17:16] <tedg> K, so hallyn is that a patch you can make/upload?
[17:17] <hallyn> tedg: stgraber: pitti:  http://paste.ubuntu.com/8151670/ ook ok?
[17:18] <hallyn> oh is there a bug# for this?
[17:19] <hallyn> i'll use 1357252
[17:19] <pitti> hallyn: LGTM (but please give it a boot test; I'm not exactly an upstart expert)
[17:19] <tedg> hallyn, +1, yeah bug 1357252
[17:20] <pitti> right, I think that's the one jodh pointed me to
[17:21] <hallyn> (building )
[17:21] <pitti> hallyn: applied that here, rebooting
[17:22] <hallyn> shared-mime-info triggers be slow
[17:22] <cjwatson> TJ-: There's no good reason to install grub-pc and grub-efi alongside each other (speaking as a GRUB developer).  The *-bin packages exist so that you can coinstall them and use grub-mkimage etc.  The only purpose of the -bin-less names is to own the system's boot process, and only one package should do that.
[17:23] <pitti> hallyn: seems happy enough here (amd64 utopic desktop du jour)
[17:23] <TJ-> cjwatson: So I can remove the non-bin packages without any undo regressions?
[17:24] <cjwatson> TJ-: I expect you'll want to keep the one you're actually using to boot
[17:24] <cjwatson> TJ-: But assuming you mean "undue", then yes.  I only have one of those installed.
[17:24] <TJ-> cjwatson: Using both, that's why I've been using a script to alter the package lists
[17:24] <cjwatson> But I have both grub-efi-amd64-bin and grub-pc-bin.
[17:25] <cjwatson> How can you possibly be using both to boot?
[17:25] <cjwatson> I mean, routinely.
[17:25] <hallyn> pitti: same here, so pushing
[17:25] <TJ-> cjwatson: Portable disk; able to boot on either type of firmware
[17:25] <hallyn> (will have to push to upstream and debian later)
[17:25] <pitti> hallyn: thanks
[17:25] <cjwatson> TJ-: You can always arrange to manually run grub-install with whatever special options you need after upgrades.
[17:25] <tedg> Thanks hallyn!
[17:25] <cjwatson> TJ-: That will be MUCH easier than messing about with editing package lists.
[17:26] <hallyn> np, let's hope this actually sorts out the evice
[17:26] <cjwatson> TJ-: And that's basically all that the surplus non-bin package will be doing for you.
[17:26] <hallyn> device
[17:26] <TJ-> cjwatson: Yeah, I was looking at an additional script in /etc/kernel/postinst.d/
[17:27] <TJ-> cjwatson: Although I've had an enjoyable day learning the internals of apt :)
[17:27] <flexiondotorg> cjwatson, You might remember that I am working on Ubuntu MATE.
[17:28] <flexiondotorg> cjwatson, How do I coerce Ubiquity to use Marco as the window manager and the themes I've created for Ubuntu MATE?
[17:29] <flexiondotorg> cjwatson, Thanks to you and xnox I submitted merge proposals for adding Marco support to Ubiquity.
[17:29] <flexiondotorg> cjwatson, Which have been accepted and merged for some time now.
[17:30] <flexiondotorg> cjwatson, I have settings packages that make the appropriate gschema overrides.
[17:32] <cjwatson> flexiondotorg: I expect that just needs work in ubiquity-dm.  No idea otherwise.
[17:32] <cjwatson> flexiondotorg: Maybe also in the upstart job file.
[17:34] <flexiondotorg> cjwatson, I added support to ubiquity-dm. Also merged.
[17:35] <flexiondotorg> cjwatson, Upstart job?
[17:35] <cjwatson> flexiondotorg: debian/*.upstart, wherever it is.  (I'm at a conference right now.)
[17:35] <flexiondotorg> cjwatson, Thanks. That is enough of a pointer.
[17:35] <cjwatson> Probably debian/ubiquity.ubiquity.upstart.
[17:36] <cjwatson> But that only really specifies the DM.
[17:36] <cjwatson> So shouldn't matter here.
[17:37] <cjwatson> flexiondotorg: What's actually going wrong?
[17:37] <flexiondotorg> cjwatson, If I select "Try Ubuntu", nothing. Everything is fine.
[17:38] <flexiondotorg> cjwatson, If I select "Install Ubuntu", then the default them in Ambiance not the themes I've configured using gschema overrides.
[17:38] <flexiondotorg> cjwatson, Also the live sessions always drags in Metacity which should be required since Marco is now a suitable depend.
[17:38] <cjwatson> flexiondotorg: I guess that means your overrides are wrong somehow, but I'm afraid I really don't know much about that.
[17:39] <flexiondotorg> cjwatson, No. The overrides are correct. Sorry to be blunt. I've override mate and gnome.
[17:39] <cjwatson> flexiondotorg: Do you mean that the live *image* has metacity when it shouldn't?
[17:39] <flexiondotorg> cjwatson, Yes.
[17:39] <cjwatson> flexiondotorg: The overrides are your responsibility to debug, I'm afraid.  I'm sorry I can't help.
[17:39] <cjwatson> flexiondotorg: For the presence of metacity, you probably just need to seed marco.
[17:40] <flexiondotorg> cjwatson, Also be aware Ubuntu is not being built on Canonical infrastructure right now.
[17:40] <flexiondotorg> s/Ubuntu/Ubuntu MATE/
[17:40] <cjwatson> flexiondotorg: I'm well aware, since if it were then I would have set it up.
[17:41] <flexiondotorg> cjwatson, Come the day I can help setup Ubuntu MATE if you'd like via merge porposals.
[17:41] <flexiondotorg> cjwatson, I am seeding Marco.
[17:41] <cjwatson> flexiondotorg: Where is your image build log?
[17:41] <cjwatson> You're obviously not doing so in the right place :)
[17:42] <flexiondotorg> cjwatson, I fully prepared to accept I've messed it up somewhere 😃
[17:42] <flexiondotorg> cjwatson, I can make my build logs available a bit later.
[17:43]  * cjwatson finds the MATE seeds and does a test germinate run
[17:43] <flexiondotorg> cjwatson, I am seed 'marco' in the live seed.
[17:43] <flexiondotorg> cjwatson, Which then creates a duplicate in the 'desktop' seed.
[17:44] <cjwatson> You don't need it in the live seed, and in any case marco isn't in http://bazaar.launchpad.net/~ubuntu-mate-dev/ubuntu-seeds/ubuntu-mate.utopic/view/head:/live
[17:45] <flexiondotorg> cjwatson, So should I leave 'marco' in the 'live' seed and 'desktop' see?
[17:45] <cjwatson> It's not in the live seed, as far as I can see.
[17:45] <cjwatson> Unless your seeds are somewhere other than where I'm looking.
[17:46] <flexiondotorg> cjwatson, You are looking in the right place. marco was in the live and desktop seeds. But I got duplicate warnings so I removed from the desktop seed.
[17:46] <flexiondotorg> cjwatson, Should I leave marco in both the live and desktop seed?
[17:46] <cjwatson> But it is not in the live seed there right now.
[17:46] <cjwatson> It is in the desktop seed, which is where it belongs.
[17:47] <cjwatson> A test germinate run against your seeds doesn't pull in metacity.
[17:48] <flexiondotorg> cjwatson, Hence my confusion as to why metacity is in the resulting image and also the default.
[17:48] <cjwatson> So image builds at least with our code wouldn't pull in metacity, as far as I can see.  I don't know what your code is doing.
[17:48] <flexiondotorg> cjwatson, OK that sounds encouraging.
[17:48] <cjwatson> Perhaps you're using a different build process ...
[17:49] <flexiondotorg> cjwatson, Another issue I can possible chalk up to "if was built officially".
[17:49] <cjwatson> Is your build code pushed somewhere I can see?
[17:49] <flexiondotorg> cjwatson, Thanks for you help again. Most appreciated.
[17:49] <flexiondotorg> cjwatson, Yes. I'll just pushed to current version...
[17:51] <flexiondotorg> https://code.launchpad.net/~ubuntu-mate-dev/ubuntu-mate/ubuntu-mate-iso
[17:55] <cjwatson> flexiondotorg: You need to drop "LIVE_TASK='ubuntu-live'" from your modified livecd-rootfs in the ubuntu-mate section.  That'll be causing it to pull in the ubuntu-live task, which won't be appropriate for you.
[17:56] <cjwatson> You're already installing the ubuntu-mate-live metapackage, so the ubuntu-live task is at best redundant and at worst will cause problems like this.
[17:59] <flexiondotorg> cjwatson, Many thanks. I'll make that change.
[18:33] <tvoss> mvo, around?
[18:33] <mvo> tvoss: yes, at a conference so a bit busy, but available
[18:47] <pitti> stgraber, infinity: I'm uploading calibre 2.0.0 to sid which ports from qt4 to qt5; would you consider that a feature (the UI is actually the same), i. e. needs an FFE?
[18:48]  * pitti just purged qt4 from his system, yay
[19:01] <stgraber> pitti: that's a borderline one, I guess just apply for an FFe, I'll confirm it's only depended upon by Edubuntu and then grant you the FFe
[19:05] <jtaylor> when is trusty unapproved being processed next?
[19:05] <jtaylor> been 3 weeks now already
[19:10] <mlankhorst> when you bug sru admins ;-)
[19:12] <arges> jtaylor: which particular package are you interested in?
[19:12] <jtaylor> tango
[19:14] <arges> jtaylor: can you fill in the rest of the SRU template on the bug (regression potential, impact)
[19:15] <arges> jtaylor: also it may be easier to identify where the patches come from if you use the DEP-3 tag 'Origin'
[19:19] <jtaylor> I'd have got to ask the debian maintainer about that, he told me when I sponsored but thats long out of my logs ._.
[19:20] <arges> jtaylor: well its probably ok since the other patchsets seem to be in the same style.
[19:20] <arges> jtaylor: just let me know when you filled out the rest of teh SRU template on that bug
[19:26] <kyleN> just did dist-upgrade on utopic and got this:
[19:26] <kyleN> dpkg: error processing archive /var/cache/apt/archives/unity-schemas_7.3.1+14.10.20140811-0ubuntu1_all.deb (--unpack):
[19:26] <kyleN>  trying to overwrite '/usr/share/glib-2.0/schemas/org.compiz.unityshell.gschema.xml', which is also in package libunity-core-6.0-9 7.3.0+14.10.20140711-0ubuntu1
[19:26] <kyleN> workaround?
[19:34] <seb128> kyleN, try to apt-get -f install it should work
[19:34] <jtaylor> arges: done
[19:34] <kyleN> seb128, didn't
[19:36] <seb128> kyleN, weird, can you paste the log from a -f install?
[19:36] <kyleN> sure, hang on
[19:36] <arges> jtaylor: thanks! Ok accepted.
[19:37] <kyleN> seb128, http://paste.ubuntu.com/8152652/
[19:39] <seb128> kyleN, try to sudo apt-get install libunity-core-6.0-9
[19:40] <kyleN> seb128, http://paste.ubuntu.com/8152688/
[19:41] <seb128> kyleN, try to sudo apt-get install libunity-core-6.0-9 unity-schemas
[19:41] <kyleN> seb128, http://paste.ubuntu.com/8152695/
[19:42] <seb128> kyleN, apt-cache policy unity-services
[19:42] <seb128> kyleN, or try to add unity-services to the install list
[19:43] <kyleN> seb128, your first suggestion: http://paste.ubuntu.com/8152701/
[19:43] <kyleN> seb128, your second: http://paste.ubuntu.com/8152704/
[19:43] <seb128> shrug
[19:44] <seb128> kyleN, add libunity-protocol-private0 qtdeclarative5-ubuntu-content1 to the list?
[19:44] <kyleN> seb128, alas: http://paste.ubuntu.com/8152712/
[19:45] <seb128> kyleN, keep adding the packages in front of the line and see if you manage to unblock it
[19:45] <seb128> like libunity9 ibunity-dev unity
[19:45] <seb128> you might get new ones, try iterating
[19:46] <seb128> did/do you have ppas or weird versions installed?
[19:48] <kyleN> I seb128 not utopic ppas installed
[19:48] <seb128> :-/
[19:49] <seb128> kyleN, adding extra source doesn't help resolving it?
[19:49] <seb128> source->binaries
[19:49] <seb128> to the install line
[19:49] <kyleN> seb128, example command pls?
[19:50] <seb128> kyleN, well, the install you had, addlibunity9 ibunity-dev unity
[19:50] <seb128> ups
[19:50] <seb128> libunity9 libunity-dev unity
[19:50] <seb128> it might give you extra errors with new package name
[19:50] <seb128> keep adding those to the install and try again
[19:50] <seb128> until it gives you one that might work
[19:51] <kyleN> ok. I'll work on this. thanks for the tips
[19:51] <seb128> yw
[19:51] <seb128> well, let me know how it goes
[19:51] <seb128> try just adding those and pastebin again
[19:51] <seb128> it's weird that it requires so much forcing though
[19:52] <seb128> you might try aptitude otherwise, its resolver works better sometimes...
[20:09] <kyleN> sebs, aptitude to the rescue :)
[20:10] <kyleN> $ sudo apt-get install -f
[20:10] <kyleN> Reading package lists... Done
[20:10] <kyleN> Building dependency tree
[20:10] <kyleN> Reading state information... Done
[20:10] <kyleN> The following packages were automatically installed and are no longer required:
[20:10] <kyleN>   linux-headers-3.15.0-6 linux-headers-3.15.0-6-generic linux-headers-3.16.0-4 linux-headers-3.16.0-4-generic linux-image-3.15.0-6-generic
[20:10] <kyleN>   linux-image-3.16.0-4-generic linux-image-extra-3.15.0-6-generic linux-image-extra-3.16.0-4-generic
[20:10] <kyleN> Use 'apt-get autoremove' to remove them.
[20:10] <kyleN> 0 upgraded, 0 newly installed, 0 to remove and 675 not upgraded.
[20:10] <kyleN> seb128, ^
[20:12] <seb128> kyleN, what did aptitude do exactly?
[20:14] <kyleN> seb128, nver used aptitude before :( . It reported a lot of packages and I used the 'g' option to handle them. they were removed and reinstalled (not sure if they all were reinstalled)
[20:15] <kyleN> I have the list of pkgs if that interested you (a copy of part of stdout during the operation)
[20:18] <kyleN> seb128, here are the removals through aptitude: http://paste.ubuntu.com/8152916/
[20:18] <jtaylor> arges: thanks
[20:20] <kyleN> seb128, I still have the complete stdout of aptitude here: http://paste.ubuntu.com/8152929/


[00:00] <Sarvatt> ripps: just no change rebuild libvdpau on your PPA for now since it'll build fine there :)
[00:13] <ion> sarvatt: :-)
[00:15] <Sarvatt> actually it may just be fail in the detection scripts, let me take a look
[00:15] <Sarvatt> X.org <IP_ADDRESS>1, required X.org <IP_ADDRESS>. -- looks like its just failing
[00:19] <ion> sarvatt: Oh, btw, i made http://heh.fi/tmp/fglrx-installer-abiver.patch earlier, but didn’t get around to posting it anywhere since fglrx failed to install on my system at the time due to me not having patches for kernel 2.6.35. I copied the rules to provide xserver-xorg-video-$ABIVER from the nvidia driver packaging verbatim.
[00:21] <Sarvatt> the one in x-updates failed on 2.6.35? it works fine here!
[00:21] <ion> No, before i found a package with the patches in the PPA. :-)
[00:22] <Sarvatt> ion: personally i dont think they should be providing an abi at all since they arent tied to an abi
[00:22] <Sarvatt> nvidia-current works with multiple video abi's and the packaging only provides one, and it took a week and a half for it to get no change rebuilt against the new abi even though it worked :(
[00:23] <ion> Ah, ok. Dunno what is the right way to go, i just came up with that when fglrx stopped working after an xorg update in maverick. It would have been nice if that version of the fglrx package had blocked that xorg update.
[00:25] <Sarvatt> yeah thats true, it probably would be more helpful on ati :)
[00:25] <Sarvatt> since they take 6 months to update things
[00:25] <Sarvatt> nvidia supported xserver 1.8 back in november or december
[00:26] <ion> And the free drivers supported it... pretty much immediately. :-P
[00:31] <Sarvatt> trying to figure out where it gets that <IP_ADDRESS> string from
[00:32] <Sarvatt> ion: do you have an xorg log from a failed boot by any chance?
[00:32] <Sarvatt> ah its in atiddxSetup from what you pasted, nevermind
[00:34] <Sarvatt> i've got an fglrx machine now so i can test hex editing the blob to work around it :)
[00:35] <Sarvatt> doesn't look like its a registry option that can be adjusted but i need to go over some more strings to be sure
[00:36] <ion> Hehe
[00:38] <Sarvatt> ya remember if that atiddxSetup error happened after loading a specific module?
[00:40] <ion> I’ll install fglrx and save the log this time, a moment.
[00:42] <ion> I’ll have to take a look at making nvidia_supported work again with the new nvidia release at some point. (I contributed the original _supported scripts.)
[00:46] <Sarvatt> oh really? thank you for doing that, i couldn't work it out
[00:48] <Sarvatt> my fglrx machine is finally done compiling chromium so i can do it
[00:50] <ion> Ok, the new nvidia driver no longer has the duplicate PCI ID list, so that heuristic can’t be used anymore. I’ll come up with something new.
[00:51] <ion> Alright
[00:55] <Sarvatt> ah looks like fglrx-2.6.33.patch isnt needed anymore
[00:56] <Sarvatt> gotta upload a new version without it
[01:13] <Sarvatt> darn, that message doesn't even show up for me - http://pastebin.com/At3G7UUY
[02:14] <Sarvatt> hmm http://sarvatt.com/downloads/xserver.gdb.txt
[02:38] <ripps> Yo, I'm back.
[02:40] <ripps> Sarvatt: Since BlackZ not here, I'll tell you. I'd file a bug, but since I don't have amd64, it feel like it's inappropriate. Also, I can't file bugs against ia32-libs because since the package isn't availble for my computer, apport tells me the package doesn't exist.
[03:32] <Sarvatt> ripps: just upload libvdpau to your PPA to fix it..
[03:32] <Sarvatt> make it 0.4-5+ripps or something
[03:33] <ripps> Sarvatt: yeah, that sounds like a good plan. I was just hoping that this could be fixed for everybody, not just me.
[03:34] <Sarvatt> you're telling me you want me to file the bug because you need ubuntu-bug or something?
[03:34] <Sarvatt> i can't upload it :)
[03:36] <ripps> Sarvatt: well, I actually started this in ubuntu-motu. But it got moved over here somehow :P
[03:37] <ripps> I can't file bugs against ia32-libs, because apport will only let me file bugs against my i386 packages. How do you file bugs manually these days?
[03:38] <ripps> Did you guys find a fix? you mentioned something about VDPAU_MODULEDIR
[03:39] <Sarvatt> superm1: any idea what to do about libvdpau-dev needing ia32-libs now and not being in main? as far as I can tell just dropping the lib32vdpau package is fine for now since we never shipped a seperate 32 bit version
[03:39] <Sarvatt> ripps: no
[04:01] <superm1> Sarvatt, agree
[04:02] <superm1> i wish debian would do what we did with putting all the nvidia stuff in a single package
[04:02] <superm1> seems so much more sensible this way
[04:03] <Sarvatt> ion: it looks like fglrx 10.6 in x-updates works with xserver 1.8, I was wrong!
[04:03] <bjsnider> since when does libvdpau-dev require ia32-libs?
[04:03] <Sarvatt> problem is, jockey's xorg.conf doesn't work
[04:04] <Sarvatt> ion: http://pastebin.com/2Ti6wMNe
[04:15] <Sarvatt> BusID "PCI:1:0:0" is required in xorg.conf in fglrx 10.6, ati just mentioned it
[04:15] <Sarvatt> or whatever the busid is for your system, fun
[04:41] <ion> Alright. Yay for nerfing autoconfiguration. :-P
[04:45] <ion> I didn’t manage to come up with a future-proof way to scrape PCI IDs from the nvidia driver yet. I tried to find a consistent code path from a non-obfuscated symbol to the list, but failed so far. Perhaps i’ll just do another heuristic that may work for a few years and then fail with some future release, requiring yet another new heuristic. :-P
[04:47] <Sarvatt> they aren't going to add new ones to the old releases, can't we just include all pci ids included in the new ones or does it contain more than it supports?
[04:47] <ion> New releases add support for new cards with new PCI IDs.
[04:48] <Sarvatt> yeah, is there no way to dump every pci id in that blob since it only has the ones it works with?
[04:48] <ion> That’s exactly what nvidia_supported does. :-)
[04:49] <ion> The trick is scraping the data from the blob in a way that doesn’ṭ require tinkering for every release.
[04:49] <ion> The previous trick worked a long time, but now they changed stuff and it doesn’t work anymore.
[04:49] <Sarvatt> oh, i thought it was removing some from that list for some reason
[04:50] <ion> If the data was behind a consistent symbol in the object file, everything would be fine. But it’s behind an obfuscated symbol which changes names on every release.
[04:52] <Sarvatt> why dont we just pull it from html/supportedchips.html?
[04:54] <ion> At the point i originally wrote nvidia_supported, the HTML list wasn’t maintained properly. In every release, it had major differences to the actual data. I should check if that’s fixed by now, actually.
[04:55] <Sarvatt> ahh gotcha, i've been checking it since around 185.35.15 and its been updated every time they add new cards at least
[04:57] <ion> They were updating it, yes, but it almost seemed as if a human received a list of added and removed PCI IDs and manually updated the HTML for every release, and errors kept creeping up every time :-P. One would think they could just autogenerate the HTML from the source code, but that wasn’t a case at least back then.
[04:58] <ion> the case
[05:01] <Sarvatt> ahh gotcha, checking how other distros do it now
[05:06] <ion> Anyhoo, it’s easy enough to modify nvidia_supported to detect the list from the current release and from a number of foture releases as long as they don’t change the format again. I don’t expect that to happen for a while. I was trying to come up with an almost completely future-proof solution, but that might not happen. And yeah, i’ll compare the list from the blob from the newest release to the HTML, perhaps they’ve fixed it.
[05:15] <Sarvatt> hmm, went to look at nvidia-installer to see how it checks since its open source, and just saw there was a new nvidia release
[05:35] <Sarvatt> darn, the nvidia 256.35 x86_64 ftp directory has the x86 one in it so i cant package it up yet
[05:45] <Sarvatt> found it, check_for_nvidia_graphics_devices() - http://cgit.freedesktop.org/~aplattner/nvidia-installer/tree/misc.c?id=19a9146a421689b409588c9505364024378e1dd1
[05:45] <Sarvatt> gotta run though, will see what it does when i get back :)
[06:01] <ion> Ok, it only has a list of legacy devices, and anything nVidia && VGA that isn’t in it is deemed supported.
[06:08] <Sarvatt> can we just use 0x04** - 0x0F** or do we have to explicitly define each one?
[06:09] <Sarvatt> ah nope their other devices are in that namespace too
[06:12] <ion> In any case, any list that is not directly based on the actual code of the newest release available for each series has a chance of being inaccurate, and nVidia’s track record hasn’t been good with such lists.
[06:13] <ion> Using such a list would probably work for most users, but then there would be hard-to-verify bug reports from users that just happen to have a card that the list missed.
[06:19] <superm1> Sarvatt, ion what about taking the approach of what NV installer does and just say everything is supported, and then maintain a blacklist of (earlier) stuff that isn't?
[06:19] <superm1> they do announce when they drop support generally, don't they?
[06:20] <Sarvatt> does jockey understand pci device namespaces?
[06:20] <Sarvatt> it uses libpciaccess?
[06:20] <Sarvatt> i mean you need to tell it to restrict it to 10de vendor id's and only look at video devices
[06:23] <Sarvatt> or is that info in the modalias already? i dont know what everything in pci:v00001002d00009715sv*sd*bc*sc*i* means
[06:25] <Sarvatt> how would you tell jockey to use everything is what I'm asking basically
[06:27] <ion> sarvatt: Here’s the diff from blob to HTML for 256.29, btw: http://gist.github.com/444604#file_list.diff
[06:28] <ion> From HTML to blob, i mean.
[06:28] <ion> The blacklist of earlier stuff would still need to be parsed the same way.
[06:29] <Sarvatt> blob is reporting some false positives then
[06:29] <ion> I’d trust the code maintained by coders more than the HTML maintained by documenters. :-P
[06:30] <Sarvatt> 0cxx is the highest pci id they have for the newest generation gpu's though
[06:30] <Sarvatt> maybe those other devices are agp-pcie bridge chips, lessee
[06:31] <Sarvatt> and that would make sense because the actual pci id of the card is hidden behind the bridge chip and not listed on that list i bet
[06:31] <Sarvatt> same problem i had with extracting pci id's on nv
[06:33] <superm1> Sarvatt, well i dont think jockey can right now; that would have to be an additional patch to it
[06:34] <Sarvatt> yep the 02xx ranges in the blob extracted one are indeed bridge chip pci ids that we'd need to add
[06:34] <Sarvatt> html is definitely out :)
[06:35] <Sarvatt> 08xx ranges are IGP's
[06:38] <ion> I wonder if nvidia would put the table (it’s just data: the PCI IDs and some flag bits probably designating each chip’s features) behind a non-obfuscated symbol if we asked nicely? :-)
[08:22] <Sarvatt> would it be wrong to hack up a postinst to run aticonfig --initial after install for fglrx? ati is insisting its required and something tells me they're not going to fix what they broke making it really be required now
[08:58] <Sarvatt> heh all of those id's I thought were wrong in your list were all removed in 256.35
[08:59] <Sarvatt> probably prerelease cards they meant to keep internal
[08:59] <Sarvatt> the 0Dxx-0Exx ones
[09:00] <ion> Ok
[09:01] <Sarvatt> this still works though - objdump --section=.rodata --full-contents --start-address=0x3940 --stop-address="$((0x3940+0x2540))" NVIDIA-Linux-x86-256.35/kernel/nv-kernel.o | sed -nr 's/^ [0-9a-f]+ ([0-9a-f]{2})([0-9a-f]{2})0000.*/\2\1/p' | sort | uniq | grep -vx 0000
[09:01] <ion> Probably by accident, and you may have a slightly incorrect range.
[09:02] <ion> I’ll get some sleep soon, but after that i’ll try to get around to making the necessary changes to nvidia_supported.
[09:03] <Sarvatt> there's only a 3k difference in all files combined in .35, pretty much the same thing as .29
[09:03] <Sarvatt> night!
[09:03] <ion> I’ll finish this episode of B5 first, though. :-)
[09:07] <ion> objdump --section=.rodata --syms .../nv-kernel.o | less, and find the one with length near 0x2540 starting near 0x3940, and pass those numbers to the --full-contents snippet to get the correct list. But i’m going to script a bit of heuristics to get the right symbol deterministically.
[09:10] <ion> To find the symbol starting at 0x3940 in the first place (for 256.29), i just ran objdump --section=.rodata --full-contents .../nv-kernel.o | less and searched for 4200 (a random PCI ID i expected to find, 0x0042 in little-endian order) in an area that looked like a nice list of IDs, picked the offset of the beginning of the list and looked up the matching symbol from --syms.
[09:18] <ion> sarvatt: nvidia_supported originally accepted multiple versions of nv-kernel.o as parameters and didn’t add PCI IDs to older versions that were supported by a newer version. Is that functionality still needed? The script could be simplified by dropping it, since it doesn’t seem to be used.
[09:22] <Sarvatt> i'd drop it personally, it's useful to be able to use the old drivers on newer cards where support overlaps to test stuff
[09:22] <ion> Alright
[17:51] <Sarvatt> looks like i'm disappearing for awhile..  it's been fun you guys
[18:05] <johanbr> Sarvatt, oh! thank you for your all your work
[19:05] <Duke`> disappearing for awhile !!?
[19:31] <Sarvatt> yeah bad timing between cutting back on work thinking i was getting another job and having to find a new apartment at the last minute :(
[23:39] <ion> sarvatt: http://gist.github.com/raw/445368/ab14590fc18aedbf5f10b3b74feddb853f7fbfbc/nvidia_supported
[23:39] <ion> sarvatt: That should work for all versions of the driver.
[23:45] <ion> sarvatt: Changed it a bit: http://gist.github.com/raw/445368/6b54c1c04836d3d9d9061cdf0b25c60b8c4c0e38/nvidia_supported