[12:15] <mooey> what files does the apport retracing thing need? does it use the attached .crash file, or coredump.gz?
[12:19] <Fujitsu> mooey: It uses the new multi-attachment format.
[12:20] <mooey> Fujitsu: i'm not sure what that is. the reason i ask, if somebody attaches the .crash file to a bug and i tag it to be retraced, will it?
[12:20] <mooey> i dont know what the requirements are for retracing
[12:22] <Fujitsu> It won't be retraced, AFAIK.
[12:23] <mooey> Fujitsu: as i suspected, thanks
[12:52] <Lathiat> robertj: heh i love it when that happens
[12:53] <robertj> I thought  a big part of these new fangled journeling file systems is that they didn't require manually fscking?
[12:53] <desrt> "stuff happens"
[12:54] <desrt> a fsck is good from time to time
[12:54] <Lathiat> i really wish it gave you a few seconds to cancel it
[12:55] <desrt> or let you ^C in the middle like it used to
[12:55] <robertj> Lathiat: doesn't it happen before USB support is probed in?
[12:55] <Lathiat> classic case in point: http://www.flickr.com/photos/lathiat/364496523/
[12:55] <robertj> I seem to remember being cought by that on ppc64 a while back
[12:57] <robertj> it just seems utterly worthless to 99.99% of people
[12:58] <desrt> far better when someone gets stuck at fsck while trying to power their laptop up to give a talk
[12:58] <robertj> could it <blasphemy>be disabled by default?</blasphemy>
[12:59] <desrt> you really _should_ run it from time to time
[12:59] <Lathiat> what we need is online fscking
[12:59] <desrt> ya.  that would kick some serious ass
[12:59] <desrt> we're talking my quality of life is significantly improved
[12:59] <robertj> desrt: and I should lose 20 pounds
[01:00] <desrt> robertj; if you lose data as a result of your extra 20 pounds it's not a problem in ubuntu
[01:00] <robertj> desrt: neither is it if my HD goes toes-up
[01:00] <desrt> it has nothing to do with your HD going toes-up
[01:00] <desrt> it has to do with bugs in the filesystem code
[01:00] <desrt> "stuff happens"
[01:00] <desrt> and the journaling isn't absolutely perfect
[01:01] <desrt> from time to time i'll see "inconsistent something-or-other" when fscking an ext3 fs.... it just happens
[01:01] <desrt> i don't think it's 'cause i have bad disks or bad ram... i think the code just has some very small bugs
[01:02] <mjg59> tepsipakki: Have we lost the patch that disables XAAOffscreenPixmaps when a compositing manager is running?
[01:02] <desrt> tepsipakki; while you're looking: have you seen keithp's xcomposite bugfix that no feisty should be without?
[01:03] <desrt> ((and applies absolutely cleanly to feisty's X))
[01:03] <tepsipakki> mjg59: we had that?
[01:03] <mjg59> tepsipakki: Yeah
[01:03] <tepsipakki> desrt: no
[01:03] <desrt> let me find it for you
[01:03] <mjg59> tepsipakki: It meant compiz actually worked :)
[01:03] <tepsipakki> thanks
[01:03] <robertj> do SUSE & Fedora still fsck?
[01:04] <tepsipakki> mjg59: was it in xorg-server?
[01:04] <desrt> tepsipakki; http://lists.freedesktop.org/archives/xorg/2007-March/022668.html
[01:04] <mjg59> tepsipakki: Oh, hang on, it's still there
[01:04] <mjg59> tepsipakki: Path 120
[01:05] <mjg59> tepsipakki: It's just been dropped from series for some reason
[01:05] <tepsipakki> oh..
[01:05] <tepsipakki> let me check
[01:05] <mjg59> Seems to apply cleanly
[01:05] <ssam> is it not possible for fsck to run at shutdown?
[01:06] <robertj> also fsck is only going to run on my file server once or twice a year, where it is perhaps more important
[01:07] <robertj> whereas my laptop gets fscked once a week
[01:07] <pochu> is XAAOffscreenPixmaps the opposite to XAANoOffscreenPixmaps?
[01:08] <mjg59> Yes
[01:08] <mjg59> tepsipakki: Of course, we also seem to be missing the compiz half of that patch :)
[01:08] <tepsipakki> mjg59: yeah.. I dropped it because of the feedback I got from Michel Dnzer. Fedora still has it, so maybe we should reactivate it again, since it is generating pain for people
[01:09] <pochu> then that pach would be really cool. we have a lot of compiz bug reports saying 'compiz doesn't work' and it's just because they're missing that option in the device section
[01:09] <mjg59> tepsipakki: Yeah, it's something of a hack, but it's one that works
[01:09] <mjg59> tepsipakki: If you can merge that back in, I'll handle the compiz side
[01:10] <tepsipakki> also the dont_backfill_bg_none.patch
[01:10] <tepsipakki> sure, I have the source ready
[01:10] <mjg59> tepsipakki: Seems to still apply just fine, so it's just a matter of hitting it in series
[01:10] <desrt> tepsipakki; he has updated the patch since i last tested it.  i'm trying the latest version to make sure it still works.
[01:14] <geser> keescook: can you look at bug #96712 and bug #96723 and ACK them? thanks.
[01:15] <tepsipakki> oh, that backfill-bg -patch was already re-enabled
[01:16] <mooey> hm. is the apport retracing service working?
[01:16] <mooey> i've just tagged a few bugs and its removing the tag but not actually attaching anything to the bug report
[01:17] <geser> there are bugs with retrace info, so it should work
[01:18] <mooey> it seems to not like bug 96681, but 96691 and bug 96718. i've tried three and all three failed
[01:26] <tepsipakki> mjg59, desrt: I could upload the server without the new composite patch?
[01:28] <tepsipakki> or leave it for the morning (it's 02:27 here :) and include that patch from keithp
[01:28] <mjg59> tepsipakki: I'm easy with either
[01:28] <mjg59> I'll upload compiz tonight (assuming this works)
[01:28] <mjg59> I've done a test build of X here
[01:29] <tepsipakki> I'm positive that the patch still works :)
[01:30] <tepsipakki> hum, interesting commits in xserver master.. adjustments to the I2C timeouts
[01:32] <tepsipakki> should make the DDC probing more robust
[01:32] <mjg59> tepsipakki: Yeah, works fine here
[01:32] <tepsipakki> nice
[01:34] <Amaranth> tepsipakki: wait, this makes compiz not need XAANoOffscreenPixmaps to not suck?
[01:34] <shawarma> That's the idea. :-)
[01:34] <Amaranth> tepsipakki: I love you. Have my babies.
[01:34] <tepsipakki> Amaranth: sorry, I have two already :)
[01:34] <Amaranth> Hehe
[01:35] <Amaranth> I think we have about 20 dupes of that bug
[01:35] <tepsipakki> can you tell me the #
[01:35] <Amaranth> and beryl has already had two dupes of it filed since it made it into universe
[01:35] <Amaranth> bug 89189
[01:35] <ubotu> Malone bug 89189 in xorg "No text in save/dialog boxes" [Medium,Unconfirmed]  https://launchpad.net/bugs/89189
[01:35] <tepsipakki> ah _that_ one :)
[01:35] <tepsipakki> I'll add it to the changelog
[01:35] <Amaranth> someone will have to patch beryl too ;)
[01:35] <shawarma> Amaranth: It needs a patch in the composite manager too it seems.
[01:37] <tepsipakki> I'll just upload xorg-server_1.2.0-3ubuntu5 now so we get that fix out of the door
[01:38] <mjg59> Hm.
[01:38] <mjg59> So, why can't I trigger cube operations any more?
[01:38] <tepsipakki> mjg59: they haven't worked for me since I can remember
[01:38] <Amaranth> do you have the keybinding plugin loaded?
[01:39] <mjg59> Amaranth: Yup
[01:39] <Amaranth> that thing should provide the largedesktop feature so it conflicts with cube and plane
[01:39] <Amaranth> well, rotate and plane
[01:39] <mjg59> Hm.
[01:39] <mjg59> "largedesktop feature"?
[01:40] <Amaranth> afaik it's only purpose is making ctrl-alt-left/right work for workspaces
[01:40] <Amaranth> yeah, in compiz if two plugins provide the same "feature" it won't let you have them loaded at the time
[01:40] <mjg59> No, that doesn't seem to be it
[01:40] <tepsipakki> oh, right
[01:41] <mjg59> It's a bit awkward given that we have the "cube" checkbox in desktop-effects...
[01:41] <tepsipakki> xorg-server uploaded
[01:41] <Amaranth> mjg59: right, desktop-effects does not cope with workspaces
[01:41] <Amaranth> it needs to set number_of_desktops to 1 and hsize to 4, it assumes those are done
[01:41] <shawarma> mjg59: I assume you have just one desktop and hsize is 4?
[01:42] <Amaranth> there was someone working on a patch, was letting him do it so maybe he'd do more patches :)
[01:42] <shawarma> mjg59: there's a but about it already. 2 sec.
[01:43] <Amaranth> bug 89786
[01:43] <ubotu> Malone bug 89786 in desktop-effects "Desktop-effect does not enable cube" [Medium,In progress]  https://launchpad.net/bugs/89786
[01:43] <shawarma> right.
[01:43] <shawarma> :-)
[01:45] <mjg59> shawarma: Right, that's it
[01:46] <tepsipakki> ok, time to get some sleep, night all ->
[01:47] <shawarma> It weird, actually. I've never gotten used to multiple desktop until they were put on a cube. :-) Now I can't live without them.
[02:00] <keescook> geser: thanks for filing those, I've confirmed them and added some comments
[02:03] <Amaranth> shawarma: with a patch from the beryl folks (taken with permission) we might be able to have cube on by default
[02:03] <Burgwork> Amaranth: cube by default if it means no workspaces is a bad thing
[02:03] <Amaranth> shawarma: it maps workspaces to viewports so when you have something on workspace 2 in metacity it'll go to viewport 2 when you start compiz
[02:04] <Amaranth> Burgwork: what i just said to shawarma :)
[02:04] <Burgwork> does it deal with the task bar as well?
[02:04] <Amaranth> the task bar works fine?
[02:04] <Burgwork> I found viewports to be extremely suboptimal
[02:04] <Amaranth> oh, you mean when you right click on the window list
[02:04] <Burgwork> does the task bar only show windows on the current viewport?
[02:04] <Amaranth> oh, that, yes
[02:04] <Burgwork> basically, it needs to act and work like metacity
[02:05] <Amaranth> the only thing you lose is "Move to Workspace X" options in right click
[02:05] <Amaranth> i have a patch for that too but it breaks ABI so it needs to get into libwnck upstream first
[02:05] <Burgwork> ah
[02:06] <Amaranth> i also have a plugin to do edge resistance without wobbly
[02:06] <Amaranth> it's almost but not quite like metacity's
[02:06] <Amaranth> that's a port of a beryl plugin thought, not my doing :)
[02:07] <Amaranth> alright to use though, plugins can have whatever license they want
[02:07] <Burgwork> almost but not quite nothing like metacity :)
[02:07] <Amaranth> heh
[02:08] <Amaranth> i think the only real difference between metacity and the snap plugin when you put it in edge resistance mode is that it doesn't pull windows off without resistance after you snap them together
[02:09] <shawarma> Amaranth: Sound shiny!
[02:09] <shawarma> Amaranth: Sounds shiny, even.
[02:09] <Amaranth> it's in bug 73700 but i got scared when i tried doing a debdiff so it's just the .c file
[02:09] <ubotu> Malone bug 73700 in compiz "Lacks edge resistence" [Low,Confirmed]  https://launchpad.net/bugs/73700
[02:10] <Amaranth> i think the only "big" problem we have left is java apps
[02:11] <Amaranth> oh, and drivers sucking with Xv
[02:18] <zyga> Amaranth: what is the problem with java apps?
[02:18] <Amaranth> they show up all white when compiz is running
[02:19] <Amaranth> i think it's swing or something
[02:19] <Amaranth> i don't know the details, i don't use java apps
[02:19] <shawarma> Amaranth: Does that include applets, too?
[02:19] <zyga> Amaranth: does it affect 1.6 or just 1.5 ?
[02:19] <zyga> (java)
[02:20] <Amaranth> shawarma: i don't think so, they don't use swing do they?
[02:20] <supervillain> yay, 16 more hours had been added to the SoC deadline!
[02:20] <Amaranth> zyga: i dunno :)
[02:20] <shawarma> Amaranth: No idea. :-)
[02:20] <zyga> Amaranth: applets can use swing, many do
[02:20] <Amaranth> zyga: run compiz and test them ;)
[02:20] <zyga> Amaranth: I cannot, I'm evil now :/
[02:21] <zyga> I only use ubuntu on servers
[02:30] <mpt> aaaaaaaaaaa
[02:30] <mpt> asac, hi
[02:31] <mpt> asac, how on earth did you end up with "upstream confirmed bugs are 'In Progress' for us"? :-)
[02:34] <mpt> that's not even slightly true
[02:43] <LaserJock> mpt: makes sense to me if they're working on it
[02:48] <mpt> LaserJock, but they're not
[02:48] <LaserJock> hmm, still make some sense but I probably wouldn't have bothered
[02:49] <LaserJock> I need to work on my bug report skills, I'm kinda lazy. Things tend to go from Unconfirmed to Fix Released
[02:49] <mpt> In this particular case, no developer has done anything about the bug since it was reported nearly six years ago
[02:50] <mpt> LaserJock, that's fine, there's no need to do unnecessary virtual paperwork
[02:50] <LaserJock> well, except users get a little upset
[02:50] <LaserJock> when there's no action
[02:50] <mpt> right
[02:50] <mpt> It's a form of communication
[02:51] <mpt> So instead of "no need" I should have said "no need from Launchpad's point of view"
[02:51] <mpt> There may be from other users' point of view, though
[02:51] <LaserJock> right
[02:52] <mpt> e.g. marking a bug as In Progress says "don't bother trying to fix it yourself, someone else is already doing it"
[03:01] <wick2o> hello
[03:10] <wick2o> anyone around? 
[03:11] <wick2o> i remastered the install cd and have a working 100% preseeded cd with a custom "main"
[03:11] <wick2o> added a few packages (openvpn, joe + a few others)
[03:12] <wick2o> now that i have that working, i want to update the cd so i dont need to apt-get dist-update after the install
[03:12] <wick2o> is it really as simple as downloading the new packages and deleting the old versions?
[03:12] <wick2o> even with the restricted linux-server and the main linux-server-src ?
[05:41] <Amaranth> i thought bug 96430 was rejected
[05:41] <ubotu> Malone bug 96430 in linux-restricted-modules-2.6.20 "MASTER: Request for new-legacy nvidia drivers (9631)" [Medium,Confirmed]  https://launchpad.net/bugs/96430
[05:45] <desrt> oh god
[05:45] <mjg59> Amaranth: Well, restricted-manager does need updating to deal
[05:46] <desrt> so check it out.  i just bought a new mainboard.  two actually.
[05:46] <Amaranth> mjg59: to install legacy instead of glx
[05:46] <desrt> http://www.intel.com/products/motherboard/DG965MQ/index.htm
[05:46] <mjg59> Yup
[05:46] <Amaranth> isn't that just a rebuild?
[05:47] <Amaranth> i thought it built that list dynamically
[05:47] <desrt> onboard dvi.  intel gma x3000.  life is good.
[05:47] <mjg59> It comes with firewire?
[05:47] <desrt> yup
[05:47] <desrt> one out the back plus an internal pin header
[05:47] <desrt> see also: 8gb memory and 6 sata ports
[05:48] <desrt> nvidia and ati can both suck it.
[05:50] <Amaranth> desrt: *boing*
[05:54] <ajmitch> ah nice, free drivers & all
[05:55] <Amaranth> dude you can use blur in compiz with that thing ;)
[05:55] <ajmitch> wow ;)
[05:55] <desrt> ya.  it's a freakin' sweet board
[05:56] <desrt> buy one.  junk your nvidia card.
[05:56] <ajmitch> and the rest of my hardware
[05:56] <desrt> my p4 3.0ghz is getting slow these days.  time to move up :p
[05:56] <ajmitch> since I have an amd64 (socket 939), so ddr ram, etc
[05:59] <ajmitch> hm, nice cheap board too
[05:59] <desrt> (all thanks to matthew having a hissy fit in livejournal)
[06:00] <ajmitch> hah
[06:00] <ajmitch> nah my geforce 6600 isn't legacy (yet) :)
[06:00] <desrt> wait until next release :)
[06:01] <desrt> nvidia is gonna phase out cards nice and gradually in order that we are required to keep 10 different legacy patches
[06:01] <desrt> *packages
[06:01] <ajmitch> hopefully nouveau will be a little bit further along by then :)
[06:01] <ajmitch> I'm happy to go without 3d for awhile
[06:01] <desrt> hopefully nvidia will be funding nouveau by then
[06:01] <ajmitch> hah
[06:01] <ajmitch> you can hope
[06:02] <desrt> i wouldn't "hah" too hard
[06:02] <desrt> there will come a point where nouveau will look like a rather attrative alternative to continuing to maintain their binary cludge
[06:02] <ajmitch> though their binary kludge is meant to be unified across platforms (somehow)
[06:03] <desrt> i wonder to what extend that's actually true
[06:03] <Amaranth> a really awesome abstraction layer?
[06:03] <Amaranth> all their functions are named __nv00000005
[06:03] <ajmitch> given the differences in features, I wonder
[06:04] <desrt> anyway... fun conversation but now i've got to go shoot myself in the head
[06:04] <desrt> cheerio.
[06:04] <Amaranth> what, more gnome-panel stuff? ;)
[06:43] <hugomelo> BenC, I sent you a new proposal
[06:43] <hugomelo> BenC, please, read it
[07:51] <jamesh> doko: I don't suppose you've had a chance to look at that python-subversion bug?
[07:55] <doko> jamesh: sorry, not yet. just verified that I still see it with 1.4.3 on ubuntu
[08:05] <Hobbsee> what would be the opinion on puttign 915resolution in main, and maybe installing it on the cd?
[08:06] <jamesh> Hobbsee: it should get obsoleted soon
[08:06] <jamesh> by the new intel driver modesetting branch
[08:06] <Hobbsee> jamesh: that's soon.  this is now.
[08:06] <StevenK> WBy what?
[08:07] <jamesh> StevenK: the new version of the Intel driver does not use the BIOS for mode setting
[08:07] <jamesh> so you don't need to patch the modes in the video bios if they are wrong
[08:07] <StevenK> Is soon before Fiesty?
[08:07] <jamesh> and it should work on systems without a PC video bios
[08:07] <Hobbsee> well, preferably.
[08:08] <jamesh> StevenK: probably not
[08:08] <jamesh> keithp's demo of his work at linux.conf.au was pretty impressive
[08:09] <StevenK> Then maybe we want to promote 915resolution for Feisty, and then demote it back for Feisty+1?
[08:09] <StevenK> Hrm, I've been meaning to finish watching Keith's LCA talk.
[08:10] <StevenK> That's the "we've managed to get the video driver autodetecting all the time" ?
[08:12] <jamesh> well, he did say that having it detect VGA plug/unplug wasn't really desirable with current laptops
[08:12] <jamesh> since it essentially chewed up a watt of power to have the corresponding hardware on
[08:13] <StevenK> So you get it to start detecting when you hit the video change button?
[08:13] <jamesh> maybe
[08:14] <ajmitch> a watt, just for that?
[08:14] <jamesh> ajmitch: the VGA hardware takes about that much power, yes
[08:15] <jamesh> ajmitch: it needs to be on to detect if a monitor is plugged in, but is usually off because it isn't needed
[08:16] <Amaranth> so
[08:17] <Amaranth> i've got this ati package that i _think_ makes it possible to suspend/resume with compiz running
[08:17] <Amaranth> but i don't own ati hardware
[08:17] <Amaranth> anyone wanna test? :)
[08:17] <Amaranth> it's just a patch from upstream git, i'm not going to break your video card :)
[08:18] <Burgundavia> sadly my ati hardware is at my gfs house
[08:19] <AndrewB> Hmm I am looking at https://wiki.ubuntu.com/Testing/InstallMethods and things look easy.. only where do I document this information to?
[08:19] <StevenK> Burgundavia: All the more reason to visit her?
[08:19] <Burgundavia> it is 11pm at night
[08:20] <StevenK> Heh
[08:20] <StevenK> "No no, I'm not here to see you, I want my laptop."
[08:20] <Burgundavia> I have my laptop
[08:21] <Burgundavia> my desktop is my ati machine
[08:21] <StevenK> I was guessing what contained ATI hardware.
[08:28] <Amaranth> anyway, debdiff is attached to bug 90740 if someone wants to test it
[08:28] <ubotu> Malone bug 90740 in xserver-xorg-video-ati "gtk-window-decorator corruption after resume from sleep" [Undecided,In progress]  https://launchpad.net/bugs/90740
[08:40] <sladen> StevenK: the -modesetting driver is in universe
[08:42] <dholbach> good morning
[09:02] <fabbione> cjwatson:    * Add scsi-firmware to cdrom and hd-media images. <- does that propagate to netboot too?
[09:23] <pitti> Good morning
[09:24] <Hobbsee> hey pitti!
[09:55] <tepsipakki> fabbione: oh, you assigned 96764 to Colin, but I marked it as dupe of 94786. I'll assign that instead :)
[09:56] <Burgundavia> tepsipakki: it was you that sent me that "group" hack awhile back, no?
[09:58] <tepsipakki> pam_group?
[09:59] <ajmitch> Burgundavia: what did it do?
[09:59] <Burgundavia> let me dig through my work email
[10:00] <tepsipakki> oh
[10:00] <tepsipakki> don't remember, sorry :)
[10:01] <Burgundavia> basically it assigned ldap users to local groups, such as cdrom, etc. so that they go access to them
[10:01] <tepsipakki> so it was pam_group
[10:02] <fabbione> tepsipakki: ok please don't mess it up.
[10:04] <Burgundavia> tepsipakki: i thought it was you
[10:05] <tepsipakki> Burgundavia: yep.. so it's working for you?-)
[10:06] <Burgundavia> I haven't put it into product due to an office move and my other hat, marketing, eating up too much of my time
[10:06] <Burgundavia> oh, and an asterisk server that believes uptime should be measured in hours
[10:07] <ajmitch> heh
[10:07] <ajmitch> looks like pam_group will need packaged
[10:07] <ajmitch> or not
[10:07] <Burgundavia> hey, it is 2 year old cvs code running on White Box EL 3
[10:07] <tepsipakki> it's included
[10:07] <tepsipakki> ajmitch: ^^
[10:07] <ajmitch> part of standard pam, how useful
[10:07] <tepsipakki> heh
[10:08] <ajmitch> yeah, apt-cache search didn't give me anything, I thought it would have been an additional module :)
[10:08] <Burgundavia> ajmitch:  you are now on the planet
[10:08] <ajmitch> lucky me
[10:09] <ajmitch> hm, it's not really a new tool, it's just one where I'm trying to fix the UI & functionality
[10:09] <Burgundavia> if it isn't in production yet, it is new
[10:10] <ajmitch> true
[10:10] <Burgundavia> work with your marketing person now, ajmitch :)
[10:10] <ajmitch> hah
[10:10] <Burgundavia> oh, btw, is that code in bzr/git yet
[10:10] <Burgundavia> ?
[10:10] <ajmitch> sure
[10:11] <ajmitch> doesn't the spec link to it?
[10:11] <Burgundavia> same repo
[10:11] <Burgundavia> ?
[10:11] <Burgundavia> morning jono
[10:12] <ajmitch> I'll push the latest to the ubuntu-dev copy of it
[10:12] <ajmitch> hey jono 
[10:26] <Amaranth> tepsipakki: the debdiff in bug 90740 fixes the bug according to the reporter, just need someone to upload
[10:26] <ubotu> Malone bug 90740 in xserver-xorg-video-ati "gtk-window-decorator corruption after resume from sleep" [Undecided,In progress]  https://launchpad.net/bugs/90740
[10:27] <tepsipakki> Amaranth: ok, thanks
[10:32] <tepsipakki> Amaranth: uploaded
[10:32] <Amaranth> awesome, thanks
[10:33] <Amaranth> that's two huge compiz-related bugs fixed today :)
[10:33] <cjwatson> fabbione: netboot never needed that in the first place; you don't need scsi-firmware in the initrd to get more udebs from the network
[10:34] <Burgundavia> cjwatson: you don't work in the london office, do you?
[10:34] <cjwatson> Burgundavia: no
[10:35] <anti_pop> did you notice that "nv" and "nvidia" is broken for most nvidia users at the moment (correct me if i am wrong)
[10:35] <tepsipakki> anti_pop: why should nv be broken?
[10:35] <Burgundavia> bugger. I need to get a hold of Chris Kenyon. I was supposed to have a phone conversation with him today and it is getting close to 2 am her
[10:35] <cjwatson> experience suggests that when commuting to London it's very rare for me to manage to get in before 10:00, and that involves waking up around 6:00
[10:35] <anti_pop> http://ubuntuforums.org/showthread.php?t=394549
[10:35] <anti_pop> https://launchpad.net/ubuntu/+bug/96833
[10:35] <ubotu> Malone bug 96833 in Ubuntu "Blank screen with the latest nv drivers" [Undecided,Confirmed]  
[10:36] <Burgundavia> right
[10:36] <anti_pop> latest upgrades broke that for me
[10:36] <Burgundavia> I have seen English traffic and am glad I don;t live there
[10:36] <Mithrandir> Burgundavia: see privmsg
[10:36] <Burgundavia> got it
[10:37] <tepsipakki> anti_pop: there hasn't been an update of nv since the beta
[10:37] <fabbione> cjwatson: hmm ok.. i will check again because IIRC i saw the warnings there too..
[10:37] <anti_pop> but something concerning xorg or x or whatever i think
[10:38] <cjwatson> fabbione: netboot doesn't have disk drivers in the initrd, in general.
[10:38] <ajmitch> Burgundavia: ah, you linked to the images on my system directly, in your blog post?
[10:39] <Burgundavia> ajmitch: of course I did. I can fix that, if your machine is busy dying right now
[10:39] <ajmitch> Burgundavia: it's interesting seeing so many hits on it
[10:39] <ajmitch> a couple of hits every few seconds
[10:39] <fabbione> cjwatson: yeps.. i still want to recheck tho.. it won't cost you anything :)
[10:39] <Burgundavia> ajmitch: when I linked an image on my home server to something on the UWN, I got hits all night. Unfortunately I couldn't sleep because the hdd was too noisy
[10:40] <ajmitch> Burgundavia: they're only a few KB
[10:41] <Amaranth> those screenshots were taken when compiz was running :)
[10:41] <tepsipakki> anti_pop: eh, that bug reporter has nvidia options in the conf
[10:41] <Amaranth> ajmitch: oh, and that's some awesome stuff there
[10:41] <anti_pop> i had not and its not working
[10:41] <ajmitch> Amaranth: hm, how can you tell? ;)
[10:42] <tepsipakki> anti_pop: a log would be nice
[10:42] <Amaranth> ajmitch: no window decorations
[10:42] <Amaranth> gnome-screensaver needs to do a little extra work or something to get the decorations too
[10:42] <ajmitch> heh
[10:42] <anti_pop> tepsipakki, ok i edit my xorg to "nv" (atm "vesa") and post which log (sorry, im not that used to stuff like that)
[10:42] <Amaranth> iirc it makes an incorrect assumption about the way it should work but actually has code to do the right thing in there
[10:43] <Amaranth> so it's just a matter of making it realize it needs to use it
[10:43] <tepsipakki> anti_pop: ok, /var/log/Xorg.0.log
[10:43] <tepsipakki> anti_pop: and your xorg.conf too
[10:43] <anti_pop> but i wont be able to go to a terminal when using nv
[10:44] <tepsipakki> how so?
[10:44] <tepsipakki> anti_pop: you can't change the virtual terminal? (ctrl+alt+F1)
[10:44] <anti_pop> when i boot with xorg.conf containing "nv", it ends up in a black screen, and im not able to lauch a terminal by alt+ctrl+F1
[10:45] <anti_pop> so i'd have to change to "vesa" again, and that would overwrite the logs, right ?
[10:45] <Chipzz> anti_pop: ctrl-alt-backspace should kill your X?
[10:45] <anti_pop> doesnt
[10:45] <tepsipakki> anti_pop: true, but the old log would be Xorg.0.log.old
[10:45] <anti_pop> ok
[10:46] <ajmitch> Burgundavia: 533 hits so far
[10:46] <ajmitch> seems that planet is popular
[10:46] <anti_pop> then ill reconfigure xserver-xorg and use nv and reboot and then post the log
[10:46] <tepsipakki> anti_pop: just for amusement, try moving xorg.conf aside and see what happens
[10:46] <anti_pop> uh
[10:46] <anti_pop> ok
[10:52] <pitti> doko: this small hack http://pastebin.ca/411815 is required to make pycentral work with fakechroot; do you think it is too evil to be uploaded to feisty proper?
[10:54] <doko> pitti: don't see a reason not to upload; does it still work without fakechroot?
[10:54] <pitti> doko: the normal case is that the os.unlink fails because fn2 doesn't exist
[10:54] <pitti> doko: I'll do a few more tests, of course, but so far yes (due to except: pass)
[10:55] <doko> ok
[10:57] <anti_pop> tepsipakki, i did the following
[10:57] <anti_pop> putting my xorg aside, restarted x -> blackscreen, not able to go to terminal
[10:58] <anti_pop> dpkg-reconfigured to "nv", rebooted (wrote down time to identify correct log) -> blackscreen, no terminal..
[10:58] <anti_pop> reconfigured to vesa, im in x again
[10:58] <pitti> doko: yep, works fine in all cases here; I added a few printfs to the 'except:' clause, and it's properly caught and pass'ed
[10:58] <pitti> doko: so, you are fine with me uploading this?
[10:59] <doko> pitti: sure
[10:59] <pitti> doko: thanks
[10:59] <anti_pop> in which folder do i find xorg.0.log or whatever its called ?
[11:01] <zyga> anti_pop: /var/log/
[11:02] <anti_pop> does this folder contain only files from actual boot ?
[11:02] <pitti> anti_pop: #ubuntu, please; and no, it has logs from previous boots as well
[11:03] <anti_pop> pitti, some guy in here requested a log, i try to do that and will leave
[11:04] <pitti> anti_pop: oh, ok; you don't need to leave, don't worry; it's just our attempt to keep the channel free of support questions :)
[11:04] <tepsipakki> anti_pop: attach it to that bug
[11:06] <anti_pop> ok i think i did find the right log and will do so
[11:09] <giangy> 'morning
[11:38] <pitti> Mithrandir: do you remember approving gs-esp 8.15.4 for feisty? (I'm currently processing the outstanding package sponsoring from Till)
[11:41] <pitti> Mithrandir: oh, nevermind, that's already in feisty
[11:54] <Mithrandir> pitti: yes, I did
[11:57] <mooey> pitti: is the apport retracing service working at the moment?
[11:58] <pitti> mooey: it should work again, yes; I need to re-tag some bugs which were untagged, but not retraced due to chroot breakage tonight
[11:59] <mooey> pitti: ah, excellent :-) theres a few bugs that failed listed in bug 96903
[11:59] <ubotu> Malone bug 96903 in apport "apport retracing service is not retracing bugs" [Undecided,Unconfirmed]  https://launchpad.net/bugs/96903
[11:59] <pitti> Mithrandir: mind you, summer time is +1 hour, not +1 day :-P
[11:59] <Mithrandir> pitti: indeed
[12:03] <pitti> mooey: yep, exactly those that my current script figured out
[12:11] <mooey> pitti: thanks, all retraced now :)
[12:11] <pitti> mooey: oh, already?
[12:15] <mooey> pitti: all of the i386 bugs, yep :)
[12:27] <cjwatson> yow, raid tests in vmware are hard on the disk space
[12:27] <fabbione> cjwatson: eheheh
[12:28] <cjwatson> maybe I should just get a 200 squillion gigabyte drive for that machine
[12:28] <fabbione> cjwatson: you will endup like me today with that setup :)
[12:28] <cjwatson> should only cost about 5 pence these days
[12:28] <Mithrandir> it's probably cost you about one beer.
[12:28] <fabbione> cjwatson: if you have room, i can ship you my SAN with tons of FC-HBA controllers :)
[12:28] <cjwatson> actually, if I got two of them I could find out if that BIOS does dmraid
[12:29] <Mithrandir> fabbione: houses in the UK doesn't need that kind of heating.
[12:29] <fabbione> Mithrandir: i didn't specify it needs to be at home :) just space :)
[12:29] <maswan> Mithrandir: sure they do, they haven't discovered insulation yet. ;P
[12:29] <Mithrandir> I didn't specify "home", I said "house".
[12:29] <Mithrandir> :-P
[12:30] <fabbione> ROFL
[12:34] <tepsipakki> fabbione: sorry to disturb you, but in xorg changelog I saw that you made a special case for elographics. Could you take a look at bug 89590?
[12:34] <ubotu> Malone bug 89590 in xorg "Feisty doesn't recognize 17" LCD screen" [Medium,Confirmed]  https://launchpad.net/bugs/89590
[12:35] <fabbione> tepsipakki: i think you can remove that special case safely now
[12:35] <tepsipakki> fabbione: woohoo :)
[12:35] <fabbione> let me check again
[12:35] <tepsipakki> please do
[12:36] <tepsipakki> in that bug the reporter has a chipset which matches that special case
[12:37] <fabbione> tepsipakki: yes i see
[12:37] <fabbione> i suggest you do this way:
[12:38] <fabbione> if we hit the special case.. try to xresprobe or whatever is called now
[12:38] <fabbione> if there are data coming from xresprobe then skip the special case
[12:38] <fabbione> if there are no data, use the special case
[12:39] <fabbione> the other solution is to remove the special case completely, but it kind of sucks because it was the only touch screen monitor we could configure out of the box :)
[12:39] <fabbione> anyway your call.. i don't care either way
[12:39] <fabbione> that special case has been there since dapper i think
[12:40] <tepsipakki> yes
[12:40] <tepsipakki> I'll think about it
[12:40] <fabbione> if you remove it, make sure to change dexconf too
[12:40] <fabbione> IIRC the special case was handled there too
[12:40] <fabbione> to create the touch screen input stanza
[12:42] <tepsipakki> yes I saw that
[12:46] <dholbach> ogra: I looked into bug 92648 - there are some questions you (or LaserJock) need to answer first
[12:46] <ubotu> Malone bug 92648 in edubuntu-docs "no menu item for About Edubuntu" [Medium,Needs info]  https://launchpad.net/bugs/92648
[12:47] <ogra> questions ?
[12:47] <dholbach> ogra: or rather 'open points'
[12:48] <ogra> two items is fine, we dont need to hide our inheritance ...
[12:48] <dholbach> ok :)
[12:48] <dholbach> i'll upload it then
[12:48] <ogra> whats the other "open point" ?
[12:48] <dholbach> you just need to create the desktop file
[12:48] <ogra> ah, k
[12:48] <dholbach> ogra: gracias
[12:48] <ogra> its there, jordan hanst given me the final package yet
[12:49] <dholbach> ok
[12:49] <ogra> *hasnt
[12:49] <ogra> btw, all my icons from gdm are gone in edubuntu ? 
[12:49] <ogra> what did chnage? 
[12:49] <ogra> (with the most recent update)
[12:49] <dholbach> kwwii should know
[12:49] <ogra> oki
[12:50] <dholbach> i was merely the upload bitch
[12:55] <ajmitch> hah
[12:57] <mneptok> dholbach: yes, but you're *our* upload bitch.
[12:57] <kwwii_> lol
[12:57] <ogra> hey kwwii 
[12:57] <ogra> so
[12:58] <ogra> in my gdm config i never defined a gtkrc ... did you change the gtkrc of the Human theme ? 
[12:59] <kwwii> ogra: nope, no change in anything in the normal Human theme
[12:59] <kwwii> ogra: all I added was a gtkrc for HumanCircle and that line in HumanList
[12:59] <ogra> hmm
[01:00] <ogra> why would that break my gdm which uses a totally different theme ? 
[01:00] <kwwii> ogra: no idea ;-(
[01:00] <ogra> i dont use and Human ...
[01:00] <kwwii> ogra: what exactly is wrong?
[01:00] <kwwii> ogra: and which theme are you basing yours on?
[01:00] <ogra> edubuntu uses the Edubuntu Colrs theme, which didnt change sice two releases
[01:00] <ogra> all icons in the gdm menu are missing here
[01:01] <kwwii> then I would suggest adding that line to the top of the gtkrc ;-)
[01:01] <kwwii> and point it to the icon set you want to see there
[01:01] <ogra> hmm, but why does gdm need it suddenly
[01:02] <ogra> thats what concerns me ... i'm fine wih adding a line at the top of my gtkrc, i just want t know why :)
[01:02] <fabbione> ogra: it's called evolution
[01:02] <fabbione> more features.. more regressions :)
[01:02] <ogra> fabbione, dont get mail apps in the game please :P
[01:02] <kwwii> ogra: that line was in the Human theme already, I have no idea when it was added
[01:02] <ogra> login managers are weird enough :)
[01:03] <kwwii> ogra: all I did yesterday was to fix that same problem in the other two themes
[01:03] <ogra> kwwii, ok, i'll look and die dumb :)
[01:04] <mneptok> fabbione: i noticed Evolution usually has 3x the regressions for features, while evolution (small e) seems to have a somewhat better ratio.
[01:05] <fabbione> mneptok: agreed.. and it takes longer to spot the errors.... like 100000 years from monkey to computer nerds
[01:10] <pochu> Mithrandir: there seems not to be any i386 image in cdimage.u.c, for more than one hour, are they being built?
[01:10] <cjwatson> pochu: I'm on it already
[01:10] <cjwatson> soyuz bug
[01:11] <pochu> oh, ok :)
[01:21] <TheMuso> Is the fact that there is no consoles in the beta a bug, or is that intensional?
[01:21] <TheMuso> s/there is/there are/
[01:24] <Treenaks> it's a bug, I think
[01:24] <Treenaks> if you boot it without the splash, you see there's a parse error in the /etc/event.d/tty* files
[01:24] <TheMuso> Treenaks: Ah ok.
[01:32] <cjwatson> TheMuso: known bug, fixed post-beta
[01:33] <TheMuso> cjwatson: Thought as much, thanks.
[01:33] <TheMuso> cjwatson: DId you by chance see the brltty bug I reported? Give me a sec and I'll get the bug number.
[01:33] <cjwatson> no
[01:34] <TheMuso> bug 91894
[01:34] <ubotu> Malone bug 91894 in brltty "Brltty doesn't properly load when attempting to use serial braille display on live CD." [Undecided,Unconfirmed]  https://launchpad.net/bugs/91894
[01:39] <cjwatson> meh
[01:45] <cjwatson> TheMuso: fixing, thanks
[01:46] <TheMuso> cjwatson: No problem.
[01:58] <gnomefreak> is the dpkg problem known? sudo dpkg --configure -a returns dpkg: unknown option -o
[01:59] <Hobbsee> gnomefreak: i cant reproduce that
[01:59] <gnomefreak> i wasnt able to till this morning
[02:00] <gnomefreak> Hobbsee: do you have anything waiting to be configed?
[02:00] <gnomefreak> thats odd
[02:00] <gnomefreak> now it works
[02:00] <Hobbsee> gnomefreak: nope
[02:01] <fabbione> ajmitch, slomo, siretart: ping?
[02:01] <ajmitch> fabbione: pong
[02:01] <fabbione> ajmitch: are you ok with a UVF exception for bzr-gtk_0.15.1.orig.tar.gz in universe?
[02:02] <gnomefreak> Hobbsee: http://pastebin.ca/411955
[02:02] <Hobbsee> odd
[02:02] <gnomefreak> seems to only happen when there are errors with dpkg
[02:03] <ajmitch> fabbione: bugfix release?
[02:03] <fabbione> ajmitch: it's required to work with the new bzr that's making its way to the archive now
[02:04] <fabbione>   * New upstream release
[02:04] <fabbione>   * Bumped Depends on bzr to 0.11
[02:04] <fabbione>   * Fixed Description in debian/control to include all commands
[02:04] <ajmitch> right, looks sane
[02:04] <fabbione> ok thanks
[02:04] <fabbione> (btw i am only sponsoring this package for Etienne)
[02:04] <fabbione> but i figured i asked before messing up
[02:04] <fabbione> or Mithrandir would have killed me :P
[02:04] <ajmitch> heh
[02:12] <gnomefreak> Hobbsee: i filed a bug anyway because IMO it should still error for -a not -o
[02:18] <mvo> cjwatson: in the meta-packages we seem to not enfore a kernel. is that a deliberate decision?
[02:20] <lexual> is there an ubiquity irc channel?
[02:20] <asac> could someone please NEW firefox?
[02:21] <Hobbsee> lexual: cjwatson is hte main person on it
[02:21] <Fujitsu> asac: It isn't NEW, surely...
[02:21] <asac> firefox-libthai
[02:22] <ajmitch> Fujitsu: new binary package
[02:22] <asac> is new bin package
[02:22] <Fujitsu> Ah.
[02:23] <Mithrandir> asac: I can do it
[02:23] <lexual> cjwatson: is it possible to start ubiquity, and provide which mirror to use for /etc/apt/sources.list ?
[02:24] <asac> Mithrandir: cool. thanks ... hope this is all for now then :)
[02:26] <Mithrandir> asac: is it intentionally that firefox-libthai doesn't depend on firefox?
[02:26] <asac> ups wtf
[02:27] <Mithrandir> I'll be fine with accepting it without that fix, but it looks wrong.
[02:27] <Mithrandir> (accepted)
[02:28] <asac> will fix it ... thanks for moving in.
[02:32] <cjwatson> mvo: yes.
[02:33] <cjwatson> lexual: you may be able to preseed the mirror in the same way you'd preseed the alternate installer (see the installation guide on help.ubuntu.com) but it's otherwise entirely undocumented and untested
[02:33] <cjwatson> lexual: channel is #ubuntu-installer, BTW
[02:36] <TheMuso> Mithrandir: When you get a chance, I reported bug 91868, to fix an accessibility bug for the live CD. If you could look at it and merge the fix, that would be great. Thanks.
[02:36] <ubotu> Malone bug 91868 in casper "Magnifier does not start from accessibility menu due to incorrectly referenced file." [Undecided,Unconfirmed]  https://launchpad.net/bugs/91868
[02:37] <Mithrandir> sure
[03:07] <bddebian> Heya
[03:43] <cjwatson> argh, trying to reproduce bug 80938 is hurting my brain
[03:43] <ubotu> Malone bug 80938 in ubiquity "MASTER: do_remove BrokenCount assertion can fail" [Medium,Confirmed]  https://launchpad.net/bugs/80938
[03:44] <_ion> Please excuse my ignorance, but what's this "MASTER:" i'm seeing in front of some bug titles?
[03:45] <cjwatson> informal convention to help maintainers remember which instance of frequently-reported bugs to dup new reports against
[03:45] <cjwatson> I picked itt up from the mozilla team
[03:46] <_ion> All right.
[03:46] <cjwatson> pochu: i386 images available now, at least for Ubuntu
[03:47] <pochu> cjwatson: cool, thanks!
[03:47] <Hobbsee> that's a great idea!
[03:48] <cjwatson> it's useful on packages with lots of bugs
[03:49] <xhaker> doko, Keybuk any of you available to talk just a bit about GSoC work?
[03:50] <doko> xhaker: sure, whats the matter?
[03:52] <xhaker> Would you have access to the applications in google already? if not i could explain in a query
[03:52] <xhaker> *i can*
[03:59] <asac> mpt: ever done mozilla triaging?
[04:08] <mpt> asac, I did it for three years (I was a QA contact at b.m.o)
[04:11] <asac> mpt: cool ... then i don't understand why you don't like in progress for upstream submitted bugs.
[04:12] <mpt> because In Progress means "Don't worry about trying to fix this one, someone's already working on it"
[04:13] <asac> mpt: yeah ... but that's the truth ... (you should take care that upstream doesn't forget)
[04:13] <mpt> I suppose Ubuntu Firefox is a special case, though, not being Free Software
[04:13] <mpt> so even if someone came along with a fix for you, you'd send them upstream anyway
[04:14] <asac> mpt: remember ... usually nobody comes along for firefox et al ...
[04:14] <mpt> true
[04:14] <asac> if one can fix firefox bugs et al they go upstream
[04:14] <asac> so ... "in progress" for us :)
[04:15] <asac> which means: mozilla team members should regularaly take care that upstream doesn't forget
[04:15] <asac> but move the bug from confirmed radar
[04:15] <asac> which means: "This needs work ... and info on what work is needed is available"
[04:15] <asac> mpt: all i want to say is:
[04:15] <mpt> This is my fault, again
[04:15] <asac> launchpad is not a one thing fits all 
[04:15] <mpt> A long time ago, I was supposed to split "Rejected" into "Not a Bug" and "Not For Us"
[04:16] <mpt> where "Not For Us" for a distro would mean "we're not going to fix it here, go upstream"
[04:16] <mpt> and "Not For Us" for upstream would mean "it's not our problem, go to the distro"
[04:17] <StevenK> mpt: The problem there is that it changes meanings depending on context. Surely Launchpad would prefer to be consistent?
[04:17] <mpt> so you'd be able to use "Not For Us" instead of "In Progress" for bugs that you weren't actually ever going to fix yourself
[04:17] <asac> yeah ... but "not for us" means (as you said about in progress" we don't care
[04:17] <asac> which is not true
[04:17] <asac> we want to help users to get a point upstream
[04:17] <asac> so we should take care that it gets attention ... from time to time
[04:18] <mpt> StevenK, it would be more consistent than the current situation. (That doesn't necessarily mean it would be a good idea.)
[04:18] <StevenK> But still changes meanings depending on context.
[04:19] <StevenK> Well, it does and it doesn't.
[04:19] <mpt> In both cases it would mean "This is a problem, but it isn't our problem"
[04:19] <mpt> Another example is an app that crashes because of a bug in a library
[04:19] <StevenK> mpt: Perhaps you need to ignore my tired goings on. :-)
[04:19] <mpt> no, they're interesting
[04:20] <mpt> Maybe it should be called "Elsewhere" instead...
[04:20] <mpt> but then eventually I'd like an advanced search operator called "elsewhere", so that could be confusing
[04:21] <StevenK> Rejected with an explantion is just as good, surely?
[04:21] <mpt> so you could search for "status:confirmed elsewhere:fixed" to find fixes that you can pick up (e.g. from another distro)
[04:22] <StevenK> "This is not a bug, bugger" status => Rejected. "This is a problem, but now ours, go talk to $NICE_PEOPLE over there." status => Rejected
[04:22] <StevenK> s/bugger/bugger off/
[04:22] <mpt> StevenK, the difference between "Not a Bug" and "Not For Us" search-wise is that "Not a Bug" would not show up in search results by default (like "Rejected" doesn't now)
[04:22] <StevenK> Where as Not For Us would?
[04:22] <mpt> but "Not For Us" bugs *would* show up, if they were also open anywhere else
[04:22] <mpt> because that would indicate they were still a valid problem
[04:22] <StevenK> My problem is Not For Us keeps reminding me of Debian's buildd network
[04:22] <zakame> hmmm, which package controls /dev/mapper/* ?
[04:23] <StevenK> zakame: Feisty or Edgy?
[04:23] <mpt> StevenK, I'm not familiar with that
[04:23] <StevenK> mpt: Ah. The Debian buildd network has a concept of Not-For-Us. Stuff that the arch in question doesn't have to bother about building, for example, grub on sparc or such like.
[04:24] <asac> mpt: i just want to emphasize that while you (launchpad team) might think that you know the single best way to do things, you probably don't.
[04:24] <asac> StevenK: No-For-Us ... is not for U.S. 
[04:24] <StevenK> It'd be nice if LP grew something like that, but less manual.
[04:24] <asac> ah :)
[04:24] <mpt> asac, sure, and I'm not criticizing you at all, I'm trying to work out how Launchpad hasn't fit your work, so I can figure out how Launchpad might improve
[04:24] <asac> mpt: will you be in spain?
[04:25] <mpt> asac, not that I know of, alas
[04:25] <asac> hmmm ... ok
[04:26] <mpt> It would be good to sit down and chat about how you do things
[04:26] <mpt> and how Ubiquity bugs are handled
[04:26] <mpt> and Xorg bugs
[04:26] <mpt> etc
[04:26] <asac> mpt: definitly.
[04:26] <Mithrandir> mpt: it would be good if LP was better for the release manager too.
[04:26] <asac> mpt: i think the approach will be: allow individualization of bug tracker by driver team or something
[04:27] <mpt> asac, maybe, but that would remove a fair chunk of the point of sharing a bug tracker in the first place
[04:27] <mpt> which is that you can be notified when a bug has been fixed elsewhere
[04:28] <Robot101> has anyone else seen cupsd start ~50 dbus-daemons?
[04:28] <mpt> whether or not elsewhere is using Launchpad themselves
[04:28] <mpt> and then grab the fix from them, and save yourself effort that way.
[04:28] <asac> but what has this to do with package states?
[04:29] <mpt> Because if you have custom statuses, how does Launchpad know which ones count as fixed?
[04:29] <asac> i see that this is upstream integration feature ... imo the states from upstream are mapped pretty well atm.
[04:29] <mpt> Yes, but what if upstream is using Launchpad? :-D
[04:29] <asac> yeah ... we could agree on a set of final states (fixed states)
[04:29] <mpt> That's a possibility
[04:29] <asac> i think the problem here are the intermediate states
[04:29] <asac> e.g. states that drive the workflow
[04:30] <asac> simple packages just go from unconfirmed -> confirmed -> fixed ... others might have various steps in between
[04:30] <mpt> or let people checkbox which of their statuses count as Fixed for the purposes of sharing (e.g. Fix Committed, Fix Verified, Fix Uploaded...)
[04:31] <asac> probably ... but as i said ... we could have a minimal set of states that are common
[04:31] <asac> i think nobody has a problem with Fix Released for instance
[04:31] <mpt> oh, yes they do ;-)
[04:32] <asac> imo it would help if we could allow teams just to introduce substates
[04:32] <asac> e.g. in launchpad we have unconfirmed -> needs info -> confirmed -> In progress -> Fixed
[04:32] <asac> now teams can say ... I want to refine state Needs Info for me
[04:32] <mpt> or just have Open, Rejected, and Fixed, and everything else is tags
[04:33] <asac> yeah ... however tags should then be associated with states as well
[04:33] <StevenK> mpt: Speaking of tags ... launchpad needs to hide tags that are not referenced by any package.
[04:33] <mpt> StevenK, known bug
[04:33] <asac> -> so substates again
[04:33] <mpt> but thanks
[04:34] <StevenK> mpt: Ah, but is it reported? :-)
[04:34] <asac> so some tags are substates and some are something else
[04:34] <asac> imo that would mix concepts
[04:34] <mpt> StevenK, bug 59154
[04:34] <ubotu> Malone bug 59154 in malone "Don't show all tags on the bug listing page" [Medium,Confirmed]  https://launchpad.net/bugs/59154
[04:35] <StevenK> Ah, nice
[04:35] <asac> does it show any tags at all?
[04:35] <asac> i haven't seen any ;)
[04:35] <mpt> Only if you click the grey "Tags" bar
[04:35] <asac> bug 59154 is one of the most important feature for me I guess
[04:39] <asac> of course its not that important ... misinterpreted summary :)
[04:41] <neuralis> Hobbsee: the nvidia message made it through
[04:41] <Hobbsee> neuralis: great.  i havent seen it yet
[04:41] <mpt> asac, thanks again for your comments, they're very thought-provoking
[04:42] <Hobbsee> ah, here it is
[04:42] <asac> mpt: night
[04:43] <mpt> (see bug 36059 if you're interested)
[04:43] <ubotu> Malone bug 36059 in malone ""Rejected" should be split into "Not a Bug" and "Not For Us"" [Medium,Confirmed]  https://launchpad.net/bugs/36059
[04:44] <asac> mpt: maybe lets talk about this tomorrow again .... i think it will take some time to get a common understanding of what is needed and what could be done to make launchpad the best ever :)
[04:45] <asac> mpt: or later today? where are you based?
[04:48] <cypher1> is Qt associated with KDE ?
[04:49] <Hobbsee> ....
[04:50] <StevenK> In as much as as GTK+ is associated with Gnome.
[05:10] <tepsipakki> mjg59: ping, wacom
[05:12] <mjg59> tepsipakki: Hi
[05:12] <tepsipakki> howdy
[05:13] <tepsipakki> mjg59: I'm looking at the various bugs about wacom, device naming et al
[05:14] <tepsipakki> mjg59: I merged a new wacom-tools hoping that it might get past UVF, would you like to take a look?
[05:14] <mjg59> tepsipakki: Sure. Can I see the debdiff?
[05:14] <tepsipakki> yes, I'll put it somewhere first
[05:15] <mjg59> Thanks
[05:23] <_ion> pitti: Hmm, i just noticed something. The amd64 port of the nvidia driver doesn't seem to support every device the x86 port with the same version number supports. Additionally, in the amd64 port the device id '0000' is listed. The easiest fix to the first problem would be to generate the lists within the linux-restricted-modules source package, and '0000' can simply be ignored by nvidia_supported.
[05:24] <pitti> _ion: I agree
[05:25] <pitti> _ion: let's see what BenC thinks about integrating those scripts into l-r-m proper, to get nice modaliases
[05:26] <BenC> pitti: I forgot to answer that email, but I'm all for it
[05:26] <pitti> BenC: yay
[05:26] <_ion> Very nice
[05:26] <BenC> anything to make your life as easy as you've made mine :)
[05:29] <_ion> benc: If you decide to include the 96xx driver in addition to the 71xx and 97xx drivers, the nvidia_supported script included in my patch already supports that. One just needs to list all the nvidia modules sorted by their version numbers in a decreasing order, something like sh nvidia/nvidia_supported .../nvidia/nv-kernel.o nvidia .../nvidia-96/nv-kernel.o nvidia_96 .../nvidia-71/nv-kernel.o nvidia_71 (whereas currently it is ...
[05:29] <_ion> ... .../nvidia/nv-kernel.o nvidia .../nvidia-legacy/nv-kernel.o nvidia_legacy)
[05:29] <_ion> My card happens to be among the ones that 97xx doesn't support anymore. :-)
[05:35] <tepsipakki> mjg59: ok, needed to test it actually builds.. two debdiffs here: http://users.tkk.fi/~tjaalton/wacom/
[05:36] <mjg59> tepsipakki: So the first is just the version update, the second is your fixes?
[05:36] <tepsipakki> the first has it all
[05:36] <mjg59> tepsipakki: Ah
[05:37] <tepsipakki> or do you prefer it otherwise=
[05:37] <tepsipakki> ?
[05:37] <mjg59> No, that's fine
[05:38] <mjg59> tepsipakki: Couple of things - we don't need setserial any moe
[05:38] <mjg59> tepsipakki: And it's still /dev/wacom
[05:38] <mjg59> Is that deliberate?
[05:39] <tepsipakki> no.. where?
[05:39] <mjg59> The init script
[05:40] <tepsipakki> oh, do you think it could be /dev/input/wacom for serial and usb?
[05:40] <tepsipakki> that was just copied from the old version
[05:41] <mjg59> Arguably, yeah
[05:41] <mjg59> Then the X setup would need fixing as well
[05:41] <tepsipakki> yes
[05:41] <mjg59> But then there'd be a chance of USB stuff just working
[05:41] <tepsipakki> what a drag
[05:41] <tepsipakki> :)
[05:45] <Riddell> Mithrandir: no opinion on k3b UVFe yet?
[05:48] <tepsipakki> mjg59: are the wacom-tools needed by the driver, in general? In the new version it's the driver which has the udev-rules.. but then again wacom-tools has the initscript..
[05:49] <cypher1> is not there a Qt C++ UI compiler available in repos ?
[05:50] <Riddell> cypher1: question for #kubuntu (but they're in the libqt4-dev and qt3-dev-tools packages)
[05:50] <cypher1> Riddell, thanks!
[05:50] <Mithrandir> Riddell: sorry, I totally forgot.  Can you prod me tomorrow during the day?
[05:51] <tsmithe> pitti, are you around?
[05:51] <Riddell> Mithrandir: ok
[05:51] <Riddell> mvo: get my software-properties questions?
[05:52] <pitti> tsmithe: hello
[05:54] <tsmithe> pitti, when you rejected wired, which pdfs were you referring to? i ran over the tree, and could only find ./src/portaudio/docs/portaudio_icmc2001.pdf ./src/portaudio/src/hostapi/asio/Callback_adaptation_.pdf  and ./src/portaudio/src/hostapi/asio/Pa_ASIO.pdf, none of which i thought were included, as the sources built using the system's copy of portaudio. i may be wrong, but i'm a bit confused
[05:54] <pitti> tsmithe: right, those
[05:55] <pitti> tsmithe: right, but we cannot ship them in the source package without, well 'source'
[05:55] <mvo> Riddell: let me check
[05:55] <tsmithe> pitti, ahh. right
[05:55] <tsmithe> i'll dfsg it, then
[05:55] <pitti> tsmithe: i. e. inclusion not in terms of binary packages, but the orig.tar.gz
[05:55] <tsmithe> and i guess i'll need an exception as well
[05:55] <tsmithe> right?
[05:55] <pitti> tsmithe: exception?
[05:55] <tsmithe> as universe is new package frozen, is it not?
[05:56] <Mithrandir> it is, yes.
[05:57] <mvo> Riddell: I got two mails about the dist-upgrader, nothing about software-propoerties. when did you send it?
[05:57] <tsmithe> ok. i don't get any bonus points as i had uploaded a bad version before the deadline, do i?
[05:58] <mjg59> tepsipakki: wacom-tools is needed for tablet PCs at the moment
[05:59] <mjg59> tepsipakki: Hm. I guess the initscript could be moved into the driver.
[06:00] <Riddell> mvo: err yeah, that's what I ment, ignore me, my brain is funny yoday
[06:00] <Riddell> today
[06:01] <gnomefreak> pitti: is need-powerpc-retrtace down?
[06:01] <pitti> gnomefreak: yes
[06:01] <pitti> gnomefreak: it hanged in dpkg --unpack for godknowshowlong
[06:01] <gnomefreak> ah ok and that is right tag right?
[06:01] <pitti> gnomefreak: I stopped it and I rebuild it with the latest fixes as we speak
[06:01] <pitti> gnomefreak: need-ppc-retrace
[06:01] <gnomefreak> ah ok
[06:01] <pitti> gnomefreak: we just had the same discussion with seb128 in #u-desktop
[06:01] <gnomefreak> oops :(
[06:02] <gnomefreak> sorry im not in there
[06:02] <pitti> gnomefreak, seb128, dholbach: so, let's agree to ppc vs. powerpc
[06:02] <gnomefreak> ppc
[06:02] <pitti> powerpc is the canonical one, but ppc tag was there first
[06:02] <gnomefreak> its easier to remember/type
[06:02] <dholbach> we have <dholbach> 5 ppc, 7 powerpc
[06:02] <dholbach> but i don't mind either way
[06:02] <seb128> I don't care either way
[06:03] <tepsipakki> mjg59: ok, thanks
[06:03] <pitti> ok, then let me remove the 'transform dpkg --architecture powerpc to ppc' special case and use powerpc
[06:03] <gnomefreak> truthfully me neither
[06:03] <dholbach> pitti: retrace both :)
[06:03] <seb128> pitti: WFM
[06:03] <gnomefreak> :)
[06:03] <pitti> dholbach: new special case :)
[06:07] <gnomefreak> ok what one won? powerpc?
[06:07] <pitti> gnomefreak: yes
[06:07] <gnomefreak> ok cool those are tagged
[06:07] <gnomefreak> its only feisty right?
[06:07] <pitti> if I am to choose, I'm all for fewer special cases
[06:07] <gnomefreak> i agree
[06:13] <tepsipakki> mjg59: um, there is a newer upstream (0.7.6.4), it should fix at least a gimp crasher.. I'll build that too
[06:13] <mjg59> tepsipakki: Good plan
[06:17] <pitti> gnomefreak, dholbach: powerpc retracer is back to live, better than ever
[06:18] <dholbach> pitti: you ROCK
[06:18] <gnomefreak> ty pitti 
[06:20] <_ion> pitti: Apparently there's actually something from nVidia with the PCI device ID 0000, and it only seems to exist on amd64 hardware, so it was not a mistake for the amd64 driver to list it.
[06:22] <Keybuk> _ion: nvidia seem to use that for subsystem ids of their bridges
[06:24] <_ion> Ok
[06:26] <Riddell> infinity: any idea what's happened to kde4libs 3.80.3-0ubuntu2 on amd64?  it hasn't hit the archive yet despite building 22 hours ago
[06:27] <cjwatson> probably stuck in failed-to-move
[06:27] <cjwatson> aye, I'll resurrect it
[06:29] <cjwatson> Riddell,infinity: done
[06:30] <Riddell> cjwatson: cool, thanks
[06:58] <PhinnFort> is the konsole-alpha (which allows real transparency in Konsole) planned to be included in feisty's version of konsole?
[07:04] <giangy> PhinnFort: ask in #kubuntu-devel
[07:04] <PhinnFort> ok
[07:06] <giangy> gh :)
[07:07] <_MMA_> Hello guys. Ubuntu Studio is in the process of building our disks. We have a custom sound theme that conflicts with ubuntu-sounds. I noticed that a depend of ubuntu-sounds was GDM and a depend of ubuntu-sounds is ubuntu-desktop. This means if we wanted to use the GDM from Ubuntu we would have to pull Ubuntu-desktop and all that comes with it.
[07:07] <_MMA_> As of now it looks like our only options to rebuild GDM without the ubuntu-sounds depend or see if the ubuntu-sounds depend could be removed from Ubuntu's GDM. Should I just post to the ML about this?
[07:11] <supervillain> I think you need to create your own sound-theme package, and replace ubuntu-sounds build-depends requirements
[07:11] <supervillain> I mean, gdm's requirements
[07:12] <_MMA_> We have. Thats not the issue. In order to use GDM it depends on "ubuntu-sounds". Then that pulls "ubuntu-desktop"
[07:13] <_MMA_> We arent using the "ubuntu-sounds" nor the  "ubuntu-desktop" packages.
[07:18] <zyga> mvo: hey
[07:18] <zyga> mvo: did you make any decisions?
[07:19] <BenC> pitti: ping
[07:19] <mvo> zyga: no, sorry. I'm busy with the release upgrader right now
[07:19] <pitti> BenC: gnip
[07:19] <zyga> mvo: okay, let's postpone this for +1 then
[07:19] <zyga> we'll do it properly by then
[07:20] <BenC> pitti: with the pci id lists produced, how does restricted-manager contend with multiple drivers matching a device?
[07:20] <pitti> BenC: the current scripts take care to assign it to the 'prefered' driver
[07:20] <pitti> BenC: e. g. if both nvidia and legacy support a given device, it is put into the nvidia list
[07:21] <BenC> pitti: Ok...is there a plan to handle upgrades from edgy->feisty for cases where they need to drop down to new-legacy, or is that going to be a release note sort of thing?
[07:21] <mvo> zyga: ok, this may mean we have to manually fix the gcc case
[07:22] <pitti> BenC: I discussed this with mvo, we might come up with a plan and update-manager/restricted-manager magic to handle this case
[07:22] <mvo> BenC: the release upgrader + release notes seems to be the only way to do this (at least that I can think of)
[07:23] <mvo> bug #96486 is about this problem
[07:23] <ubotu> Malone bug 96486 in update-manager "u-m should automatically install nvidia-glx-legacy if hardware requires it" [Medium,Confirmed]  https://launchpad.net/bugs/96486
[07:23] <BenC> anything I need to do to ease this, or just drop the new stuff in...any info you'll need from me once this gets into the archive?
[07:23] <zyga> mvo: not necessairly, as I said I have made full scan of main so if you agree we can just use 'old' current data for universe and use the new scanner for main, restricted and multiverse
[07:23] <zyga> the new scanner works fine with g++ case
[07:25] <mvo> BenC: what worries me is that people who not use the upgrader will be bitten by this. so solving this on a packaging level somehow would be really good, but I don't think that this is possible given the nature of the packages
[07:25] <mjg59> mvo: I can't think of any way for it to be possible
[07:25] <mjg59> We simply have no mechanism for expressing those dependencies
[07:25] <BenC> mvo: The only thing I know to do for this case would be to leave nvidia package as 9631, and force people with new cards to install nvidia-new or something
[07:25] <mvo> and we can't fold nvidia and nvidia-glx into one package of course
[07:25] <BenC> people who are not supported by 9631 wont have an upgrade issue
[07:26] <mvo> nvidia and nvidia-legacy of course
[07:26] <mvo> hm, renaming is a interessting idea, how feasible would this be?
[07:26] <pitti> mvo: it would be totally cool to merge both packages, and have the postinst detect which one is needed
[07:26] <BenC> we could have nvidia (9631), nvidial-legacy (7xxx) and nvidia-new (97xx)
[07:26] <pitti> BenC: that would only aggravate the problem in the future
[07:27] <mvo> pitti: that might be good though, then we have some more time to deal with the issue :)
[07:27] <BenC> the future looks bleak no matter how you slice it
[07:27] <mjg59> Mm. I guess installing and then dpkg-diverting stuff based on PCI ID would be possible
[07:27] <mjg59> If utterly insane
[07:27] <mvo> evil, but ...
[07:27] <BenC> mjg59: You thinking of including 9631+97xx in nvidia package and use magic to handle which one to use?
[07:28] <_ion> nvidia-glx Provides: driver-pci-10de-0040, driver-pci-10de-0041, ...  nvidia-glx-legacy Provides: driver-pci-10de-0020, driver-pci-10de-0021, ... ;-)
[07:28] <pitti> _ion: argh, no
[07:28] <_ion> pitti: Note the smiley
[07:28] <mjg59> BenC: Yeah
[07:28] <pitti> _ion: oh, right
[07:28] <pitti> now that l-r-m will ship the modaliases, postinst detection is relatively easy
[07:28] <BenC> that would handle the current case and make things easier in the future for sure
[07:29] <mvo> it sounds good too me if we can make it work reliable and it would help people upgrading in the more traditional way
[07:29] <BenC> we could just build the nvidia.ko module based on boot-up detecting in l-r-m-c init script
[07:29] <mvo> (which I expect will be a lot of people still)
[07:30] <_ion> benc: That would be neat.
[07:30] <BenC> we already link it on boot anyway, so adding detection and another stack of objects to link would be easy
[07:31] <pitti> BenC: and I guess the diversion magic in the postinst would become quite messy
[07:31] <mvo> BenC: is that enough? are/usr/lib/xorg/modules/libglx.so etc the same for nvidia-glx and -legacy?
[07:31] <BenC> pitti: with that method we don't need diversions
[07:31] <doko> do we have a common function, which prints out the name of the currently running video driver?
[07:31] <pitti> BenC: for the libGL.so stuff?
[07:32] <BenC> oh, libs...
[07:32] <pitti> doko: I didn't find any
[07:32] <BenC> we could use alternatives and set them in the script
[07:32] <pitti> doko: however, the question 'which is the video driver that you need' is relatively easy to answer
[07:32] <_ion> Perhaps /usr/lib/xorg/modules/drivers/drv_nvidia.so or whatever it was could be a link to one of drv_nvidia_{71xx,96xx,97xx}.so, and the link would be updated on bootup. The libGL stuff would be handled in same fashion.
[07:33] <BenC> _ion: right, using alternatives to keep it package friendly
[07:33] <pochu> heno: hi :) can you take a look at bug 97022? thanks ;)
[07:33] <ubotu> Malone bug 97022 in Ubuntu "dasher should be added to assistive technology preferences " [Undecided,Unconfirmed]  https://launchpad.net/bugs/97022
[07:33] <heno> yep
[07:36] <doko> pitti: just wanting to set some environment when I find fglrx or nvidia running; of course a lsmod | grep -E '^(fglrx|nvidia)' is a simple minded solution
[07:37] <pitti> doko: which should actually work, because you cannot modprobe them without xorg.conf using them
[07:38] <mvo> BenC: what bug should I subscribe too keep myself updated on this?
[07:39] <BenC> pitti: Ok, I'll try to have this nvidia combined package done by Friday (with a kernel upload) using alternatives to decide which one to enable
[07:39] <pitti> carlos: ah, new langpacks ready from today; so these should be good?
[07:39] <carlos> pitti: not yet, I still need to do some changes
[07:39] <pitti> BenC: they'll use the brand new modalias lists?
[07:39] <pitti> carlos: alrighty
[07:39] <BenC> pitti: Yes
[07:39] <pitti> cool
[07:39] <pitti> BenC: you rock!
[07:41] <BenC> pitti: I feel dirty :)
[07:43] <pitti> tkamppeter: ping
[07:43] <mvo> BenC: thanks a lot for taking care of the nvidia issue :) will you followup on ubuntu-devel? or should I do that?
[07:44] <heno> pochu: done (rejected)
[07:44] <_ion> benc: Does my patch seem to have any problems?
[07:44] <BenC> mvo: I already did
[07:44] <pochu> heno: thanks :)
[07:44] <BenC> _ion: what patch?
[07:45] <_ion> benc: The one i emailed. It generates the modules.alias override lists from the modules.
[07:45] <mvo> thanks!
[07:46] <wick2o> afternoon
[07:50] <BenC> _ion: Ah, haven't checked it closely yet, but will this evening
[07:50] <_ion> benc: All right.
[07:52] <asac> mdz: you want to keep translate application & get help online in firefox menu for feisty?
[07:54] <mdz> asac: most likely, yes.  at some point (perhaps UDS?) you ought to have an in-depth conversation with the Rosetta folks about what's necessary to get the server side worknig
[07:54] <mdz> asac: is there a compelling reason to remove it (something other than the server side not being ready yet)?
[07:54] <asac> afaik get help online is disabled for other apps as well now?
[07:56] <asac> We could disable it for now and enable it in an update in case rosetta supports firefox at some point
[07:56] <tkamppeter> pitti, pong
[07:58] <asac> mdz: main reason would be to reduce possible user confusion :)
[07:59] <tkamppeter> Some GNOME or XDG menu experts around here?
[08:00] <tkamppeter> Where are menu entries saved when the user changes something with the menu editor (System -> Preferences -> Main Menu)?
[08:01] <tkamppeter> Problem is bug 86893, the user seems to have a menu entry for HP Toolbox which is not from the HPLIP package.
[08:01] <ubotu> Malone bug 86893 in hplip "[Feisty]  Clicking on HPLIP Toolbox in gnome menu does nothing" [Medium,Fix committed]  https://launchpad.net/bugs/86893
[08:01] <zyga> tkamppeter: look for .local
[08:01] <mdz> asac: er, it is?  it should not be
[08:01] <zyga> tkamppeter: then check out what's there
[08:01] <mdz> asac: it certainly is enabled here; is it not working on your system?
[08:01] <asac> mdz: get help online?
[08:02] <mdz> asac: oh, you mean specifically Get help online.  that's been removed from the generic menu stuff, but the hardcoded apps still seem to have it
[08:02] <asac> mdz: so i think i can drop it as well for now :)
[08:03] <mdz> asac: there's no question about firefox and rosetta; it needs to be supported
[08:03] <mdz> asac: if it requires an update to enable it, I guess that's reasonable
[08:04] <mdz> since it's likely to have a security update at that point anyway
[08:04] <asac> ok ... so i will drop it for now. As soon as we have rosetta support we can switch it on.
[08:04] <asac> mdz: you can bet on that :)
[08:05] <tkamppeter> zyga, thank you very much.
[08:06] <zyga> tkamppeter: no problem
[08:07] <zyga> tkamppeter: you can find more information about this at freedesktop.org
[08:07] <zyga> this is defined there
[08:09] <tkamppeter> There is one problem (bug?) with the menu editor: If I only look into the properties of a menu entry without changing it, there is already a ~/.local/share/applications/*.desktop file created, which hides the system's *.desktop file and so prevents the user from getting access to an updated menu entry.
[08:10] <tkamppeter> pitti, are you still there?
[08:11] <pitti> tkamppeter: yes, partly
[08:12] <tkamppeter> pitt, you wanted to talk with me?
[08:12] <pitti> tkamppeter: can you please fix the file conflict in foo2zjs?
[08:12] <tkamppeter> pitti, the new foo2zjs which I gave you for upload does not contain mscompress any more.
[08:13] <pitti> tkamppeter: the current upgrade breaks because mscompress is installed as a dependency, but foo2zjs already ships that package
[08:13] <pitti> s/package$/file/
[08:13] <pitti> tkamppeter: i. e. mscompress is unpacked before foo2zjs is updated
[08:13] <fabbione> Unpacking mscompress (from .../mscompress_0.3-2_i386.deb) ...
[08:13] <fabbione> dpkg: error processing /var/cache/apt/archives/mscompress_0.3-2_i386.deb (--unpack):
[08:13] <fabbione>  trying to overwrite `/usr/bin/msexpand', which is also in package foo2zjs
[08:13] <tkamppeter> s/mscompress/msexpand/
[08:14] <fabbione> pitti: ah you were just saying the same
[08:14] <pitti> tkamppeter: the actual bug (shipping mscompress in /usr/bin by an unrelated package) is not reversible any more, so we now need a Conflicts/Replaces: on mscompress
[08:14] <pitti> fabbione: right
[08:14] <fabbione> i just noticed :)
[08:14] <pitti> tkamppeter: right, msexpand
[08:14] <tkamppeter> pitti, how can I solve this situation, I cannot change a package which is already on the user's systems?
[08:14] <pitti> tkamppeter: mscompress now needs to Conflicts:/Replaces: foo2zjs (<< the current version)
[08:16] <tkamppeter> This will make the update of mscompress trigger foo2zjs also being updated to the current version (the one without msexpand)?
[08:16] <pitti> tkamppeter: no, it won't force the upgrade, and it doesn't need to
[08:16] <pitti> tkamppeter: since mscompress and older foo2zjs really conflicted, this needs to be done anyway
[08:17] <pitti> tkamppeter: hm, wait; it doesn't really help either
[08:17] <pitti> tkamppeter: no, it does; (for upgrades which pull in mscompress)
[08:17] <pitti> mscompress can hardly be installed already, so that's fine
[08:24] <tkamppeter> So, pitti, I will set this conflict in the mscompress package then.
[08:24] <pitti> tkamppeter: thanks
[08:24] <pitti> this package could do with a rebuild anyway
[08:25] <tkamppeter> But, pitti, did you really move it into main already? My mirror still pulled it from Universe.
[08:25] <pitti> tkamppeter: today; mirrors usually need a day to catch up
[08:25] <pitti> mscompress |      0.3-2 | http://de.archive.ubuntu.com feisty/universe Packages
[08:25] <pitti> mscompress |      0.3-2 | http://archive.ubuntu.com feisty/main Packages
[08:27] <tkamppeter> pitti, this package is not maintained upstream any more, so it is only rebuilt if someone complains about something in it, and no one at Ubuntu is really the maintainer of this package.
[08:27] <tkamppeter> pitt, Germany seems to be faster than Portugal.
[08:27] <pitti> tkamppeter: NB that de.ubuntu is still universe, too
[08:28] <tkamppeter> Now I see, the other was archive..., the master server.
[08:31] <zyga> I just noticed that rsync to archive.ubuntu.com asks me to register my mirror
[08:32] <zyga> what is the purpose of registering a private mirror that is not publicly available?
[08:32] <zyga> (I cannot even give anyone a mirror URL)
[08:53] <mooey> which package has the nvidia restricted driver in it?
[08:54] <pitti> mooey: nvidia-glx (libraries) and linux-restricted-modules (kenerl module)
[08:55] <mooey> pitti: thanks
[09:03] <seb128> mooey: do you want to open a bug about a card not supported after upgrade? because there is already a zillion of those
[09:05] <Amaranth> please forward all nvidia bug reports to the black hole called nvnews forums ;)
[09:11] <mooey> seb128: no sir, just reassigning bugs out of 'Ubuntu' :-)
[09:11] <seb128> mooey: k
[09:11] <mooey> it was to do with resolutions not being supported in newer drivers
[09:27] <wick2o> I'm tring to update a ubuntu 6.06.1 install cd so i dont have to apt-get update at the end of the install...Is it as simple as downloading the new packages onto the cd and deleteing the old ones? perhaps updateing a symlink to the kernel dir to get an updated kernel as well?
[09:27] <wick2o> i already have a working remaster using the instructions on the wiki
[10:04] <gnomefreak> mvo_: you have a second?
[10:05] <gnomefreak> mvo_: was ubuntu-restricted-extras not built for i386?
[10:10] <mvo_> gnomefreak: it should be 
[10:11] <mvo_> gnomefreak: looks ok to me
[10:12] <gnomefreak> someone on i386 kernel gets the following error 
[10:12] <gnomefreak> Ubuntu restricted extras cannot be installed on  your computer type (i386)
[10:13] <mvo_> mpt: could you please proof-read http://paste.ubuntu-nl.org/12378/ ? its for peple that have nfs-imports but no nfs-common installed (that worked in edgy, dapper but does not work in feisty anymore). 
[10:13] <mvo_> gnomefreak: can you please run "sudo apt-get install --simulate ubuntu-restricted-extras" and tell me the output (pastebn) 
[10:13] <gnomefreak> its not my pc that had issues though
[10:14] <gnomefreak> when he gets back if im still here ill have him run it on his -386
[10:14] <mvo_> gnomefreak: the message in g-a-i is bad. I have seen the message when the real reason was that the package was uninstallable for some reason
[10:14] <mvo_> gnomefreak: thanks, that would be cool. he can mail me the output 
[10:15] <gnomefreak> ok he just got back
[10:15] <gnomefreak> it wont install on -generic for him either :)
[10:15] <mvo_> could someone please proof-read http://paste.ubuntu-nl.org/12378/  (and give good suggestions)
[10:16] <mvo_> gnomefreak: the output of the apt-get command would be good :)
[10:16] <gnomefreak> hes running it 
[10:18] <gnomefreak> mvo_: http://www.pastebin.ca/412604
[10:18] <gnomefreak> i havent looked yet
[10:19] <mvo_> gnomefreak: can you please ask him to put his /etc/apt/sources.list to a pastebin?
[10:19] <gnomefreak> i am
[10:19] <gnomefreak> hes going on about maybe us mirror doesnt have it and it should 
[10:20] <mvo_> gnomefreak: thats possible (unlikely, but possible) 
[10:20] <gnomefreak> hes using weird mirrors
[10:21] <gnomefreak> http://ftp.osuosl.org/pub/ubuntu/ didnt have it but us.archive.c does
[10:21] <gnomefreak> i wish people would use the archive mirrors
[10:21] <gnomefreak> it installs fine with us.archive.com sorry to bother you.
[10:21] <mvo_> gnomefreak: ok, that is settled then. thanks
[10:21] <gnomefreak> thank you
[10:34] <LaserJock> is there a channel for Ubuntu SoC stuff yet?
[10:36] <tepsipakki> what's wrong with launchpad?
[10:36] <tepsipakki> I mean
[10:36] <tepsipakki> it timed out
[10:36] <pochu> tepsipakki: down, #launchpad
[10:37] <LaserJock> tepsipakki: it's not feeling well
[10:37] <tepsipakki> of course
[10:37] <pochu> I have 500 and 502 errors everytime
[10:37] <tepsipakki> just when I should ask advice from upstream :)
[10:38] <kwwii> launchpad is down for a bit but they are on it
[11:01] <pochu> LP is back :)
[12:04] <JonRob> hi, I was interviewing Mark Shuttleworth the other day and he mentioned that there's a boot parameter that allows you to install ubuntu using only free software - but i can't find it documented anywhere, anyone know what it is?