[00:42] <amikrop> Hello. Please package the latest gnome-screensaver into the main repos, because it now has the bug of not being able to stop when playing fullscreen movies.
[00:42] <amikrop> A signal (I think --poke) does not work with the current version.
[00:42] <amikrop> But now there is a patch.
[00:42] <MsMaco> is a bug filed?
[00:42] <amikrop> I think.
[00:42] <superm1> yes, siretart was on that shortly before release
[00:42] <superm1> i'm not sure what happened of it though
[00:42] <MsMaco> hi superm1
[00:43] <superm1> hi MsMaco
[00:43] <ajmitch> superm1: it's in a PPA, I'm guessing he might look at getting it into -updates
[00:43] <amikrop> https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/428884
[00:43] <superm1> i sure hope so. it's certainly a very suboptimal experience right now
[00:44] <amikrop> I think this is the report. So, is the package ready to get available as an update?
[00:44] <MsMaco> superm1: im going to be attempting to make a dkms-based package soon, going off that UDW session you did a while back. if i get stuck, do you mind if i poke you?
[00:44] <superm1> MsMaco, it would be better if you did said poking tomorrow, but yes feel free
[00:45] <superm1> things are actually significantly easier nowadays too
[00:45] <superm1> and will only be improving now that debian is working on dh_dkms :)
[00:45] <mneptok> amikrop: is the person that fixes that bug the "Screen Savior?"
[00:45] <MsMaco> ah, i wont be attempting it today anyway. i have to migrate laptops so i can send this one for a replacement hinge. lid's almost detached :(
[00:46] <ajmitch> mneptok: puns like that should be shot
[00:46] <superm1> ah, then that would make it quite difficult to work with.
[00:47] <wgrant> Are the powerpc buildds still running Dapper?
[00:47] <MsMaco> will also make it difficult to test with since the hardware itd be enabling is on the to-be-fixed laptop :P gonna get bugabundo to test it for me ;)
[00:47] <amikrop> mneptok: :P
[00:49] <amikrop> superm1: excuse me, but I didn't get what it is going to happen with this case
[00:49] <amikrop> the package is ready and it is going to be moved on official updates?
[00:49] <superm1> amikrop, i've not followed the details here, but once the proper fix has been developed, it will be put into -proposed
[00:49] <ajmitch> amikrop: no, from reading the bug, the package is mostly ready but needs some further work
[00:49] <wgrant> s/will/may/
[00:50] <bluefox_> why is rhythmbox stupid?
[00:50] <superm1> people will need to verify that it works, and it will live there for about 2 weeks, and then go to updates if it fixes the problem properly without introducing regressions
[00:50] <ajmitch> wgrant: I think siretart plans to follow through with fixing it :)
[00:50] <MsMaco> bluefox_: because applications lack brains?
[00:50]  * bluefox_ saves a file into ~/Music/, rhythmbox sees the .part and then loses the file when the .part is lopped off and the file's called .mp3
[00:52] <amikrop> superm1: wow. would you suggest any workarounds until then?
[00:53] <iWolf> Is there any Community Council Members Here?
[00:57] <MsMaco> iWolf: pleia2 is signed on to freenode, but she's afk right now
[00:57] <iWolf> Anyone else
[00:57] <wgrant> iWolf: Why do you want a CC member?
[00:58] <iWolf> I need to ask a question
[00:58] <iWolf> Community Council Related
[00:58] <iWolf> Community*
[00:58] <lifeless> just ask it
[00:58] <lifeless> if we can't help we'll point you at the list
[00:58] <iWolf> Its about Teams
[01:04] <iWolf> Check this bug: https://bugs.launchpad.net/ubuntu/+bug/464710/
[01:04] <iWolf> Problem with distro?
[01:13] <jgoppert> I'm trying to repackage libjsw on my ppa. My first go at this. Anyways it doesn't work for karmic due to a gtk 1.2 dependency. I've got a quick fix that will work but I can't figure out dpatch. I try to modify debian/rules not to run the makefile in the jscalibrator directory and somehow after i create the patch and apply all patches it still tries to call the makefile in this directory. I think it is possibly that someone unp
[01:14] <MsMaco> "someone unp..." cutoff
[01:14] <jgoppert> I think it is possibly that somehow unpatch is being called by build and that somehow allows make to run on an unpatched debian rules file?? help??
[01:15] <ebroder> jgoppert: You can't patch debian/rules using dpatch. Just edit it directly
[01:15] <RAOF> And you're right: unpatch will be a part of the clean target, which will be run first in the build process.
[01:16] <jgoppert> ok thats kind of what i thought was going on, so i modify the original tarball? or how do i go about that
[01:17] <jgoppert> stupid question i know but i've tried that and have been very lost, do i do it in the patch to the original tarball? like the .gz.diff
[01:17] <RAOF> You don't modify the original tarball, you modify the packaging directly, then the source package contains your changes in the diff.gz.  This is better suited to #ubuntu-motu, by the way.
[01:17] <jgoppert> ok thanks for the help guys
[01:29] <jgoppert> they are kind of dead over there a motu, so anyways i figured out what i was doing and got libjsw packaged, i noticed that when uploading to the ppa i just give it my .changes file, but since there is no original tarball on my ppa do i need to upload that as well, the tarball is also not in karmic yet
[01:43] <ScottK> jgoppert: #ubuntu-motu really is more appropriate than here.
[01:54] <bluefox_> okay I'm going to ask this before going forward.
[01:54] <bluefox_> Did someone hard-disable IP forwarding in the Ubuntu kernel?
[01:57] <ion> Works in 2.6.31-14-generic-pae
[01:59] <bluefox_> nevermind I'm dumb
[01:59]  * bluefox_ writes a firewall rule for IP masquerading.
[02:00] <dtchen> not that I can see. /etc/sysctl.conf unsets the /proc bits by default, but that's fairly straightforward to enable.
[02:00] <bluefox_> Yeah, I had forgotten that I have to do PAT for this to work.
[02:47] <slangasek> pitti: is there some straightforward way that apport could check for "package is already installed and configured" as the error message, and file the bug against dpkg or apt or something instead of the individual package which isn't at fault?
[03:01] <lifeless> slangasek: probably; we can haz bug plz?
[03:01] <slangasek> done
[03:06] <MsMaco> lolspeak is an accepted dialect here?
[03:07] <StevenK> MsMaco: Sometimes.
[03:08] <emgent> ccheney`: ola ola
[03:08] <syn-ack> I know its waaaaaaaaaay OT but you guy have GOT to see this: http://www.youtube.com/watch?v=pAoqOCQlb0E
[03:08] <syn-ack> I'm still laughing
[03:16] <lifeless> MsMaco: selectively :)
[03:39] <laptopnenolod> so, umm
[03:39] <laptopnenolod> mountall has some weird bug where it hangs when ran on Xen
[06:57] <eboyjr> Does Quickly have a dev website besides Launchpad?
[06:58] <eboyjr> https://wiki.ubuntu.com/Quickly is good, nvm
[07:10] <dholbach> good morning
[07:24] <eboyjr> dholbach, good night
[07:25] <dholbach> hi eboyjr
[07:26] <eboyjr> Lol hiya.. It's night over here :P
[07:26] <dholbach> :)
[07:51] <pitti> Good morning
[07:51] <omani> g morning
[07:52] <pitti> MsMaco: no problem :)
[07:54] <pitti> slangasek: yes, should be easy; found the bug
[07:54] <pitti> (... report)
[08:00] <lifeless> anyone spent any time looking into the wrong kernel/initramfs after upgrading to karmic?
[08:01] <MsMaco> lifeless: dan's been looking
[08:01] <MsMaco> apparently users are prompted about keeping old config or using new one
[08:01] <MsMaco> and are choosing to keep the old config
[08:01] <MsMaco> and thus grub is not updated
[08:01] <lifeless> MsMaco: I wasn't prompted...
[08:01] <slangasek> pitti: ok - morning :)
[08:03] <pitti> slangasek, mvo: for disabling apport again after that dist-upgrade, would I do the conffile change in preinst or postinst? I think "preinst", to avoid conffile questions, right?
[08:03] <MsMaco> lifeless: nor was i. thats the confusing bit. no idea what determines who is prompted
[08:03] <mvo> I think preinst
[08:04] <pitti> since "no" is the default
[08:04] <slangasek> pitti: I don't think there's much difference, really - since the conffile shouldn't have changed between the previously installed version and the current one, there'd be no conffile prompt anyway
[08:04] <slangasek> preinst lets you correctly handle the exceptional case where the user has removed apport and is reinstalling it
[08:05] <pitti> slangasek: ah, true
[08:05] <slangasek> so preinst is a bit better :)
[08:05] <slangasek> lifeless, MsMaco: has anyone grabbed a copy of one of these "Don't install the maintainer's version" menu.lst files yet?
[08:05] <pitti> changing conffiles in maintainer scripts is new territory for me, so I better double-check
[08:06] <lifeless> slangasek: let me see if a backup was kept by update-grub
[08:06] <slangasek> update-grub keeps one backup
[08:07] <lifeless> MsMaco: whats the bug #
[08:12] <MsMaco> lifeless: there isnt a single bug. there's hundreds of bugs over the last 3 days that dtchen has triaged
[08:13] <MsMaco> of people with "no sound after upgrade" because they're using the wrong kernel
[08:13] <MsMaco> slangasek: no idea. dan may have
[08:13] <MsMaco> slangasek: he's asleep though
[08:14] <lifeless> MsMaco: there should be a single master bug or the failure to upgrade the menu.lst correctly
[08:14] <MsMaco> i guess...vast majority are being filed as audio bugs
[08:14] <MsMaco> there's also the caveat that some of these people, when told to use the right kernel...end up with no X
[08:15] <MsMaco> so they have to choose between 2.6.31-with-sound-but-no-X or 2.6.28-with-X-but-no-sound
[08:15] <MsMaco> (ive spent a lot of time on the forums the last few days)
[08:16] <slangasek> lifeless: well, they're each going to have to be looked at individually regardless, because many of these are likely to be "I changed menu.lst by hand, then update-grub did what I told it to" - there's no way to fix that other than using <blink> tags in the release notes, the menu.lst format is crap and this was a major reason for pushing grub2
[08:16] <slangasek> (too bad we didn't get grub2 by default on upgrade, this cycle)
[08:17] <lifeless> slangasek: sure, they have to be looked at
[08:18] <lifeless> slangasek: so, is the bug, 'if any menu.lst changes were made, we fail to run update-grub' ?
[08:18] <slangasek> no, not atall
[08:18] <lifeless> slangasek: then I totally misunderstood what you said
[08:19] <slangasek> we run update-grub, update-grub pops up a message informing the user that there's a conflict between their local changes and the changes the system wants to make, user clicks through "keep my changes" and ends up not getting entries for the new kernel
[08:19] <MsMaco> whereas it should be more of a merge?
[08:19] <slangasek> merge is one of the options the user didn't choose
[08:19] <lifeless> slangasek: ok. That doesn't match what happened to me.
[08:20] <slangasek> lifeless: gonna need more info, then
[08:20] <lifeless> slangasek: I upgraded, rebooted, no sound. Ran 'sudo update-grub', which did not prompt me at all. Rebooted, had sound (though initially muted).
[08:20] <slangasek> lifeless: and the kernel package was in 'installed' state?
[08:20] <lifeless> I have the backup menu.lst.
[08:20] <slangasek> hit me
[08:20] <MsMaco> oh. what dan saw in one comment looked more like "i upgraded, during upgrade i was prompted, i chose no, rebooted, and had no sound"
[08:20] <lifeless> slangasek: I can make no assertions about the kernel packages state at the time, i didn't think to check.
[08:21] <slangasek> lifeless: have you run update-manager or apt or dpkg since then?
[08:21] <lifeless> slangasek: I think so
[08:21] <slangasek> lifeless: ah; well, give me time stamps for the menu.lst files and full dpkg/apt logs as well, then :)
[08:21] <lifeless> slangasek: what bug do you want it on
[08:21] <lifeless> or should I make a new on?
[08:21] <lifeless> one?
[08:21] <slangasek> lifeless: feel free to open a new one on grub
[08:22]  * lifeless pops through to the other machine
[08:22] <slangasek> these other bugs apparently haven't been getting triaged over to the grub package yet, so I've only seen the barest trace of this issue
[08:22] <MsMaco> slangasek: look at pretty much any "alsa-driver" bug in the last week...
[08:23] <MsMaco> dan sent one of 'em to you two in email
[08:23] <MsMaco> he pasted a link to another comment along the same lines in here earlier, but i dont have scrollback
[08:24] <lifeless> 108576 could be a candidate
[08:24] <slangasek> *week*?  and no one thought to escalate it before the release?
[08:25] <MsMaco> he said he hit a couple of these weird "booting into the wrong kernel" ones back around beta but didnt notice the trend
[08:25] <slangasek> MsMaco: I have one thread in my mailbox about this starting Saturday, though lifeless isn't Cc:ed, so not sure if that's who you mean by "you two"
[08:25] <MsMaco> lifeless = robbie?
[08:25] <slangasek> MsMaco: hah, no
[08:25] <MsMaco> oh oops
[08:25] <JanC> according to crimsun some changes need a 2-5 min power down before they work because of crappy hardware, so that might also accidentally explain what lifeless saw...
[08:25] <slangasek> lifeless: 108576> unlikely to be the same bug, the ucf-based update-grub handling didn't exist back then
[08:26] <slangasek> lifeless: well.. might be the same as /your/ bug, but not the same as the other one I'm complaining about
[08:26] <lifeless> slangasek: kk
[08:27] <lifeless> slangasek: is apt/term.log useful?
[08:27] <MsMaco> i only heard about grub not updating when a week before release someone in #ubuntu+1 said current was -10 because his grub hadnt been updated since then
[08:27] <slangasek> lifeless: apt/term.log and dpkg.log both; I expect I'll need to cross-reference
[08:28] <lifeless> anything sensitive in term.log? its 0500
[08:29] <MsMaco> shouldnt be...its just the spew from apt-get install type operations
[08:29] <lifeless> no passwords ?
[08:30] <slangasek> right, I'm not aware of anything sensitive; they routinely get copied to bug reports without setting the 'private' bit
[08:30] <slangasek> passwords> God, I hope not
[08:30] <slangasek> that would be Special
[08:30] <lifeless> ok
[08:30] <MsMaco> haha
[08:31] <lifeless> slangasek: bug 470265
[08:31] <lifeless> bug 470265
[08:31] <lifeless> bug, ubottu fail..
[08:31] <lifeless> bug, ubottu fail..
[08:32] <lifeless> bug 470265
[08:32]  * lifeless shrugs
[08:32] <lifeless> slangasek: its there, ping me if you want more.
[08:32] <slangasek> intrepid to karmic, eh?
[08:32] <slangasek> lifeless: will do, thanks
[08:32] <lifeless> slangasek: jaunty.
[08:32] <slangasek> ok :)
[08:32]  * lifeless slaps himself
[08:32] <slangasek> lifeless: timestamps on menu.lst*?
[08:32] <slangasek> (need to know where to line it up with in the logs)
[08:33] <lifeless> slangasek: the backup appears to be open, copy data as opposed to 'cp -a' or 'mv'
[08:33] <lifeless> slangasek: the timestamp is unlikely to be useful, still - I've attached it
[08:34] <slangasek> right, ok; that limits its usefulness, but I should be able to get something out of it
[08:35] <slangasek> huh, the diff is telling
[08:35] <slangasek> update-grub has only successfully run once since the new kernel was unpacked
[08:35] <lifeless> right
[08:35] <lifeless> I just don't know *why* :)
[08:36] <slangasek> lifeless: grep postinst_hook /etc/kernel-img.conf ?
[08:38] <lifeless> zip
[08:38] <slangasek> we really ought to put those hooks in /etc/kernel/postinst.d instead of relying on the installer's setup to have infinite shelf life
[08:38] <lifeless> nada
[08:38] <lifeless> nothing
[08:38] <slangasek> lifeless: that's it, then.  On a normal system, you should see 'postinst_hook = update-grub'
[08:38] <lifeless> I haven't touched kernel-img.conf
[08:38] <slangasek> lifeless: when was this machine installed, and how?
[08:38] <lifeless> so the bug is 'somehow kernel-img.conf is missing postinst_hook'
[08:39] <slangasek> did you ever have lilo on it instead of grub?
[08:39] <lifeless> no, its my new i7 desktop
[08:39] <slangasek> please post your full kernel-img.conf to the bug
[08:39] <lifeless> which dates it
[08:41] <pitti> slangasek, mvo: apport fix committed (see bug followup, and http://bazaar.launchpad.net/%7Eubuntu-core-dev/ubuntu/karmic/apport/ubuntu/revision/1570); quick eyeballing appreciated
[08:41] <lifeless> slangasek: done, with datestamp
[08:41] <lifeless> slangasek: which is either the jaunty cd datestamp, or when I installed the machine.
[08:44] <slangasek> lifeless: ack, thanks
[08:44] <lifeless> slangasek: I'm quite sure I installed jaunty fresh on it
[08:44] <slangasek> hmm, disturbing thought that all jaunty installs from liveCD might have this problem :/
[08:44]  * slangasek will start poking at the livefs
[08:44] <lifeless> its certainly never had lilo on it
[08:45] <slangasek> right
[08:45] <lifeless> Was it a livecd install? I think so. dmraided though, so I may have manually partitioned
[08:45] <lifeless> theres probably a log somewhere ;)
[08:46] <lifeless> indeed, installer logs are present if you want them
[08:46] <slangasek> lifeless: oh awesome, please attach those also :)
[08:46] <slangasek> (anyone wandering by this bug is going to be completely confused by the stack of attached files)
[08:46] <lifeless> 21 april is the deb timestamp
[08:47] <lifeless> slangasek: are passwords in the installer logs?
[08:49] <slangasek> pitti: $1 check is superfluous but not wrong; bdmurray pointed out on the bug that release-upgrader 0.126.5 would also have this bug, so best to grep for 0.126.[56].  Otherwise, looks ok to e
[08:50] <slangasek> me
[08:50] <slangasek> lifeless: nope
[08:50] <slangasek> (man, what do you take us for :)
[08:50] <pitti> slangasek: ah, thanks
[08:51] <slangasek> oh hey, I don't have to download a copy of the jaunty ISO to check this, do I
[08:52] <slangasek> the bandwidth of me walking across the house and back is awesome
[08:53] <pitti> slangasek: I just noticed that apport doesn't upgrade with being disabled (the upstart job failed, which causes postinst to fail); I'll file a bug and fix this first
[08:54] <slangasek> pitti: meep; methinks we should have a session on writing upstart jobs at UDS
[08:56] <pitti> slangasek: oh, nevermind; it's the new lucid debhelper apparently
[08:57] <slangasek> oh, hmm
[08:57] <pitti> it adds an additional invoke-rc.d call
[08:57] <slangasek> mismerge?
[08:57] <mdke> slangasek: pitti: I wonder if you have any ideas on the cause of bug 464037 - we have two duplicates (from Dell machines) and I can confirm it myself when installing gnome-user-guide-gu. I've read through the build log but can't figure it out, I wonder if it is something to do with pkgstriptranslations. Not urgent, but if you have any bright ideas...
[08:57] <lifeless> slangasek: I've written a good summary I hope
[08:57] <slangasek> pitti: oh, you merged it ;)
[08:58] <pitti> slangasek: well, most of the upstart bits were committed to debian, so apparently there was an eror somewhere; will look into this after I'm done with this SRU
[08:58] <lifeless> MsMaco: this bug is the master, if you have other bugs where just upgrade-grub fixed the problem (no prompts being asked, just-worked), please feel free to close them as dups to this bug
[08:58] <slangasek> pitti: no, only *some* of the upstart bits were committed to Debian, then Keybuk extensively modified debhelper again after I'd negotiated that patch with joeyh
[08:59] <lifeless> slangasek: the concept of this being every or even  many livecd installs is scary-as
[08:59] <slangasek> so the chance of a mismerge is actually quite high
[08:59] <pitti> slangasek: yeah, there were some bits which weren't accepted, I merged those
[09:00] <pitti> especially the --only-upstart bits
[09:00] <slangasek> lifeless: indeed - but it gives us a nice way to clean up all the bug reports at once
[09:00] <slangasek> pitti: well, it's not that they weren't accepted, it's that they haven't been submitted... anyway, I guess you'll be able to sort it now that you're looking at it :)
[09:00] <slangasek> [281264.038921] SQUASHFS error: Major/Minor mismatch, older Squashfs 3.1 filesystems are unsupported
 right, how do I mount a jaunty squashfs :P
[09:01] <MsMaco> lifeless: alrighty
[09:02] <lifeless> slangasek: someone claimed that the initramfs could be stale too, but I haven't seen data to corroorate that
[09:03] <lifeless> s/oo/obo
[09:03] <slangasek> that'd be a separate bug, and should only ever happen when the kernel package has failed to finish installing
[09:03] <MsMaco> yeah i saw one person in #ubuntu where initramfs was wrong after an update-grub. the initramfs existed, so i just told them to edit it manually and it worked
[09:03] <MsMaco> er edit menu.lst manually
[09:05] <MsMaco> slangasek: inside a jaunty vm?
[09:05] <slangasek> MsMaco: no virtualization capabilities here
[09:05] <slangasek> if I had a jaunty vm, I wouldn't need to loopback mount the CD, I could just... boot the CD :)
[09:05] <slangasek> (which is what I'm going to end up doing as soon as I wrap this email)
[09:06] <MsMaco> i can look if you tell me what to look for
[09:06] <wgrant> cjwatson, slangasek: How important is v3 source package support before 2009-12-05?
[09:07] <slangasek> MsMaco: I want the contents of /etc/kernel-img.conf from inside the livefs
[09:07] <slangasek> MsMaco: specifically, I'm comparing it with http://launchpadlibrarian.net/34936461/kernel-img.conf
[09:07] <MsMaco> ok
[09:08] <pitti> wgrant: we'll start the syncs/merges from Debian in the next days, so if we need it at all, we need it soon, I guess
[09:10] <slangasek> wgrant, pitti: well, I wonder how quickly the new formats are going to be adopted - so far we just have buxy's one test package, right?
[09:10] <slangasek> and if we're autosyncing from testing, that's 10 days grace period
[09:10] <wgrant> Right. It's unclear exactly how quickly it will be adopted.
[09:10] <pitti> slangasek: apport waiting in karmic/unapproved now
[09:11] <pitti> wgrant: right, that's the "if we need it at all" (for lucid) bit
[09:11] <pitti> I haven't seen such a package yet
[09:11] <slangasek> pitti: ok; may not get a chance to approve that 'til morning
[09:11] <wgrant> pitti: There is only one in the Debian archive at the moment.
[09:11] <slangasek> pitti: there's one test package in the archive; I know buxy is chomping at the bit to be able to start uploading them :-)
[09:11] <pitti> if it's only two or so, we can easily rebuild them on our side for lucid
[09:11] <wgrant> But dak only gained support for it last week.
[09:13] <\sh> moins
[09:14] <MsMaco> lifeless: wait where's that bug number?
[09:15] <MsMaco> 470265?
[09:15] <lifeless> bug 470265
[09:15] <lifeless> oh wow ubotto fail
[09:15] <lifeless> or hmm
[09:15] <lifeless> no slangasek trampled on my edit
[09:15] <lifeless> it should say jaunty
[09:15] <slangasek> heh
[09:15] <slangasek> thank AJAX :)
[09:16] <lifeless> hell no
[09:16] <lifeless> least you didn't edit the description
[09:16] <lifeless> :)
[09:16]  * slangasek grins
[09:16] <\sh> oh that bugged me too...and I thought I messed my installation (intrepid -> jaunty -> kernel update fail)
[09:17] <MsMaco> lifeless, slangasek: ok, livecd's /etc/kernel-img.conf attachd to bug
[09:17] <MsMaco> lifeless: it says jaunty when i look in firefox in the vm
[09:18] <slangasek> MsMaco: thanks
[09:18] <MsMaco> np
[09:18] <lifeless> MsMaco: yes, cause I just fixed it ;)
[09:18] <slangasek> lifeless: was yours i386 or amd64?
[09:18] <lifeless> amd64
[09:18] <slangasek> ok
[09:19] <slangasek> (probably doesn't matter, just wondering which livefs build logs to look at)
[09:19] <slangasek> somebody want to check the kernel-img.conf in a *karmic* livefs?
[09:20] <MsMaco> booting i386 karmic...
[09:21] <slangasek> no mention of kernel-img.conf anywhere in the livefs build log for jaunty final, so not sure what actually generates the one that's there in the livefs - the kernel package, maybe
[09:25] <slangasek> well, when ubiquity calls grub-installer it should unconditionally add its hooks to /etc/kernel-img.conf
[09:26] <MsMaco> still need the karmic live cd's /etc/kernel-img.conf?
[09:27] <lifeless> slangasek: what one in the live fs ?
[09:27] <slangasek> MsMaco: might be nice for reference
[09:27] <lifeless> MsMaco: yes, I'd say that that is a useful thing.
[09:27] <MsMaco> ok
[09:27] <slangasek> lifeless: the /etc/kernel-img.conf
[09:27] <lifeless> slangasek: not the file, the hook :)
[09:27] <lifeless> http://launchpadlibrarian.net/34939246/kernel-img.conf - no hook
[09:28] <lifeless> I wonder if it might be an ordering problem
[09:28] <lifeless> grub-installer before /etc/kernel-img.conf exists
[09:29] <lifeless> if grub-installer is depending on dpkg hooks to run lazily at the right time
[09:29] <buxy> slangasek: everybody can upload new packages using new formats, I did logitee-tools, quilt itself and ftplib
[09:29] <slangasek> lifeless: not in the karmic version of grub-installer; checking jaunty now
[09:29] <slangasek> buxy: quilt> bah :)
[09:31] <slangasek> buxy: anyway, obviously everybody /can/ upload packages in the new format, I just have no feel for how many /will/ do so or how quickly
[09:31] <buxy> slangasek: that depends also whether I make dpkg-source produce new formats by default or not :)
[09:31] <slangasek> ugh
[09:31] <slangasek> well, that would neatly screw Ubuntu over until LP supports v3, then
[09:32] <buxy> it has been accepted as release goal, and there aren't that many packages failing to build with new formats, see http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=hertzog@debian.org;tag=3.0-quilt-by-default
[09:33] <slangasek> it's been accepted as a release goal to make it the /default/?
[09:34] <slangasek> that's not mentioned on http://release.debian.org/squeeze/goals.txt or http://wiki.debian.org/ReleaseGoals/NewDebFormats
[09:35] <buxy> "Have all packages in the archive buildable using the new source package formats." => this is my prerequesite to enable dpkg-source to produce new format by default
[09:36] <slangasek> well, yes, but that doesn't mention anything about actually /making/ it the default for squeeze...
[09:37] <buxy> well, the other half is my responsibily as dpkg (co-)maintainer, I can surely make that decision? and it's not like I haven't made it clear since quite some time
[09:39] <lifeless> buxy: changing the default will affect every derivative distro
[09:39] <slangasek> obviously if we're having this conversation, it wasn't clear to me that you meant to make it the default for squeeze
[09:39] <slangasek> it is your decision; I'm informing you of one side effect of this decision
[09:39] <buxy> but it needs some fine-tuning still, I will probably solicit some input
[09:40] <buxy> slangasek: I'm still not sure we can make it for squeeze, it has taken much longer than what I hoped
[09:40] <Whoopie> jdong: thanks for ACKing bug 427217. What are the next steps?
[09:55] <al-maisan> EOCHAN
[10:02] <buxy> slangasek: is there a launchpad ticket requesting support of the new format in the ubuntu infrastructure?
[10:02] <slangasek> wgrant: ^^ ?
[10:03] <wgrant> Bug #293106
[10:03] <wgrant> The code is pretty much done.
[10:03] <wgrant> But it is very very awkward timing.
[10:05] <buxy> thanks, I subscribed to it, if you have questions just ask
[10:07] <slangasek> MsMaco: well, so far my sampling of recent alsa-driver bugs yields me only reports from people who /are/ running the karmic kernel
[10:09] <slangasek> hmm, a lot of checkbox bugs
[10:22] <fatal^> buxy: debian bug #485137 should be fixed in unstable (sometimes during the 2.27.x experimental era).... would be nice if you could confirm that (and tag the bug appropriately)...
[10:24] <buxy> fatal^: the recipe to reproduce is easy, why don't you do it yourself?
[10:24] <MacSlow> tseliot, yeah... let's hope that "special driver" is an OpenSource one
[10:24]  * tseliot nods
[10:25] <fatal^> buxy: no time/interest/access_to_suitable_system at the moment. will probably forget it, so I thought it might be slightly better to poke you about it now.
[10:25] <MacSlow> tseliot, th GPU-core in the GMA500 isn't too bad... has geometry-, vertex- and fragment-shaders in hw
[10:25] <buxy> fatal^: it might be better to record that information in the BTS
[10:26] <buxy> I don't have time for such individual request, if I do anything like that it will be automated over all the bugs I submitted :)
[10:26] <tseliot> MacSlow: yes, it doesn't draw too much power and has hardware HD video decoding
[10:26] <tseliot> so it's good on the paper
[10:27] <MacSlow> tseliot, afaik the same GPU-core also drives the iPhone's screen
[10:27] <tseliot> power-VR?
[10:27] <MacSlow> tseliot, yes
[10:28] <tseliot> let's cross our fingers and wait then :-)
[10:43] <SandGorgon> is Ubuntu going to follow XDG desktop specifications (http://standards.freedesktop.org/basedir-spec/basedir-spec-0.6.html) - for config file locations ?
[12:19] <pitti> SandGorgon: we try, anyway; but of course there's still a lot of old upstream software which doesn't
[12:42] <lucas> gah. ruby1.8 needs a SRU. The version in unstable/testing fixes several major bugs, but nobody noticed :(
[12:43] <soren> Do we have an expected ETA for when Lucid opens? Do we expect it to be this week?
[12:51] <mvo> soren: rumors in #ubuntu-release say soon, almost certainly this week
[12:56] <soren> mvo: Cool. Thanks.
[13:24] <pitti> soren: still waiting for a debhelper fix to publish, then I think we're ready
[13:24] <pitti> soren: feel free to upload already (it'll land in the queue)
[13:43] <tseliot> MacSlow: http://www.phoronix.com/scan.php?page=news_item&px=NzY2Mg
[13:52] <soren> pitti: Great. Thanks!
[14:46] <engla> DktrKranz: thanks for your work on Kupfer. I think next version is going to default to install in DATADIR
[14:46] <engla> (install its python package there). I think it's smarter anyway, and as long as the binary is in the $PATH, there is no trouble to find the package
[14:46] <DktrKranz> yup :)
[14:46] <engla> but it is strange for a linux package to be installed all in one directory like that
[14:49] <DktrKranz> well, it's one of the features provided by python packaging, in case someone ever wants to package some "kupfer" module, and make it available system-wide, we're safe
[14:59] <dholbach> https://wiki.ubuntu.com/UbuntuOpenWeek kicking off in 1 minute in #ubuntu-classroom
[15:11] <mantiena> Hi all
[15:13] <mantiena> I've noticed lots of identifical bugreports about jaunty->karmic upgrading problems when users have ttf-mscorefonts-installer (same bug occurs when also during installation ttf-mscorefonts-installer package, but not so often), maybe someone from Ubuntu developers can assign bug #464422 to the right person and increase importance ? Every day since karmic release about 10 identifical bugs are reported about this problem :(
[15:13] <mantiena> This problem appears because ttf-mscorefonts-installer always tries to download fonts from internet servers without asking if user wants to do this and returns an error if there are no access to the fonts download locations
[15:59] <hdon> hi all. does the libevent-dev package even work at *all*? it seems to contain errors :(
[15:59]  * hdon wonders if it has been tested
[16:15] <nxvl> james_w`: ping
[16:15] <nxvl> james_w`: i'm trying to bzrize a package, but i can't find any documentation in https://wiki.ubuntu.com/DistributedDevelopment/Documentation/
[16:15] <james_w`> hi nxvl
[16:16] <nxvl> james_w`: i remember that with svn there was a way to do that from the dsc
[16:16] <james_w`> nxvl: a new package?
[16:16] <james_w`> oh
[16:16] <james_w`> bzr import-dsc
[16:16] <nxvl> james_w`: yup
[16:16] <nxvl> james_w`: awesome, will check the manpage for that, thank you
[16:16] <james_w`> bzr help import-dsc will get you started
[16:16] <james_w`> also file:///usr/share/doc/bzr-builddeb/user_manual
[16:17]  * nxvl HUGS james_w` 
[16:23] <kklimonda> james_w`, will there be a way in future to work completely in VCS? Download upstream source though svn or git, merge with package branch and release ready source package?
[16:24] <Laney> will need to run autogen.sh or similar
[16:24] <kklimonda> Laney, i know, i know
[16:24] <james_w`> kklimonda: yes
[16:25] <Laney> I once tried to package f-spot based on the git tags, then decided it was too much work
[16:31] <joaopinto> is /etc/rc.local expected to be called on Karmic boot ?
[16:42] <_lemsx1_> the lsb-base package on Ubuntu introduces /etc/lsb-base-logging.sh which is supposed to be provided by sysadmins and other packages wanting to change the way init functions are called. this is inconvenient for others
[16:43] <_lemsx1_> there are 4 new bugs that should be merged with this one LP #328089
[16:44] <_lemsx1_> now that karmic is out, i want to get this resolved some how...
[17:02] <feisar> I know this is officially not the right place to ask for support but the normal channels seem clueless. How do I add a new user with an encrypted home? --encrypt-home does not work in 9.10, it did in 9.04
[17:14] <bdmurray> pitti: Do you know why apport-kerneloops reports are still coming in about karmic?
[17:14] <pitti> bdmurray: unfortunatly kerneloops wasn't disabled before release; james_w wanted to look into this AFAIR
[17:15] <bdmurray> pitti: we are getting lots and lots of these
[17:18] <james_w> pitti, bdmurray: just uploading to -proposed now
[17:18] <bdmurray> james_w: is there a bug number so we can get it verified quickly?
[17:18] <bdmurray> sbeattie: ^
[17:18] <pitti> james_w: thank you!
[17:20] <james_w> bug 471137
[17:52] <zul> so umm I know this has been asked before but is lucid open yet?
[17:53] <ogra> zul, https://wiki.ubuntu.com/LucidReleaseSchedule
[17:53] <ogra> give it till end of the week
[17:54] <zul> ogra: thanks
[18:13] <jdong> pitti: potential verification-failed on bug 415766; ebroder's latest comment?
[18:15] <ebroder> jdong: I'll admit that I have no idea how that interacts with dkms, which you may care about more than module-assistant
[18:21] <hoonteke> is there a way to mirror an ubuntu via bittorrent?  I don't mean just offering bittorrent, I mean saving some mirror's bandwidth by utilizing bittorrent to download it my private mirror.
[18:33] <jdong> ebroder: yeah I have no idea either
[18:33] <ebroder> I guess I could go poke at that for a second
[18:33] <MsMaco> if it should be -1 not 0.1, jdong made me do it!
[18:33] <MsMaco> s/-//
[18:34] <ebroder> No, no - it should definitely 0.1
[18:34] <ebroder> It's a question of ubuntu0.1 or +ubuntu0.1
[18:34] <jdong> MsMaco: no, it's the - vs +
[18:34] <MsMaco> ah ok
[18:34] <jdong> + is like the professional edition ;-)
[18:34] <MsMaco> :P
[18:35] <ebroder> Anyway, I'll poke as soon as I finish dealing with the fallout of bug #430224 for my build servers
[18:35] <jdong> yay ubottu!
[18:36] <ebroder> *eyeroll* This is the "initctl in a chroot does the wrong thing" bug
[18:36] <ScottK> pitti: I was wondering if you could take a look at Bug #466028.  I think it may be a post-update regression (I don't recall seeing the error before).
[18:36] <jdong> heh has anyone gotten anything amusing to happen as a result of that?
[18:36] <ebroder> jdong: I don't think anything amusing will happen; just annoying errors. Although I can certainly see it causing problems for Debathena's login chroots at some point down the line
[18:37] <jdong> ebroder: yeah, I'd imagine
[18:45] <ebroder> jdong: I can't tell for sure, but it looks like dkms tracks modules outside the package manager. If that's true, the version number wouldn't matter if you're using dkms, but it still would if you use the module-assistant
[18:46] <jdong> ebroder: now that you mention it, yeah, it'd purge the dkms modules and re-build them during postinst
[18:46] <jdong> not a big deal there
[18:46] <ebroder> (My perspective is biased, because Debathena is still distributing module-assistant-built modules for everybody)
[18:47] <jdong> not biased at all; no reason why not to do a 1-character regression correction :)
[19:45] <lantizia_> I'm very much sufficiently *ISSED off... whose bright idea was it to have GDM restart OVER AND OVER AND OVER if it fails to start X?
[19:45] <lantizia_> Jesus didn't this thing go under any testing?
[19:46] <lantizia_> Dependant on name server chosen, network-manager is screwed at name resolution too
[19:47] <ebroder> lantizia_: I don't know anything about your problem, but a word of advice from the other side: I have very little desire to help someone who starts their bug report by ranting about how incompetent I am
[19:47] <lantizia_> Then don't brand something as stable just because 6 months have passed
[19:48] <jdong> that's a very helpful attitude
[19:48] <lantizia_> No it isn't... but I'm not using a very helpful OS either
[19:48] <lantizia_> I don't argue that I'm being a cock right now but it's irritated me greatly
[19:48] <jdong> well sorry to hear that
[19:48] <jdong> but it's unlikely this approach will yield any productive results
[19:49] <lantizia_> And #ubuntu is full of people who have silly questions like how to delete a file, or run a windows games... the odd's of having any real dialogue to work through issues is nill
[19:56] <ScottK> Doesn't make this a support channel
[20:01] <MsMaco> ebroder++
[20:38] <mdeslaur> Riddell: I have some qt4-x11 packages for intrepid and jaunty in https://launchpad.net/~ubuntu-security-proposed/+archive/ppa/+packages
[20:38] <mdeslaur> Riddell: if you want to try them out
[20:41] <Riddell> mdeslaur: ok, I'll try them in a couple of hours
[20:41] <mdeslaur> Riddell: cool, thanks
[20:41] <mdeslaur> Riddell: it's webkit security updates, so anything that uses qt4-webkit
[20:41] <mdeslaur> Riddell: no rush
[21:35] <davidroderick> I ran out of disk space and so I started to apt-get remove stuff I found in /var/lib/dkpg/available.  This broke my system in subtle ways.  How should I have found a list of end packages?
[21:36] <chrisccoulson> siretart` - there?
[21:37] <davidroderick> I think that I might trash the os and move to gentoo
[21:49] <siretart> chrisccoulson: yes?
[21:49] <chrisccoulson> siretart - did you do any work on the screensaver/vlc issue?
[21:50] <chrisccoulson> i was looking at the totem source earlier, and it contains the same hackery (simulating fake keypresses) as gnome-session for preventing the session from going idle
[21:50] <siretart> chrisccoulson: nope. I've just digged out the patch from the gnome bugzilla and prepared a ppa package
[21:50] <RAOF> davidroderick: This isn't really the channel for that question, and it's not entirely obvious what you're trying to ask, but I think "deborphan" is the answer.
[21:51] <siretart> chrisccoulson: but I've read a bit about xlib. There is this API called XResetScreenSaver. Why can't we use just that API?
[21:52] <chrisccoulson> siretart - not sure about that
[21:53] <siretart> btw, how do KDE applications prevent the screensaver from activating?
[21:54] <chrisccoulson> siretart - i'm not sure about that either. in gnome, applications must prevent the session from going idle somehow. once the session goes idle, gnome-screensaver will display the screensaver after a preset time
[21:55] <siretart> btw, I found that API from this message: http://lists.freedesktop.org/archives/xdg/2009-May/010461.html while googling around..
[21:56] <chrisccoulson> siretart - interesting. i'll have to try and figure out what that does on the server-side
[21:56] <chrisccoulson> basically, we just need a way of resetting the IDLETIME counter
[21:57] <chrisccoulson> which is reset automatically when you move the mouse / press keys etc
[21:58] <siretart> hm. the documentation XSetScreenSaver(3) fits perfectly to this description...
[22:02] <Riddell> siretart: I believe they insert fake key events using libxtest
[22:06] <chrisccoulson> Riddell - that's also what some gnome apps do as an alternative to using the inhibit interface
[22:06]  * siretart reads the xlib specification, page 195, section 9.7. Controlling the Screen Saver.
[22:10] <chrisccoulson> siretart - remember though that gnome-screensaver disables the built-in X screensaver anyway
[22:11] <chrisccoulson> just to complicate things ;)
[22:11] <chrisccoulson> it's all very confusing :-/
[22:12] <siretart> chrisccoulson: it does?! why the heck is this?
[22:12] <siretart> btw, what *is* the 'built-in X screensaver' anyway?
[22:13] <chrisccoulson> siretart - the built in X screensaver is all controlled server-side. ie, it takes care of the timeout and screen blanking itself
[22:14] <chrisccoulson> but gnome-screensaver disables this and takes control of the screen itself
[22:14] <chrisccoulson> and the screen blanking is handled by gnome-screensaver too
[22:14] <siretart> hm. I guess I need to do way more research here
[22:14] <chrisccoulson> at least that's my understanding of it
[22:15] <siretart> chrisccoulson: you said that one cannot assume that the MIT-SCREEN-SAVER extension is always available. is that correct?
[22:15] <siretart> do you know of examples when it is not available?
[22:15] <chrisccoulson> the built-in X screensaver probably doesn't allow a nice fade, and probably provides no way of drawing the unlock dialog too
[22:16] <siretart> but it defines a documented and fine API for locking/unlocking/inhibiting the screen
[22:16] <chrisccoulson> siretart - i've no specific examples of when the extention might not be available, but i've had to debug several issues recently where people have made invalid assumptions about the presence of various X server features.
[22:16] <siretart> wouldn't it be great if g-s-s would just handle these xlib defined notifications just as one would expect it?
[22:17] <ajmitch> siretart: wouldn't it be great if no software had bugs? :)
[22:17] <chrisccoulson> and regardless of whether it is available or not, you must always make a call to XScreenSaverQuesryExtension to properly initialize some client-side parameters
[22:17] <chrisccoulson> else behaviour is unpredictable
[22:17] <chrisccoulson> it would be great if software had no bugs:)
[22:18] <chrisccoulson> but then i'd have nothing to do...
[22:18] <chrisccoulson> ;)
[22:18] <siretart> ajmitch: sure, but we are not (yet) able to identify the defect exactly
[22:19] <ajmitch> I know, I was reading through that bug. It's a shame that screensavers are still a complicated field
[22:20] <chrisccoulson> they are too complicated. i knew nothing about gnome-screensaver until i had to debug a separate issue 3 weeks or so ago
[22:21] <chrisccoulson> i had to spend several evenings trying to figure out how it worked ;)
[22:26] <siretart> chrisccoulson: re: XScreenSaverQueryExtension - you're right, this is even documented in XScreenSaver(3)
[22:26] <chrisccoulson> siretart - this is also the case for any X extension request
[22:27] <chrisccoulson> i think the call is needed for obtaining the major op code associated with the extension
[22:45] <siretart> chrisccoulson: ah, I think now I understand the issue. g-s-s has moved away from libxscreensaver (the MIT-SCREEN-SAVER) extension to directly query the IDLETIME sync counters in order to make the fading out effect interruptible
[22:45] <siretart> is this correct?
[22:45] <chrisccoulson> siretart - almost. it's actually gnome-session which queries the IDLETIME counter
[22:45] <chrisccoulson> gnome-screensaver just listens to the session idle status from gnome-session
[22:47] <siretart> okay, but I assume applications should still be able to use libxscreensaver to reset the IDLETIME counter and thus inhibit g-s-s
[22:47] <siretart> or even just plain libx11
[22:49] <chrisccoulson> siretart - the IDLETIME counter is accessible via the SYNC extension
[22:49] <chrisccoulson> but it is not writable by any clients
[22:50] <chrisccoulson> that seems to be the issue
[22:51] <siretart> chrisccoulson: perhaps XResetScreenSaver can be used to reset that counter?
[22:52] <siretart> or rather: make XResetScreenSaver(3) reset the counter?
[22:52] <chrisccoulson> siretart - i don't know. perhaps it does that indirectly already?
[22:54] <siretart> chrisccoulson: what library exposes the SYNC extension?
[22:54] <siretart> Xext?
[22:55] <chrisccoulson> siretart - yes, i think that's the one
[22:57] <siretart> okay, that seems to be documented here: http://www.xfree86.org/current/synclib.pdf
[23:06] <siretart> chrisccoulson: do we have client programs to query the xsync counters, or do I have to hack something up myself?
[23:07] <chrisccoulson> siretart - gs-idle-monitor.c in gnome-session has some examples
[23:08] <chrisccoulson> siretart - that file also contains an example of how to reset the counter
[23:09] <chrisccoulson> which is copied directly from totem too
[23:09] <siretart> I'm just reading that file right now
[23:09] <bluefoxicy>   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
[23:09] <bluefoxicy>  4576 bluefox   20   0 1307m 117m  22m R  188  3.2   2696:39 pidgin
[23:09] <bluefoxicy> htf can pidgin use 200% CPU
[23:09] <bluefoxicy> to idle
[23:09] <jdong> hahaha :)
[23:10] <bluefoxicy> it's been doing this a lot too
[23:10] <chrisccoulson> bluefoxicy, empathy?
[23:10]  * chrisccoulson runs
[23:10] <bluefoxicy> empathy is crap
[23:10] <chrisccoulson> hmmm
[23:10] <slangasek> bluefoxicy: not helpful
[23:10] <siretart>         /* FIXME: is there a better way to reset the IDLETIME? */
[23:11] <siretart> hrmpf
[23:11] <chrisccoulson> siretart - that's the bit i referred to in the bug report
[23:11] <bluefoxicy> FIXME and XXX are awesome
[23:11] <bluefoxicy> grep at the source code for a while, find these, examine
[23:11] <bluefoxicy> hack the shit out of everything
[23:11] <bluefoxicy> wash, rinse, repeat
[23:11] <chrisccoulson> siretart - it's really not very nice ;)
[23:11] <bluefoxicy> (FIXMEs occasionally become exploitable bugs)
[23:11] <siretart> chrisccoulson: hm. synclib.pdf mentions the API Status
[23:11] <siretart> XSyncSetCounter ( Display * dpy, XSyncCounter counter, XSyncValue value )
[23:12] <siretart> XSyncSetCounter sets counter to value. It returns False if dpy does not
[23:12] <siretart> support the SYNC extension; otherwise, it returns True.

[23:12] <slangasek> chrisccoulson: did my xtrace help? :)
[23:12] <chrisccoulson> siretart - i tried patching gnome-screensaver to do that already
[23:12] <chrisccoulson> but Xorg doesn't let you change the value
[23:12] <directhex> hm
[23:13] <chrisccoulson> siretart - you just get a BadAccess error, and a crash;)
[23:13] <chrisccoulson> slangasek - thanks - i've not had time to have a proper look at it yet
[23:13] <directhex> apparently debian now finally supports source format 3.0 - does ubuntu?
[23:13] <dtchen> slangasek: I'm beginning to think this grub issue is caused by users' errors. I haven't been able to reproduce the issue, but that doesn't mean very much...
[23:13] <slangasek> chrisccoulson: no worries
[23:13] <chrisccoulson> but i suspect it probably will help. i noticed something briefly at the end of the file when i glanced at it eariler, although that might end up being nothing
[23:14] <slangasek> dtchen: some of them will have been.  But each occurrence should be inspected individually before drawing a broad conclusion.
[23:14] <slangasek> (FSVO "each")
[23:14] <slangasek> directhex: no
[23:15] <directhex> slangasek, so don't upload any 3.0 stuff to debian i want to be syncable?
[23:15] <slangasek> directhex: for the nonce
[23:17] <siretart> chrisccoulson: have you seen http://antony.lesuisse.org/software/xorgsync/synctest.c?
[23:17] <chrisccoulson> slangasek - it looked like the last XRRSetScreenSize call sets the screen size to 1280x800 when there is still an output allocated to a range outside of that new size
[23:18] <siretart> chrisccoulson: there various xsync API calls are demonstrated. the alarm ones fail for me, though
[23:18] <chrisccoulson> from the randr documentation: "All active monitors must be configured to display a	subset of the specified size, else a Match error results."
[23:18] <chrisccoulson> might be nothing though. i need to look in more depth
[23:20] <slangasek> chrisccoulson: feel free to use me as a sounding board, but I know nothing about the protocol, so can't give you much feedback :)
[23:20] <slangasek> chrisccoulson: I do think it's odd that it switches the size to 2640x800 and then immediately back down to 1280x800
[23:20] <chrisccoulson> siretart - i've not had a proper look at that source file, but SYNC does allows clients to set up and manipulate counters. unfortunately though, IDLETIME is a special counter which clients aren't permitted to modify directly
[23:21] <chrisccoulson> slangasek - the larger size there would probably be normal if you have a second screen located to the right of your main screen
[23:21] <siretart> i see
[23:23] <slangasek> chrisccoulson: er, why is it normal for gnome-settings-daemon to not make up its mind on the first go? :)
[23:24] <chrisccoulson> slangasek - AFAICT, it should pick an existing configuration if the hardware that is attached matches that of a configuration that was stored previously
[23:24] <chrisccoulson> if the hardware configuration is new, it auto-configures by appending new screens to the right-hand side of existing screens
[23:24] <chrisccoulson> at least that's how i understand it ;)
[23:25] <slangasek> chrisccoulson: sure; my question is, why does it issue the command *twice* with two different resolutions, when I only hit the button once?
[23:25] <slangasek> it's not new hardware
[23:25] <slangasek> (it has no EDID, so maybe it doesn't know this is the case)
[23:25] <chrisccoulson> ii'm not too sure without looking at the data in more detail. i don't have 2 screens to test it out, and i don't have the benefit of playing with RANDR either
[23:26]  * chrisccoulson curses proprietary drivers
[23:35] <jdong> did keybuk ever make any headway on the mystery sreadahead-is-slow bugs
[23:36] <jdong> http://bradmisik.com/random/mike-desktop-karmic-20091102-1.png
[23:36] <ion> Yes. He wrote ureadahead.
[23:36] <jdong> was just helping someone with this craziness
[23:37] <jdong> pretty beefy system, sreadahead seems to just thrash
[23:37] <ion> It’s available for testing from the ubuntu-boot PPA.
[23:37] <jdong> *nods*
[23:42] <gp> hi guys pl help my server has run out of space (ec2 instance ) ......i created a new partition and mapped home folder to it but its now working
[23:43] <azeem> if it's now working - great!
[23:43] <gp> # /etc/fstab: static file system information.
[23:43] <gp> # <file system>                                 <mount point>   <type>  <options>       <dump>  <pass>
[23:43] <gp> proc                                            /proc           proc    defaults        0       0
[23:43] <gp> /dev/sda3                                       None            swap    defaults        0       0
[23:43] <gp> /dev/sda1                                       /               ext3    defaults        0       0
[23:43] <gp> /dev/sda2                                      /home            ext3    nodev,nosuid    0       2
[23:43] <jpds> !paste | gp
[23:43] <gp> not working :-(
[23:43] <gp> sorry
[23:44] <gp> is fstab is correct here
[23:44] <gp> ?
[23:44] <azeem> gp: this is not a support channel, please ask in #ubuntu
[23:44] <slangasek> or possibly #ubuntu-server, in the case of ec2
[23:46] <brown`> What should be permissions on /etc/cron.daily/apt be for Karmic?
[23:47] <brown`> On my my system, installed fresh from alternate CD, they are 644.
[23:48] <wgrant> brown`: 755 here, installed from the final i386 alternate CD.
[23:50] <gp> pl in the name of Gaint panda pl help me
[23:50] <gp> i copied to home folder to /mnt   and then renamed the home folder
[23:50] <gp> changed "/dev/sda2 /mnt ext3 defaults 0 0"  to "/dev/sda2                                      /home            ext3    nodev,nosuid    0       2"
[23:50] <gp> but fstab is not mounting it
[23:50] <brown`> wgrant: Thanks.  I installed from one of the betas and then upgraded to Karmic final.  Update manager is not checking for updates daily.  Is there an easy way to verify permissions and content for all installed packages?
[23:53] <gp> its national emergency pl help me
[23:53] <brown`> Second question:  My PC running 9.10 hibernates.  On reboot the root partition is identified as having problems, so the system mounts it read only.  Can applications already running write to files on the root partition.
[23:58] <wgrant> brown`: You probably want to ask in #ubuntu.
[23:58] <brown`> wgrant: ok, will do, thanks.  Figured I'd ask here, since it's a kernel question.