[07:10] <dholbach> good morning
[22:39]  * Bl4ckD34Th Bl4ckD34Th return to take your soul! You own to Bl4ckD34Th!!!


[12:12] <coz_> i like it as so far very nice simple colorgul look easy to maneuver in
[12:12] <coz_> colorful
[12:14] <coz_> vdepizzol, I like it all I wold just clen up the ubuntu logo symbol the edges seem choppy
[12:14] <coz_> just my opinion
[12:14] <vdepizzol> coz_: thank's :)
[12:14] <coz_> vdepizzol, what about the font? you didn't want to use the official ubuntu ttf?
[12:16] <vdepizzol> coz_: I didn't try. I'll :)
[12:16] <coz_> vdepizzol, well I like the design very much :)
[12:36] <darkmatter> vdepizzol, lovely work mein freund.. it looks very nice thus far
[12:38] <coz_> darkmatter, agreed
[12:38] <coz_> darkmatter, but you and I are perverts so what do we know:0
[12:39] <darkmatter> :P
[12:39] <coz_> darkmatter, so tell be about saskatcuan not spelled ritht of course
[12:40] <darkmatter> coz_ you'll like the top secret work being done on Glory... wasn't by intent, but the widget layout is picking upa few traits that I know will bring back memories
[12:40] <coz_> oooo darkmatter i think i understand:)
[12:41] <coz_> darkmatter, even if it is not yellow I will like  it :)
[12:41] <darkmatter> well... saskatchewan is cold... has cows, wheat, potash, oil, uranium, and hotties
[12:41] <darkmatter> lol
[12:41] <darkmatter> coiz_ yup... like that
[12:41] <darkmatter> I just noticed the "neo <that>" traits last night
[12:42] <coz_> darkmatter, I like cold, I don't eat cows I like wheat don't use postash I don'tthink . oil is ok uranium you can keep and hotties cool
[12:42] <darkmatter> its not the same thing obviously... but it has a really interesting feel
[12:42] <darkmatter> lol
[12:43] <coz_> darkmatter, well I know you will do it well, so whatever  you have is fine with me... I am interested in your concepts and how you carry them out so i will like it icomes from one like mind
[12:44] <coz_> darkmatter, what about work up there
[12:44] <coz_> jobs
[12:45] <darkmatter> work?? theres enough... more opportunities arising et... would be nice if I wasnt on disability... could get a half decent one
[12:46] <darkmatter> not saying its exeedingly diverse employ (as in choice of career)... but its there
[12:47] <coz_> darkmatter, thinking of making a run from all I have here don't be surprised if you see me up there :)
[12:47] <darkmatter> lol
[12:47] <vdepizzol> darkmatter: :)
[12:48] <darkmatter> coz, was thinking of the thing you mentioned about my theme "how ya though it might have had yellow" thing before ya saw it
[12:48] <darkmatter> dude.. that was inspiration
[12:49] <darkmatter> the "morningglory" scheme is actually shifted to a base of very pale honey...
[12:49] <darkmatter> kinda golden but not a yellow
[12:49] <darkmatter> almost a creamy color
[12:49] <coz_> darkmatter, well doesn't need to be yellow ..actually it wold be nice to see tha tin different colors come to think of it, although the yellow looked fine for be  more pastel shades would look nice also
[12:49] <coz_> darkmatter, ok ifinished typing that before I read what you just typed :)
[12:49] <darkmatter> glry will be the gray
[12:50] <darkmatter> *glory
[12:50] <coz_> oooo creamy colors are nice
[12:50] <coz_> i am freezing here 7F
[12:50] <darkmatter> I'm freezing too... its -22c
[12:50] <darkmatter> :O
[12:50] <coz_> ok now I have to do my math or google the difference beween f and c
[12:51] <coz_> brb nephew dropped in
[12:51] <vdepizzol> coz_: Brazilian summer here: 23C
[12:51] <darkmatter> just google "f toc:
[12:51] <darkmatter> bah
[12:51] <darkmatter> missed em
[03:27] <MayaAntz> hello
[05:21] <La_PaRCa> hey guys. Quick question: What is the font used for the ubuntu strapline?
[06:15] <La_PaRCa> Hey guys, does anyone know the name of the font on the ubuntu logos?
[06:18] <troy_s> La_PaRCa: yes
[06:18] <troy_s> ubuntu-title ttf
[06:18] <troy_s> apt-cache search ubuntu title
[06:19] <troy_s> sudo apt-get install ttf-ubuntu-title
[06:19] <La_PaRCa> troy_s, awesome!
[06:19] <La_PaRCa> thanks
[06:19] <troy_s> erm
[06:19] <troy_s> if you mean the font underneath
[06:19] <troy_s> i believe the other one, with the tails, is modata
[06:19] <troy_s> and if all else vails
[06:19] <troy_s> fails
[06:19] <troy_s> http://www.myfonts.com/WhatTheFont/
[06:19] <troy_s> good luck :)
[06:20] <La_PaRCa> ok, thanks
[06:34] <La_PaRCa> doesnt seem like I can find the font for the text underneath
[06:54] <BHSPitLappy> ugh
[06:54] <BHSPitLappy> the Show Desktop button is so badly implemented
[06:54] <BHSPitLappy> it's like the whole button itself is bitmapped in
[06:55] <BHSPitLappy> when you have a transparent panel, it's the only button that doesn't go transparent with it
[11:17] <darkmatter> ping
[02:26] <kwwii> anyone know where the original files are for the usplash?
[02:27] <kwwii> I wanted to try and improve on the progress bar backgrounds
[03:11] <kwwii> Seveas: I am working on improving the usplash, could you explain a few things to me?
[03:16] <Seveas> kwwii, sure
[03:16] <Seveas> kwwii, btw, I'm making patches to mak using everything easier. I assume you only want to change the artwork and not the code?
[03:16] <kwwii> Seveas: what do the *-16.png files do?
[03:16] <Seveas> 16-color files
[03:16] <kwwii> Seveas: yepp, only small artwork changes this time
[03:16] <Seveas> used on amd64
[03:17] <kwwii> Seveas: but they have a 256 colormap...funny
[03:17] <Seveas> that indeed is funny
[03:17] <Seveas> someone should be slapped
[03:17] <kwwii> ;-)
[03:19] <kwwii> I hope to have something done by tomorrow...I'll ping you so you can have a look at what I have made
[03:20] <kwwii> Seveas: one of the problems is that people seem to think that the progress bar is smaller than on the desktop. sabdfl would like to have the progress bar look exactly like the one on the desktop
[03:20] <kwwii> although the pixel size is the exact same :-)
[04:14] <alefteris> hi everyone! could someone point me to the upstream for the edgy/feisty gdm themes?
[04:17] <kwwii> alefteris: I doubt that the gdm from ubuntu went upstream since it is distro specific
[04:19] <kwwii> but if you want the sources for it, run "apt-get source ubuntu-artwork"
[04:21] <alefteris> kwwii, ok that is what i did.. so the sources for the theme are kept ionly n bazzar?
[04:27] <kwwii> alefteris: guess so, not sure where else they should be kept ;-)
[04:28] <kwwii> bbl
[04:28] <alefteris> can someone take look at this https://launchpad.net/ubuntu/+source/feisty-gdm-themes/+bug/70829
[04:28] <Ubugtu> Malone bug 70829 in edgy-gdm-themes "gdm theme should use dejavu fonts" [Low,Needs info]
[04:52] <TheSheep> troy_s: you here?
[04:52] <troy_s> there you are!
[04:52] <troy_s> thesheep where the hell you been?
[04:52] <troy_s> tsk tsk
[04:52] <troy_s> great to see you here.
[04:53] <troy_s> TheSheep: ?
[04:53] <TheSheep> troy_s: I don't think I will be able to help the project on regular basis :(
[04:54] <TheSheep> troy_s: several other of my projects started to be alive, and I was a little busy lately
[04:54] <TheSheep> troy_s: I'm sorry
[05:02] <alefteris> troy_s, could you please take a look at this bug https://launchpad.net/ubuntu/+source/feisty-gdm-themes/+bug/70829. What I need to do next to push this forward?
[05:02] <Ubugtu> Malone bug 70829 in edgy-gdm-themes "gdm theme should use font aliases" [Low,Needs info]
[05:03] <alefteris> you can see the differerces here http://librarian.launchpad.net/5809389/screenshot2.png and http://librarian.launchpad.net/6298458/Screenshot-FeistyVM.png
[05:35] <troy_s> alefteris: Ideally
[05:35] <troy_s> alefteris: "Branch" a bzr repository of the issue in question
[05:36] <troy_s> as in
[05:36] <troy_s> 'sudo apt-get install bzr' (if you don't already have it)
[05:37] <troy_s> go to www.launchpad.net/products and find the 'product' in question
[05:37] <troy_s> in this case, feisty-gdm-themes
[05:37] <troy_s> click on 'code' in the left panel to get the list of branches that are available from bzr
[05:38] <troy_s> click on the branch in question
[05:38] <troy_s> and copy the link for use with bzr
[05:38] <troy_s> in this case, it is:
[05:38] <troy_s> bzr branch http://bazaar.launchpad.net/~ubuntu-art-pkg/feisty-gdm-themes/ubuntu
[05:38] <troy_s> oops
[05:38] <troy_s> bzr branch http://bazaar.launchpad.net/~ubuntu-art-pkg/feisty-gdm-themes/ubuntu my-local-feisty-gdm-themes
[05:38] <troy_s> which will create a subdirectory called 'my-local-feisty-gdm-themes'
[05:38] <troy_s> go into that directory, and make the changes.
[05:39] <troy_s> test it (either using symlinks or trying the make which may not work if you have added files)
[05:39] <troy_s> once you are certain you have fixed the issue
[05:39] <troy_s> push your 'new' branch as per wiki.ubuntu.com/Bzr and register it against the bug report by selecting 'add a branch' and notify the bug listing.
[05:39] <troy_s> phew.
[05:39] <troy_s> basically two steps:
[05:40] <troy_s>  1) branch the bzr and make your fixes
[05:40] <troy_s>  2) push and update bug listing with a comment and a branch
[05:40] <troy_s> that makes it easiest for daniel to merge your changes.
[05:40] <troy_s> alefteris: Ok?
[05:40] <troy_s> if you need further help or tutoring, just ping me.
[05:41] <alefteris> troy_s, ok this seems a lot easier than the way I made a patch from the sources :)
[05:41] <troy_s> it is very easy
[05:41] <troy_s> the problem is, if you haven't setup bzr yet, you will need to take an additional step to set it up at launchpad
[05:41] <troy_s> once you have done that, it is _very_ easy to push changes
[05:41] <alefteris> when i finish, who should i contact? daniel?
[05:42] <troy_s> note -- they won't take effect until one of the artwork packagers takes notice...
[05:42] <troy_s> no.
[05:42] <troy_s> although he is an artwork packager
[05:42] <troy_s> the best bet
[05:42] <troy_s> is to simply subscribe or make sure that an artwork packager is subscribed.
[05:42] <alefteris> i should assign the bug to ubuntu-artwork-packagers?
[05:43] <alefteris> ok thanks
[05:43] <troy_s> https://launchpad.net/~ubuntu-art-pkg
[05:43] <troy_s> you could subscribe the team yes
[05:43] <troy_s> that SHOULD notify them
[05:43] <troy_s> but again, the formalized process is missing key players to take on the duties.
[05:43] <troy_s> those folks have team access to the bzr so they can push formal changes to the main 'trunk' branch
[05:44] <troy_s> kwwii has access too
[05:44] <troy_s> and he is probably a good pointman now as canonical is paying his rent
[05:44] <kwwii> :-)
[05:44] <troy_s> there he is :)
[05:44] <alefteris> hehe#
[05:44] <troy_s> the bottom line though
[05:44] <kwwii> just got back from my walk
[05:44] <troy_s> is that you want to make it as PAINLESS for the packagers as possible
[05:44] <kwwii> alefteris: are you talking about the font change in gdm?
[05:44] <troy_s> which means using bzr
[05:44] <alefteris> kwwii, yes
[05:44] <lizardking> hi
[05:44] <troy_s> then they can simply do a bzr merge
[05:44] <troy_s> without farting around with pain
[05:44] <lizardking> what do you are talking about?
[05:45] <troy_s> bzr merge, bzr push
[05:45] <troy_s> lizardking: fixing reported bugs
[05:45] <kwwii> alefteris: I agree completely with you, so once it is pushed we'll use it
[05:45] <alefteris> ok I do it right away
[05:45] <troy_s> alefteris:  oh yes... i forgot to mention
[05:46] <kwwii> if we do it before thursdasy it will be in the next herd
[05:46] <lizardking> troy_s: is there new feisty artwork or is the same than edgy?
[05:46] <troy_s> make sure that the 'powers that be' agree before you bother to work on something.  they will be a little more responsive now that we have kwwii handling ubuntu details.
[05:46] <troy_s> lizardking: kwwii is handling that.
[05:46] <troy_s> lizardking: if you are wise, you would not try to get involved as it directly involves the master of aesthetic nightmares himself -- sabdfl.
[05:47] <troy_s> lizardking: but that is just my 2c.
[05:47] <troy_s> lizardking: pretty sure that who_, jmak, fschoep, and others anyone else who survived his edgy endgame would agree.
[05:49] <lizardking> troy_s: Last week I wrote at sabdfl asking the question of trademark
[05:50] <troy_s> trademark regarding?
[05:50] <kwwii> from what I understand the decision making for the default theme will stay in canonical hands at least for a little while (as he is paying for this). This doesn't mean that people cannot work on it, it just means that the direction it takes will be directly controlled by someone
[05:51] <lizardking> troy_s: yes, he does not answer me yet
[05:51] <kwwii> in the meantime, the plan is to make the automated theme building stuff as good/simple as possible
[05:51] <troy_s> kwwii:  Practically, it means that working on it is nightmarish without design concepts and such.  Unless you value the 'throw sh*t at the wall and hope it sticks' approach.
[05:51] <kwwii> so that everyone can create a theme however they like
[05:51] <troy_s> lizardking: he probably wont... you have to appreciate that sabby is _damn_ busy
[05:51] <kwwii> troy_s: yeah, that is part of what I am trying to work out
[05:51] <troy_s> and he gets about sixteen thousand emails a day.
[05:52] <kwwii> lizardking: perhaps I could answer your question
[05:52] <lizardking> troy_s:  yes I suppos that
[05:52] <troy_s> kwwii: Problem is you can't work it out if the guy who is calling the aesthetic judgements has zero sense on the matter nor ideas on implementation strategies.
[05:52] <lizardking> kwwii: I'm hearing you
[05:53] <troy_s> alefteris: https://wiki.ubuntu.com/BzrContributorHowto
[05:53] <kwwii> troy_s: hopefully once I "prove" myself things will change in that regards
[05:53] <troy_s> there is a summary of what i just described, but with different teams involved.
[05:53] <troy_s> kwwii:  I don't know.  I suspect he wants a patsy, which might earn his faith, but possibly doesn't help the larger issues.
[05:54] <kwwii> well, that is my fear as well ;-)
[05:54] <troy_s> kwwii:  The main problem is that
[05:54] <troy_s> kwwii: "art" is actually a many pronged element in an operating system -- there is implementation artwork (like icons/walls/etc) but then there is the artistry of design.
[05:54] <troy_s> which is an entire other can of worms.
[05:55] <troy_s> kwwii:  The true unfortunate portion of this entire puzzle is that there are some _very_ knowledgeable folks already in our midst who would at least be able to engage the concepts on a semantic level and attempt to address them in terms of future design patterns.
[05:55] <troy_s> (read people like Darkmatter, TheSheep, etc.)
[05:56] <lizardking> kwwii: : please Can you tell me what is the answer to my question?
[05:56] <troy_s> knowledgable _and_ researched.
[05:56] <troy_s> lizardking: Your question needs clarification.  What form of licensing for what?
[05:56] <kwwii> lizardking: I didn't quite understand the question
[05:57] <lizardking> kwwii: :ok, I mean the truoble of oransoda trademark. Kwwii tells me that he has the answer
[05:57] <kwwii> troy_s: I think that until now the biggest problems have been that of simple artwork and continuity, not the bigger, more long term design issues
[05:58] <kwwii> lizardking: well, you cannot use anything that is trademarked by anyone
[05:58] <kwwii> lizardking: that is a major no-no, unless you have permission from those who hold the trademark
[05:58] <troy_s> kwwii:  I think most people who try to get involved with ubuntu artwork seek to break off from the continuity that has been established.
[05:58] <troy_s> kwwii:  Arguably, making _any_ change is a departure from continuity.
[05:59] <kwwii> troy_s: yepp, we tend to get 8 differing opinions from 5 people
[05:59] <troy_s> kwwii:  Currently, the continuity is nothing more than an accident that happens to meet sabdfl's liking.
[05:59] <lizardking> kwwii: : ok
[05:59] <troy_s> kwwii:  lol.  To say the least.
[05:59] <kwwii> that is also true, probably because he doesn't have the time to lead this correctly
[05:59] <troy_s> kwwii:  But the bottom line is that if the end result of all of this is to simply make the Ubuntu current look operate more effectively, I don't know how much support there is going to be in the end.
[05:59] <cryingfreeman> Hi everyone, can you tell me if there are any Ubuntu slideshows, logos etc that is available for download? I need some for a presentation that I'm about to do..
[05:59] <kwwii> but I think that by hiring me there is a long term plan to fix things
[05:59] <kwwii> troy_s: right
[06:00] <kwwii> troy_s: basically I get to start at the very bottom and build everything up again
[06:00] <troy_s> kwwii:  And with a distribution such as Ubuntu, we can possibly really 'shape' interface considerations in much the same way that Novell was trying to do with little bits like SLAB etc.
[06:00] <kwwii> cryingfreeman: check the wiki
[06:00] <lizardking> cryingfreeman: : Do you view the Impress OpenOffice ubuntu template or examples?
[06:00] <troy_s> kwwii:  Problem with 'building up' is that we are still stuck with sabdfl's fundamental direction, which is haphazard to say the least.
[06:01] <troy_s> cryingfreeman do a search for DIY marketing on the wiki
[06:01] <kwwii> troy_s: as I have some experience with Novell I must say that all that work is done in a closed room by 3 people
[06:01] <troy_s> kwwii:  Which reminds me
[06:01] <lizardking> kwwii: : It's not true open development the Novell's one, in my opinion
[06:01] <troy_s> kwwii:  Can you (as a rather higher priority because I have responded to at least 20 irc and 30 email requests) attempt to get the source svg files into the bzr repos for who's ubuntu logo?
[06:02] <kwwii> troy_s: oh, I can see lots of places where things can go wrong, and I know that it will be very tricky to work this out right
[06:02] <cryingfreeman> lizardking: Didn't know there were any. :)
[06:02] <kwwii> as even sabdfl doesn't completely understand the subject
[06:02] <troy_s> kwwii:  That's fine too... my issue isn't with the process that Novell implements -- it is the fact that SOMEWHERE in the line, they are ATTEMPTING to innovate.
[06:02] <cryingfreeman> Troy_s: Thanks a bundle. :) keep up the good work.
[06:02] <kwwii> troy_s: is that the one that is used in edgy? I found them on the wiki
[06:02] <lizardking> cryingfreeman: Yes they are there! and are quite cool. Btw I advice you to make slides with LateX Beamer ;)
[06:03] <kwwii> troy_s: and then redrew them myself
[06:03] <kwwii> simplifying things, etc
[06:03] <troy_s> kwwii:  Obviously the 'Novell paradigm' leaves at least as much to desire as our own regarding process ;)
[06:03] <troy_s> kwwii:  The source files SHOULD be in the source repository on bzr
[06:03] <troy_s> as it is the 'sources'
[06:03] <troy_s> with me"/
[06:03] <troy_s> ?
[06:03] <kwwii> ahhh, yeah, true
[06:03] <troy_s> (yet another baby step to 'art and design' getting its shit together.  ;) )
[06:03] <kwwii> hehe, yeah
[06:03] <troy_s> we shouldn't need to crawl the wiki to get instant sources
[06:04] <troy_s> hell -- that is what bzr is for :)
[06:04] <kwwii> yepp, very true
[06:04] <lizardking> folks I have to go studying...see U soon ok?
[06:04] <kwwii> lizardking: see you soon
[06:04] <kwwii> troy_s: yeah, it took we quite a while to find the stuff I need
[06:04] <troy_s> further, keeping up to date is far easier... (and dare I say with SVGs diff might provide detailed changes in the actual filestructure which is rather interesting)
[06:04] <kwwii> and I still haven't found everything
[06:04] <troy_s> kwwii:  So when you push your package, put the sources in there and simply exclude them from the build package
[06:04] <troy_s> follow me?
[06:04] <lizardking> Information Retrieval wants me :(.. havea nice day! bye
[06:05] <kwwii> troy_s: yepp, I will do that
[06:05] <troy_s> It also allows us to utilize powerful applications like imagemagick or other cmd line tools to 'break' images apart from their sources -- saving
[06:05] <kwwii> Information Retrieval sounds like a part of the CIA
[06:05] <troy_s> painful graphical resolution changes etc.
[06:05] <troy_s> LOL
[06:05] <troy_s> lizardking: bye friend.
[06:05] <kwwii> ok, my wife and kid are waiting on me to go to dinner
[06:05] <kwwii> bbl
[06:05] <troy_s> see ya kwwii
[06:45] <alefteris> troy_s, is there any way to remove my branch? netowork connection faild and the push was not finished.. :(
[06:45] <troy_s> alefteris: just re-push
[06:46] <troy_s> alefteris: To push
[06:46] <troy_s> you will need to follow the instructions in wiki.ubuntu.com/Bzr
[06:46] <troy_s> it will step you through publishing your ssh key
[06:46] <troy_s> (not difficult)
[06:46] <alefteris> its gives me an error..
[06:46] <alefteris> bzr: ERROR: File exists: u'/~alefteris/feisty-gdm-themes/ubuntu.bug70829': mkdir failed: unable to mkdir
[06:47] <troy_s> eek
[06:47] <troy_s> yes...
[06:47] <troy_s> you aren't choosing a good branch to push to
[06:47] <troy_s> A) Have you published your SSH key?
[06:47] <alefteris> yes
[06:47] <troy_s> B) If you have, you should include the product and push to your local spot on the Bazaar server.
[06:47] <troy_s> for example:
[06:49] <troy_s> bzr push<EMAIL_ADDRESS>[06:50] <troy_s> or something like that
[06:50] <troy_s> note
[06:50] <troy_s> alefteris: the 'alefteris' is your Launchpad identity string.
[06:50] <troy_s> i just used alefteris as an example
[06:50] <troy_s> alefteris: Ok?
[06:51] <alefteris> ok i show the .bug00 naming in one of the documents you told me to look, thats why i used it
[06:51] <troy_s> sure...
[06:51] <troy_s> that's fine too
[06:51] <troy_s> but note the syntax
[06:51] <troy_s> what is your lp identity?
[06:51] <alefteris> alefteris
[06:52] <troy_s> ok so
[06:52] <troy_s> bzr push<EMAIL_ADDRESS>[06:52] <troy_s> better?
[06:52] <troy_s> ;)
[06:52] <troy_s> note that you could push to ~alefteris/whateveryouwant
[06:53] <troy_s> but if you include the feisty-gdm-themes in there, i think it will automatically be crosslinked from the feisty 'other branches' page.
[06:53] <troy_s> follow me?
[06:53] <alefteris> yes
[06:54] <alefteris> ok but what happens with the .bug branch that failed? it apears in https://code.launchpad.net/feisty-gdm-themes/+branches. Can i remove it?
[06:56] <troy_s> erm let me look
[06:57] <troy_s> alefteris: on a side note, what did you generate your edgy vm vmplayer vmx file with?
[06:57] <troy_s> https://code.launchpad.net/~alefteris/+branch/feisty-gdm-themes/ubuntu.bug70829
[06:57] <alefteris> from here: http://www.easyvmx.com/
[06:57] <troy_s> try heading there
[06:57] <troy_s> and
[06:57] <troy_s> marking the branch as abandoned
[06:57] <troy_s> see if that works.
[06:57] <troy_s> let me see if there is another option
[06:58] <troy_s> (delete functionality is missing from bzr as of now -- it will be added soon hopefully -- until then abandoned is all you can do)
[06:58] <troy_s> try marking it as abandoned and it SHOULD be removed from branch listings.
[07:02] <alefteris> troy_s, what's this warning in the brarch webpage about? Launchpad could not mirror this branch at 2007-02-06 20:00:09 EET.  The error was: Not a branch: /srv/sm-ng/push-branches/00/00/0b/00/.bzr/branch/
[07:27] <troy_s> yeah it means you didn't finish the push
[07:27] <troy_s> as in it doesn't exist
[07:27] <troy_s> so simply push something empty to it for a success
[07:27] <troy_s> if you can
[08:12] <troy_s> alefteris: did you get it to work ok?
[08:14] <alefteris> troy_s, yeah, the warning message is gone now :)
[08:15] <alefteris> very easy way to fix bugs :)
[08:17] <troy_s> woo!
[08:17] <troy_s> bzr is great, but still has some 'features' :)
[08:17] <troy_s> the folks in #bzr are MORE than helpful.
[08:19] <alefteris> but still im not sure how can someone can test the changes that he makes in his bzr branch
[08:19] <alefteris> you cant build a package this way..
[08:19] <alefteris> i think..
[08:20] <troy_s> alefteris: The build functions
[08:20] <troy_s> are written by Daniel
[08:21] <troy_s> kwwii and dholbach have been reworking the artwork build process to make it better
[08:21] <troy_s> that said, for now, it will build if you don't add any files -- changing existing files should still build properly.
[08:21] <troy_s> standard build procedures are cd DIRECTORY
[08:21] <troy_s> ./configure
[08:21] <troy_s> ./make
[08:22] <troy_s> erm
[08:22] <troy_s> for debian it is checkinstall or whatever the hell command.
[08:22] <troy_s> anyways, that will build a package and install it via dpkg
[08:22] <troy_s> then you can test it.
[08:22] <troy_s> if you know how to test gdms without packages, just test the code and you can skip 'building' the damn thing
[08:24] <alefteris> troy_s, it would help on this was added to the wiki page..
[08:24] <alefteris> i mean a section about testing before pushing the changes
[08:25] <troy_s> alefteris: I would add something, but it is still up in the air.
[08:25] <troy_s> Hell I had to fight like a bugger to try and get the artwork team to start using bzr...
[08:26] <troy_s> at least now, it is progressing.
[08:26] <troy_s> alefteris: the more you use it, the more you can help others.
[08:26] <troy_s> alefteris: Build instructions are pretty simple... let me see if I can find an archived email.
[08:28] <troy_s> debuild -us -uc && sudo debi
[08:28] <troy_s> alefteris: That is for CURRENT build system mechanics (automake hell)
[08:28] <troy_s> the new system will use python setup I believe
[08:30] <alefteris> oh its the same way that i used to build from the package sources
[08:30] <troy_s> alefteris: But yes... you should test them before you push them.
[08:30] <troy_s> yes.
[08:30] <troy_s> the difference with that command
[08:30] <troy_s> is that you get a package that gets installed so you can remove it.
[08:30] <troy_s> as opposed to dealing with the nightmare of tracing files


[03:58] <tomreyn> pfft! :-P
[03:59] <Bashing-om> !cookie | tomreyn
[03:59] <tomreyn> doctor says no
[03:59] <Bashing-om> Me also - no sugar :(
[04:00] <tomreyn> pun on "computer says no" intended.
[04:01] <tomreyn> i don't rmemeber and don't see any indication of me working on this bug though
[04:02] <Bashing-om> tomreyn: I was peeking over you shoulder when you provided the solution :D
[04:02] <tomreyn> oh ok :)
[07:14] <lordievader> Good morning
[07:36] <ducasse> good morning
[10:55] <lotuspsychje> good noon
[10:56] <jeremy31> 4 minutes early
[10:56] <lotuspsychje> hey jeremy31
[10:56] <jeremy31> hi
[11:27] <lotuspsychje> !info linux-image-generic bionic
[11:28] <lotuspsychje> !info linux-image-generic-hwe-18.04


[00:12] <loppy2> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[00:39] <nkk71> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[01:41] <pinPoint2> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[01:41] <pinPoint2> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[01:41] <pinPoint2> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
[01:54] <chaoscon7> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[02:22] <cheapie17> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[02:22] <cheapie17> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[02:37] <Compu> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[03:03] <JoeK28> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[03:15] <nemesys> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[03:33] <PuppyKun0> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[03:39] <ollien> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[03:49] <nyuszika7h5> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[03:58] <NeddySeagoon21> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[04:13] <Namarrgon0> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[04:13] <Namarrgon0> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[04:13] <Namarrgon0> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
[04:50] <MetaNova27> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[04:55] <RussellB289> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[05:35] <PlasmaStar28> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[06:31] <Shrooms28> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[07:02] <basic`29> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[07:13] <ilbelkyr22> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[07:14] <Cisien9> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[07:35] <kek918> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[08:23] <Chords> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[08:23] <Chords> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[08:41] <iownall5557> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[09:07] <purrdeta26> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[09:07] <purrdeta26> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[09:07] <purrdeta26> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
[09:26] <eido1on> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[09:43] <Omnious> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[10:04] <Frogging10114> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[10:09] <Bock> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[11:47] <matlock> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[11:47] <matlock> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[11:47] <matlock> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
[11:47] <matlock> A fascinating blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
[11:53] <Hink> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[11:57] <RustyJ14> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[11:57] <weq21> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[11:57] <LuK133722> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[12:05] <Minkar> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[12:10] <davidebeatrici16> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[12:30] <SWAT25> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[12:55] <elenah26> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[12:55] <elenah26> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[12:55] <elenah26> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
[12:55] <hsiktas24> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[13:18] <l4z4i> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[13:34] <vans21> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[13:36] <israfel> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[14:14] <hggdh18> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[14:39] <arza0> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[14:57] <Sheraf5> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[14:59] <joycepao> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[14:59] <joycepao> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[15:25] <quicksilver10> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[15:58] <LooCfur> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[15:58] <LooCfur> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[16:09] <Olipro29> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[16:22] <Nick`> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[17:14] <eNbass14> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/


[07:00] <mup> PR snapd#11971 opened: daemon,overlord/servicestate: followup changes from PR #11960 to snap logs <Created by Meulengracht> <https://github.com/snapcore/snapd/pull/11971>
[07:10] <mup> PR snapd#11972 opened: cmd/snap: fix visual representation of 'AxB%' cpu quota modifier <Simple 😃> <quota> <Created by Meulengracht> <https://github.com/snapcore/snapd/pull/11972>
[10:30] <mup> PR snapd#11973 opened: update-copyright.sh: add tool to update copyright year <Simple 😃> <Skip spread> <Created by mardy> <https://github.com/snapcore/snapd/pull/11973>
[12:06] <mup> PR snapd#11969 closed: many: expose and support provenance from snap.yaml metadata <snap-revision-delegation> <Created by pedronis> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/11969>
[14:01] <mup> PR snapd#11974 opened: snap-bootstrap: changes to be ableo to boot classic rootfs <Created by alfonsosanchezbeato> <https://github.com/snapcore/snapd/pull/11974>
[14:36] <mup> PR snapd#11975 opened: tests: improve 'ignore-running' spread test <Simple 😃> <Created by MiguelPires> <https://github.com/snapcore/snapd/pull/11975>
[14:56] <mup> PR snapd#11972 closed: cmd/snap: fix visual representation of 'AxB%' cpu quota modifier <Simple 😃> <quota> <Created by Meulengracht> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/11972>
[16:22] <mup> PR snapd#11976 opened: sandbox/cgroup: ignore container slices when looking for snap pids <Bug> <Created by MiguelPires> <https://github.com/snapcore/snapd/pull/11976>
[16:37] <mup> PR snapd#11971 closed: daemon,overlord/servicestate: followup changes from PR #11960 to snap logs <Created by Meulengracht> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/11971>
[18:37] <mup> PR snapd#11977 opened: many: preparations for revision authority cross checks including device scope <Created by pedronis> <https://github.com/snapcore/snapd/pull/11977>


[03:41] <micahg> OvenWerks: if ardour from Debian experimental builds (2.8.16), are there any objections to syncing it?  we currently have 2.8.14 but it fails to build even with a boost patch
[03:53] <micahg> OvenWerks: nevermind, still fails
[05:13] <OvenWerks> micahg: we would really like ardour 3.* synced. Is this a problem with general ubuntu package upheaval?
[05:16] <OvenWerks> I am thinking it almost would have made sense to skip a release... I can see why the push for R.R.
[05:23] <OvenWerks> zequence: wow, there is a 3.10 lwolatencey kernel out.
[05:33] <micahg> OvenWerks: is it packaged?
[05:36] <micahg> OvenWerks: if zequence can get it sponsored into Debian, I'll be happy to sync it
[05:59] <zequence> micahg: It still needs a little bit of work
[06:00] <micahg> you've got about a month until feature freeze :)
[06:01] <zequence> I won't have any time until after 30th, but I've been meaning to do some work on it
[06:05] <zequence> OvenWerks: apw, on the kernel team is going to do one or a couple of updates to -lowlatency, and then hand it over to me
[17:38] <ttoine> zequence, I finally found time to make the "boutique"
[19:23] <princeraven> Hello Ubuntu Studio Developers :)
[19:24] <princeraven> Is it the right way to help you with developing Ubuntu Studio?
[19:25] <princeraven> I'm new to irc :D


[00:09] <Sarvatt> darn, it might have been good to mention somewhere like the changelog about the changes to DontZap handling with the updated xkeyboard-config bryce :D
[00:10] <Sarvatt> should I add it to the wiki maybe for the release notes?
[00:12] <Sarvatt> just having DontZap in xorg.conf isnt good enough to enable it anymore, need to setxkbmap -option terminate:ctrl_alt_bksp (you can map it to other things now as well and enable/disable in userspace)
[00:12] <bryce> Sarvatt: erf forgot about that
[00:12] <bryce> Sarvatt: yeah definitely need to get that documented
[00:13] <bryce> in fact I wonder if we ought to transition people... check if it is set in xorg.conf and then turn the option on for people
[00:13] <bryce> hrm
[00:17] <Sarvatt> thats a really good idea
[00:29] <james_w> we should make the dontzap package do the right thing as well
[01:03] <Sarvatt> its a checkbox option in the keyboard layout options now, would we even need the dontzap package anymore?
[01:04] <Sarvatt> "Key sequence to kill the X server"
[01:14] <Sarvatt> sent tseliot an email with a heads up about it getting updated in karmic today
[02:13] <bryce> Sarvatt: thanks
[02:14] <bryce> yeah the dontzap package becomes redundant
[02:14] <bryce> but it may still be of benefit in some cases
[02:14] <bryce> good to email alberto, he can take a look and decide.
[03:13] <hyperair> Sarvatt: i fell asleep waiting for fsck to finish (god knows why it triggered, i restarted it properly damnit! and i just fscked less than a frigging day ago! stupid ext4 >=( ), but anyway  the stuff you told me to add to modules resulted in the black screen occurring *before* i could even type in my cryptsetup password
[03:13] <hyperair> cryptroot password i mean
[03:13] <hyperair> so i had to type it in blindly
[03:13] <hyperair> heh
[03:13] <Sarvatt> ah, how about booting with video=fbcon?
[03:18] <hyperair> Sarvatt: hmm i'll try that. kernel parameter right
[03:18] <Sarvatt> probably something to do with the whole cryptloop stuff :D
[03:18] <hyperair> Sarvatt: it doesn't blank out if usplash isn't on, by the way.
[03:18] <hyperair> if i boot without the 'splash' parameter, it doesn't blank out
[03:21] <Sarvatt> so I guess KMS has a problem with the cryptloop display stuff...
[03:23] <hyperair> Sarvatt: it does?
[03:23] <Sarvatt> apparently? its blacking out and not working under a real drmfb?
[03:23] <hyperair> Sarvatt: i don't really think so, because if i don't have that, the screen blanks out anyway, but *after* the cryptloop display stuff
[03:24] <Sarvatt> because you arent using the drmfb until later
[03:24] <hyperair> well yes, but how would KMS have issues with cryptloop?
[03:24] <hyperair> it doesn't exactly attempt to display anything, right?
[03:25] <hyperair> the cryptloop prompt is rendered by usplash
[03:25] <Sarvatt> doesnt it hook into usplash for the prompt?
[03:25] <Sarvatt> yeah
[03:25] <hyperair> as in, it talks to usplash
[03:25] <hyperair> hmm
[03:25] <hyperair> so you're saying that the usplash prompt causes problems with it?
[03:25] <hyperair> but why would it cause problems if it happened before i915 kicked in?
[03:26] <Sarvatt> because you dont use the drm fb until alot later normally (18 seconds in in your dmesg)
[03:27] <hyperair> but there aren't any further cryptloop prompts!
[03:27] <Sarvatt> just using intelfb or uvesafb or whatever it uses until then and it blacks out
[03:27] <hyperair> hmmm
[03:27] <hyperair> what does usplash use exactly?
[03:31] <Sarvatt> actually, looking at my bootcharts
[03:31] <Sarvatt> it looks like usplash in KMS just plain shuts off right after it starts and leaves the picture up
[03:32] <hyperair> what?
[03:32] <hyperair> O_O
[03:32] <Sarvatt> when i915 is built in and i have a KMS console up at 3 seconds in
[03:32] <Sarvatt> i should force a fsck and see if it shows the fsck stuff :D
[03:32] <hyperair> how bizarre O_o
[03:32] <hyperair> hmm
[03:32]  * hyperair is beginning to really hate fsck
[03:32] <hyperair> 20 minutes for one round
[03:32] <hyperair> ugh
[03:32] <hyperair> what a pain
[03:33] <Sarvatt> my bootcharts without KMS have usplash going for a long time, with kms it stops 2 seconds after it starts and i dont get progress bars or anything
[03:33] <hyperair> i don't even know why my stupid /home loves to trigger fsck
[03:33] <hyperair> i se
[03:33] <hyperair> no progress bars eh
[03:33] <hyperair> then imo we should get usplash fixed before turning on KMS by default
[03:33] <hyperair> or remove it completely.
[03:34] <hyperair> no actually newbies have a tendency to think that black screen with scrolling text = spoilt computer
[03:34] <Sarvatt> probably the cryptloop :D
[03:34] <hyperair> meh
[03:34] <Sarvatt> (reason for the fscks i mean)
[03:35] <hyperair> no, i don't think so
[03:35] <hyperair> it never had an issue before this
[03:35] <hyperair> come to think of it, it never managed to unmount root because it was busy at the end of the shutdown cycle
[03:37] <hyperair> but cryptloop doesn't cache stuff does it
[03:37] <hyperair> it's pretty much synchronous in that all operations on it are written straight to the disk, unless i'm mistaken
[03:37] <Sarvatt> ext4 is marked needs fsck until its unmounted..
[03:38] <Sarvatt> clears the flag when its unmounted cleanly
[03:39] <hyperair> which means /home is never unmounted cleanly
[03:39]  * hyperair facepalms
[03:39] <hyperair> but hey i restarted it normally, surely the kernel should know to unmount all filesystems before shutting down *properly*?!
[03:40] <Sarvatt> shutdown script trying to unmount / before your cryptloop maybe?
[03:40] <hyperair> er doesn't it have to unmount / before cryptloop?
[03:40] <hyperair> either way if / needs fscking, i don't really care
[03:40] <hyperair> that takes at most 5 minutes
[03:41] <hyperair> i'm annoyed if /home needs fscking
[03:41] <hyperair> that takes at least 20 minutes
[03:41] <hyperair> ugh
[03:41] <Sarvatt> your cryptloop isnt somewhere on /?
[03:41] <hyperair> oh yeah it is
[03:41] <hyperair> it's on /dev/mapper
[03:41] <hyperair> /something
[03:49] <Sarvatt> i mean it might be trying to unmount the actual loop device before the file system inside is unmounted so that needs fsck, i had a similar problem with the shutdown scripts doing the kill wifi script before umountnfs by default..
[03:50] <hyperair> no, you can't do something of that sort. cryptsetup does not allow you to do anything to the underlying block device before unmounting it
[03:50] <hyperair> and the LVM on top of cryptsetup won't allow that eitehr
[03:51] <Sarvatt> can you remove the loop module with it mounted?
[03:51] <hyperair> no i don't think you can
[03:51] <hyperair> it'll complain that it's "in use"
[03:51] <hyperair> also, some rounds of REISUB don't trigger an fsck, but some do
[03:51] <Sarvatt> how about the crypto module?
[03:52] <hyperair> hmm
[03:52] <hyperair> i think it would also complain about still being used
[03:52] <hyperair> lemme try
[03:53] <hyperair> actually come to think of it... what's the name of the module? O_o
[03:53] <hyperair> ah nevermind found it
[03:53] <Sarvatt> maybe add a sync to the shutdown script?
[03:53] <hyperair> module in use
[03:53] <hyperair> where is the shutdown script? O_o
[06:48] <tjaalton> xserver master switched back to zapping by default, so that the shortcut can be configured with xkeyboard-config 1.6
[06:49] <tjaalton> I'm not sure there's much to migrate, other than documenting it
[06:49] <tjaalton> note that there's no shortcut defined by default
[06:49] <tjaalton> so it's effectively still off
[08:35] <tseliot> bryce: are you still there?
[08:43] <tseliot> nm
[15:59] <Ng> bah, rebooted this morning for a new kernel and my laptop wouldn't come out of dpms-off after lunch, had to do sysrq stuff
[16:41] <hyperair> Ng: that sounds fun. did you by any chance get to fsck in the dark later?
[16:41] <Ng> hyperair: heh, no, ext4 seemed to be happy just recovering things
[16:42] <hyperair> Ng: good for you. i had to sit through a 20 minute long fsck, faced with a black screen, because usplash doesn't like KMS.
[16:42] <Ng> ohh, there's an oops in my logs
[16:42] <hyperair> or KMS doesn't like usplash
[16:42] <hyperair> or something
[16:42] <hyperair> yeah there's always an oops when that happens
[16:42] <Ng> it's 915 related
[16:42] <hyperair> i couldn't capture it though, for some reason dmesg > dmesg.txt gave me a bloody blank file
[16:42] <Ng> which I guess isn't surprising
[16:43] <Ng> wow, multiple oopses
[16:43] <hyperair> heh
[16:43] <superm1> hyperair, dmesg | tee dmesg.txt instead maybe then
[16:43] <Ng> I think they're all the same, some hung_task kernel thing
[16:43] <hyperair> superm1: i don't see how that would be any better
[16:43] <superm1> well if plain ol 'dmesg' doesn't work, then i guess it wouldn't be any better
[16:44] <hyperair> heh
[16:44] <Ng> do we want bugs from i915 on the kernel?
[16:44] <Ng> (I would assume so)
[16:46] <hyperair> i would think so too
[16:46] <Ng> huh, the backtrace looks a lot like bug #384865 which is 9.04
[16:46]  * Ng facepalms, it's 9.10
[16:48] <Ng> I guess this should be upstreamed
[16:57] <hyperair> heh
[17:01] <Ng> upstreamed and linked
[17:01] <hyperair> woohoo
[17:01] <Ng> bit weird having it in the kernel package in ubuntu and the intel video driver in bugs.freedesktop.org, but whatever
[18:10] <Duke`> Sarvatt: now intel KMS on jaunty works without xorg.conf file!
[18:17] <hyperair> since when did KMS require a xorg.conf?
[18:18] <hyperair> wasn't it some kernel module option?
[18:19] <crevette> hey a
[18:21] <Duke`> hyperair: previously, xorg server was trying to load i810 module instead of intel driver and failed... so I had to force manually the intel driver in a simple xorg.conf file
[18:21] <hyperair> i see
[18:21] <hyperair> great then =p
[18:23] <jcristau> Duke`: sounds unrelated to kms..
[18:23] <jcristau> also doesn't sound like a problem, but meh
[18:23] <crevette> I've a problem with KMS, I boot with grub i915.modeset=1 ,I can see the splash screen but no gdm
[18:23] <hyperair> that sounds like the opposite of what i get
[18:23] <tjaalton> bryce: has the nouveau testing been with kms? our snapshot of the driver is quite old too
[18:23] <Duke`> jcristau: yeah was strange, but it did only when I enabled KMS
[18:23] <hyperair> i get gdm but i don't get the usplash
[18:24] <jcristau> Duke`: loading i810 was not the problem then.  loading fbdev might have been.
[18:24] <crevette> my hardware is described at https://wiki.ubuntu.com/X/KernelModeSetting/ (bmillemathias)
[18:24] <Duke`> jcristau: ah yes, that was probably that
[18:25] <Duke`> http://pastebin.com/m20b737fc
[18:25] <crevette> my Xorg is https://wiki.ubuntu.com/X/KernelModeSetting/
[18:25] <crevette> my Xorg is http://bmm80.free.fr/misc/X/Xorg.0.log rather
[18:35] <bryce> (sorry, was in #ubuntu-desktop meeting)
[18:36] <bryce> tjaalton: not going so good, so far.  Getting black screens on 2 cards, and failsafe mode on the third.
[18:36] <crevette> hey no problem bryce, I was supposed you were in meeting, irc is low latency by nature
[18:36] <crevette> :)
[18:36] <bryce> Ng: for bug reports against the kernel that involve X issues such as KMS, etc. what we're doing is tagging them 'xorg-needs-kernel-fix'
[18:37] <bryce> Ng: this let's us find the X/kernel bugs more easily in the huge kernel bug pile
[18:37] <Ng> aha
[18:38] <Ng> bryce: thanks, added the tag
[18:42] <crevette> I didn't opened a bug yet, what should I attach as files to the bug (I already have Xorg.0.log)
[18:42] <crevette> and to which component should I the bug against? (xorg, intel driver, kernel?)
[18:52] <Sarvatt> thats an xorg-server problem crevette
[18:52] <Sarvatt> the exact problem just fixed for Duke` :D
[18:53] <Ng> now I just need to find someone to bribe/pester into fixing the problem :D
[18:53] <tjaalton> bryce: but is it with kms? would it be different without?
[18:57] <crevette> Sarvatt, what is the problem I arrived a bit late ... :)
[18:57] <Sarvatt> http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=daf26a14473563aa7368c93246f483b11e009d23
[18:58] <crevette> ah yeah, it seems to be that
[18:59] <crevette> because I see also the failsafe thingy trying to launch X just after and failing also
[18:59] <crevette> this patch was not sent upstreamN
[18:59] <jcristau> the patch is a hack
[19:01] <bryce> tjaalton: yeah this testing was with apw's kms kernel; I need to re-test with the stock kernel and !kms, and also probably should pull newer -nouveau bits
[19:01] <bryce> tjaalton: but so far the problems are making me lose some confidence on how far we can get with -nouveau this cycle
[19:04] <Sarvatt> well I got it working fully including 3d via gallium, some changes were needed. you need to drop the dependancy on linux-nouveau-source in the nouveau ddx when you use the KMS kernel, and the KMS kernel doesnt work in non KMS mode for me
[19:07] <Sarvatt> bryce: were you booting with nouveau.modeset=1 on the grub command line?
[19:07] <bryce> Sarvatt: no, I assumed the kernel was set up with that by default
[19:08] <Sarvatt> if i didnt use that it would try to boot in non KMS which wasnt working at all, dmesg flooded with errors and a black screen when x starts
[19:09] <bryce> ah, perhaps that's what I'm seeing ... trying
[19:09] <crevette> Sarvatt, so the fix will be available soon
[19:09] <tjaalton> bryce: ok.. I should try with my 8600GT
[19:11] <bryce> [    0.000000] Unknown boot option `nouveau.modeset=1': ignoring
[19:11] <Sarvatt> did you drop the nouveau kernel source from the ddx install bryce?
[19:12] <bryce> this is with 2.6.30-8-generic #10~kms2-Ubuntu
[19:12] <Sarvatt> because if you built the kernel module with dkms just installing it normally you'll get the non KMS compatable one
[19:14] <Sarvatt> do you see symbol version mismatch errors in dmesg? you built an external module thats overriding the KMS compatable one if so
[19:14] <crevette> is the "i915.modeset=1" boot option supported in the karmic kernel, because I have the same error message than bryce
[19:14] <Sarvatt> i915 isnt in the initrd by default so it gives the error trying to pass it early
[19:15] <jcristau> bryce: that message is expected
[19:15] <jcristau> bryce: just means i915 is not built-in
[19:15] <bryce> how about "[   25.697743] nouveau: Unknown parameter `modeset'" which appears later?
[19:15] <tjaalton> or nouveau, in this case
[19:16] <jcristau> tjaalton: yeah, that :)
[19:16] <tjaalton> bryce: maybe it's the dkms version Sarvatt mentioned
[19:16] <bryce> there are no messages in dmesg about mismatched versions
[19:17] <bryce> fwiw, I didn't build this kernel, this is from apw's package.
[19:18] <Sarvatt> did you install xserver-xorg-video-nouveau? because if you did it overrided the nouveau kernel module that has KMS support with the one from nouveau-kernel-source
[19:19] <bryce> ah, that could be; yes I updated -nouveau after installing the kernel.  Will try redoing that
[19:19] <Sarvatt> unless you rebuilt xserver-xorg-video-nouveau without the linux-nouveau-source dependancy dropped
[19:19] <Sarvatt> err with it dropped I mean
[19:20] <Sarvatt> i'll make a ppa with everything right now
[19:20] <tjaalton> just force purge -source, and remove the module it built
[19:23] <bryce> nouveau-kernel-source:
[19:23] <bryce>   Installed: 0.0.11+git20090515-0ubuntu1
[19:23] <tjaalton> yep, that would suggest that it overrides the module from the kernel
[19:23] <bryce> tjaalton: but if I try purging it, it also tries to remove -nouveau itself
[19:23] <bryce> The following packages will be REMOVED:
[19:23] <bryce>   nouveau-kernel-source* xserver-xorg-video-nouveau*
[19:24] <bryce> I'll just try reinstalling the kernel over the top first
[19:24] <tjaalton> that's why I said force purge :)
[19:24] <tjaalton> or use what Sarvatt will provide
[19:24] <tjaalton> or build -nouveau without the dep
[19:25] <Sarvatt> it'll probably take me about 30 minutes to get everything together, will be here though https://edge.launchpad.net/~sarvatt/+archive/nouveau
[19:26] <bryce> tjaalton: that was with apt-get purge -f nouveau-kernel-source
[19:26] <tjaalton> dpkg --purge --force-depends nouveau-kernel-source?
[19:29] <bryce>  * Running DKMS auto installation service for kernel 2.6.30-9-generic
[19:29] <bryce>  *  nouveau (0.0.11+git20090515)...                                                                                nouveau (0.0.11+git20090515): Installing module.
[19:29] <bryce> ................
[19:30] <tjaalton> heh
[19:31] <tjaalton> dropping the dependency should work
[19:31] <bryce> although I notice from the changelog, that nouveau.modeset=1 is probably unnecessary - * NOUVEAU: Pull in the Nouveau driver and enable KMS by default.
[19:34] <Sarvatt> ok everything uploaded to the PPA, just gotta wait to be built
[19:34] <bryce> heya gang65
[19:35] <gang65> hello bryce
[19:36] <bryce> tjaalton: http://pastebin.ubuntu.com/197228/
[19:39] <Sarvatt> https://edge.launchpad.net/~sarvatt/+archive/nouveau
[19:39] <tjaalton> bryce: ok, and what happens then on boot?
[19:41] <bryce> tjaalton: [   22.776767] nouveau 0000:01:00.0: display fifo hung :(
[19:41] <bryce> heh, smilies in dmesg
[19:41] <jcristau> progress!
[19:41] <jcristau> :)
[19:41] <tjaalton> hehe
[19:41] <bryce> I had a brownish flash before it went black this time
[19:41] <Sarvatt> yeah thats without nouveau.modeset=1, i actually add options nouveau modeset=1 to /etc/modprobe.d/nouveau.conf as well
[19:42] <bryce> alright, from the changelog it sounds like that's not necessary, but easy enough to test
[19:43] <bryce> SWEET
[19:43] <bryce> console switched to the tiny fonts
[19:43] <bryce> wow, login screen is fucked though
[19:43] <Sarvatt> oh yeah, you also have to add nouveau to xorg.conf
[19:43] <tjaalton> yeah it tries to use nv
[19:44] <bryce> mm, think I did that already, lemme check
[19:44] <bryce>         Driver  "nouveau"
[19:44] <bryce>         Option  "Randr12" "on"
[19:44] <bryce> yep
[19:44] <Sarvatt> its possible whatever driver you're using doesnt work with the kernel nouveau though, they bumped the api around 0605, the one in my PPA should work
[19:45] <tjaalton> releases ftw
[19:45] <bryce> ok, well it's a *very* dark screen, but i could make out gdm's login box, so did my credentials and it started the desktop session, however the screen is fully blank (backlight is on, screen is kind of off-black)
[19:48] <Sarvatt> oops, silly me, uploaded the ddx before the drm was finished building on x64 and lpia
[19:48] <bryce> [   23.372708] nouveau 0000:01:00.0: Unhandled PFIFO_INTR - 0x00000010
[19:50] <Sarvatt> i386 is fine though, dont know if you're on x64 or not
[19:51] <bryce> murphy would have it no other way ;-)
[19:51] <Sarvatt> rebuilding amd64 now
[19:51] <Sarvatt> i should make a livecd for this :D
[19:51] <bryce> well, I need food anyway, so hopefully the amd64 stuff will be there when I get back
[19:57] <Sarvatt> amd64 or i386 for the livecd?
[19:59] <Sarvatt> well getting i386 because i dont think the script can handle building a amd64 one on my i386 machine i'm doing it on right now :D
[20:00] <Sarvatt> so i've gotta add nouveau to xorg.conf, and i'll echo options nouveau modeset=1 to /etc/modprobe.d/nouveau.conf, sure i'm forgetting a step...
[20:02] <Sarvatt> hmm i force it to EXA and use option noaccel false too on my nouveau kms machine
[20:02] <Sarvatt> but i think thats why i have problems with nouveau gallium
[20:36] <Sarvatt> ahh heck, Recommends: still pulls in nouveau-kernel-source, reuploading another with it dropped completely
[20:36] <Sarvatt> glad i tried it out before building the livecd :D
[20:48] <Sarvatt> yeah i have to pass nouveau.modeset=1 to grub every time or it wont boot, even with options nouveau modeset=1 in /etc/modprobe.d/nouveau.conf
[20:48] <Sarvatt> there an easy way to make that the default option on a live cd?
[20:51] <tjaalton> not sure
[20:55] <Sarvatt> ok heres logs of everything working http://sarvatt.com/downloads/nouveau-kms.txt
[20:56] <tjaalton> you've got gallium there too?
[20:59] <Sarvatt> yep
[20:59] <Sarvatt> not packaged, built it locally
[20:59] <tjaalton> ok
[21:00] <Sarvatt> used ./configure --enable-glx-tls --disable-egl --disable-asm --with-dri-drivers= --enable-gallium-nouveau --disable-gallium-intel --disable-gallium-radeon --with-state-trackers=glx,dri --with-demos=xdemos,demos,trivial,tests
[21:01] <Sarvatt> then I use LD_LIBRARY_PATH=~/source/mesa-7.6.0~git20090613.18af7c38/lib LIBGL_DRIVERS_PATH=~/source/mesa-7.6.0~git20090613.18af7c38/lib/gallium <program> to run it
[21:04] <Sarvatt> hate these darn HP bioses, i need to fix the dsdt for every single one i have
[21:06] <Sarvatt> probably should mention i cant run anything more than glxinfo with gallium :D
[21:23] <Sarvatt> ahh ok isolinux/gfxboot.cfg you can append things to the command line
[21:33] <Sarvatt> with no xorg.conf, is there any way to tell xserver to prefer the nouveau driver, or am I going to have to make the xorg.conf only work for nouveau on the livecd?
[21:39] <tjaalton> not without patching the server
[21:41] <Sarvatt> can I add multiple device sections and have it go down the list to find a working one?
[21:42] <tjaalton> hmm yes
[21:42] <tjaalton> that's what the server does, in practise
[21:45] <Sarvatt> http://sarvatt.com/downloads/xorg.conf.txt
[21:45] <Sarvatt> that look ok to you? or do i need screens too
[21:45] <tjaalton> not sure, have you tried it?
[21:49] <jcristau> Sarvatt: yeah iirc you need one Screen for each Device
[21:49] <tjaalton> try running without one, see what the logfile looks like
[21:50] <jcristau> otherwise it'll just use the first Device
[21:52] <Sarvatt> i just stepped out for a few minutes and dont have another machine handy to try it, and i'm almost done building the livecd so it'd be a shame to restart x to test it on this
[21:53] <Sarvatt> would adding screen 0 to each device work possibly?
[21:54] <Sarvatt> ahh i'm just going to add the nouveau device, if anyone wants to use it on something else they can fix it in failsafe :D
[21:57] <Sarvatt> sure is fun building the squashfs on an atom cpu, hope my battery lasts
[22:02] <Sarvatt> building it based on https://edge.launchpad.net/~sarvatt/+archive/xorg-testing so can test xserver <IP_ADDRESS> too
[22:03] <Sarvatt> need to update the xserver master hooks,because alot more builds now, just kdrive having problems
[22:11] <tjaalton> <IP_ADDRESS>?
[22:11] <tjaalton> I see no such release
[22:16] <Sarvatt> not released yet, xserver master branch
[22:16] <Sarvatt> making the liveusb now to see if it works then i'll upload it
[22:22] <tjaalton> ah, so inventing release numbers then?-)
[22:33] <Sarvatt> no thats the version it reports
[22:34] <Sarvatt> no go on the livecd, xorg.conf gets overwritten with a default one on first boot
[22:35] <Sarvatt> AC_INIT([xorg-server], <IP_ADDRESS>, [https://bugs.freedesktop.org/enter_bug.cgi?product=xorg], xorg-server)
[22:37] <tjaalton> Sarvatt: ah, ok
[22:43] <Sarvatt> cant figure out whats making it recreate a default xorg.conf, hmm
[22:46] <tjaalton> xserver-xorg.postinst
[22:46] <tjaalton> casper runs that
[22:47] <tjaalton> forgot that it's still not fixed in karmic
[22:52] <Sarvatt> hmm so if i comment the stuff from remove_conffile_prepare () { down to run ()  { out of xserver-xorg.postinst it should keep it?
[22:55] <tjaalton> maybe
[22:56] <jcristau> Sarvatt: rm xserver-xorg.postinst might be even better, for the live cd?
[22:56] <Sarvatt> even easier, will try that
[22:58] <jcristau> hrm. unless it still does something important. i'd need to check :)
[22:59] <jcristau> ah, right, it does the ln -s /usr/bin/Xorg /etc/X11/X
[22:59] <jcristau> but that probably doesn't need to be re-run on the live system
[23:01] <Sarvatt> yeah theres a link there already, phew
[23:49] <Sarvatt> ok i have a working livecd now, problem is you need to manually remove splash from the startup line. dont know if i should rebuild it with splash disabled by default or just note that :D
[23:51] <Sarvatt> ahh i can rebuild it manually without rebuilding the squashfs