User1: Hey, it appears the latest mplayer svn makes dash segfault during ./configure.  Can anyone else reproduce this?
User1: My version of dash is the latest in jaunty, 0.5.4-12ubuntu2.  mplayer svn is at svn://svn.mplayerhq.hu/mplayer/trunk .
User1: I'd give a backtrace, but dash is stripped.  Should I build one by hand with -g?
User2: http://wiki.ubuntu.com/DebuggingProgramCrash has instructions for acquiring debugging symbols and getting backtraces
User1: User2 thanks
User2: (i.e. yes, it's stripped, but we save the debug symbols in packages on ddebs.ubuntu.com)
User1: User2 looks like dash and mplayer's configure script are both wrong.
User1: the configure script has a bug -- they replaced all the `` with $(...) instances, but there's a place where they had
User1: `(echo foo | grep ...)`
User1: that turned into $((echo ...) ...
User2: hah
User2: arithmetic expansion
User1: and dash slurped in the entire file while parsing looking for the closing ))
User2: I don't entirely blame dash for getting confused, although obviously it's still a bug
User1: it segfaulted because parser builds stuff using alloca(), and it ran out of room.
User3: Good for them for quoting things properly, though!
User3: ...or something
User2: indeed, the problem is obvious from http://bazaar.launchpad.net/~vcs-imports/mplayer/trunk/revision/29144
User2: interestingly, bash manages to parse it as the author intended, although I have no idea how
User2: it must be doing some serious lookahead to manage that
User1: User2 probably once it sees something that's not an arithmetic token, it gives prunes that branch of the parse tree and figures it must just be a normal command line replacement?
User1: (i.e, 'echo' isn't numeric ...)
User1: I'd need to go back and look at bash's grammar..
User1: User2 my two-line patch has been sent to the mplayer mailing list.  I suppose that's good enough.
User1: Thanks for your help.
User4: User6 I'm getting multiple user feedback that the udev update doesn't trigger a reboot notification. Is this intended?
User5: kirkland: just thought you might like to know that I got my sheeva plug (http://www.linuxdevices.com/news/NS9634061300.html) today and it is running jaunty server, in a 150mb footprint no less!
User5: I will hopefully be putting up a blog post soon about it, I imagine not too many people are shipping jaunty already, let alone the ARM port
User6: User4 lacking it is not intended, no.  It was mentioned in the USN, though.
User4: User6 ah, okay. I suppose it doesn't make much sense to spam another update to pop up a pretty bubble.
User6: User4 but it's possible the packaging lacked it originally
User4: yeah about 5 users told me it on separate accounts, so I'm assuming the packaging lacked it.
User4: I don't think we had to replace udev very often (the binary itself) :)
User6: User4 it's actually never happened before for -security.  :P
User4: :)
User4: I'm kind of shocked that of all the other major distros that I subscribe security notifications to, none have mentioned this yet.
User4: when was this vulnerability discovered?
User6: User4 last week
User4: yikes
User6: User4 1700 UTC today was the coordinated release time... *shrug*
User4: ah, I see
User4: I suppose it looks like a one-man show for now, huh? :)
User6: but yeah, I'm a bit surprised, this is a pretty serious issue.  :P
User4: yeah, painfully serious.
User6: 1700 was SUSE's recommendation, too.
User3: I'm still trying to figure out if I care enough to patch my high-use Debian machine myself while I wait for them to get their act together
User4: and it's not like the SELinux profiles in RHEL do anything to stop it either. udevd_t is shockingly unconfined_domain()
User6: yup.  the Xen-guest SELinux-escape route is possible with this vuln too.
User4: ouch, xen guests can exploit the host you mean?
User3: Wait..what?
 * ebroder may really care now
User6: it was a paper that was written about a specific Xen guest-to-host vulnerability.
User4: haha ebroder is gonna have a sleepless night :D
User6: User3 the Xen issue was fixed a long while ago.
User3: Oh, ok
User4: ah, dan walsh wrote a reflection on that, I recall
User4: i.e. it being a mistake RH didn't confine VM's in the host.
User6: jdong, User3 http://invisiblethingslab.com/pub/xenfb-adventures-10.pdf
User6: User4 no, it was confined, but allowed block device access.
User6: anyway, same principles could be used to escape SELinux with the udev vuln.  I think, I'm not much of an selinux-escape-artist
User4: mmm I see.
User7: good morning
User4: currently what I see in refpolicy is that the "user_u, sysadm_u, staff_u" users do not have the ability to use netlink_socket
User4: I assume that means users confined under these domains would not have then ecessary access to pull this off.
User4: however, the default config is to place users in unconfined_u so this is moot.
User8: User9 so, evidence is piling up that switching "greedy" on is a very good thing.  There is only one data point to the negative - your firefox case
User8: User9 so I'm wondering how to reproduce that issue, and if we can definitively tie it to greedy, or if it might be an unrelated issue
User9: User8 which was informally confirmed by others on IRC last night; so we'd be trading performance for correctness...
User9: the only thing that changed to trigger the behavior was turning on greedy
User9: reproducing> i965, switch/scroll windows rapidly
User8: User9 was it?  I missed that discussion.
User8: User9 I'm on i965 and not reproducing it
User9: er, sorry - 945
User9: you'd think I'd know by now what I'm running
User8: heh
User8: what were other people on?  who else reported seeing the issue?
User8: if it's only appearing on !i965 or only i945 or whatever, maybe we can conditionalize those cases
User9: I'll check my logs
User9: User8 it was Lure this morning
User9: <Lure> User9 I have also noticed some black areas with greedy (but not to the level that I would go back to non-greedy ;-))
User4: User6 *WOW*, the Xen dude is quite an escape artist. Quite an amazing read.
User9: User8 did you get a fixed patch that doesn't cause insta-segv?
User4: User6 by far the biggest mistake was xend_t being allowed *ALL* block devices.
User8: User9 no, but based on the good perf numbers we're getting I'm considering taking a shot at making one
 * slangasek nods
User8: User9 I mean, if it's worth giving it a shot
User8: ideally, I'd like to have the black firefox problem out of the way though
User10: User9 wait, is it scroll in firefox quickly *or* switch between various windows, or is it switch between firefox windows? i'm confused
User10: ive got a 945 at home i can play with in the morning and a 965 here
User8: I also have a 945 I can upgrade and play with tomorrow I guess
User9: User10 a lot of all of the above
User10: User9 ok
User11: sigh, this klogd hang is driving me nuts
User11: it's not doing any remote logging, so that's not it
User11: User38 shouldn't init wait for the network to be up before it proceeds to rc2?
User12: tjaalton, I don't think init sets up networking, and anyway, it shouldn't wait, since it can take indefinitely long (e.g., if the dhcp server is down during boot)
User12: tjaalton, where does klogd hang for you?
User11: User12 it hangs on boot if the network is not up yet (normal dhcp setup, network-manager isn't used)
User12: tjaalton, hmm... weird
User11: because the dhcp server is on another network, so it might take a while to get a lease
User11: I'll try to strace it..
User11: ldap is used, and it tries to run it as 'klog' user.. maybe that's why it fails
User13: window level all
User11: hm, now that I messed up the klogd initscript (it didn't try to start it at all), it fails in the next initscript which is dbus
User11: so klogd is not at fault here, that's for sure
User11: User12 it's the mountnfs-scripts that are failing.. looks like mountnfs.sh is run even though the network is not up, and that hangs the boot
User12: tjaalton, that'd be a bug, yes
User12: the fix would be to switch to using upstart events, I'm sure :)
User14: Good morning
User15: hello pitti
User9: User17 we're slipping in one kernel upload post-RC; one change is specific to lpia, but the other applies to anyone running ext4.  Can you sync up linux-rt and linux-ports and get them into the upload queue, so we can push that through ASAP after RC is done?
User12: slangasek, any chance you'd accept a further change to fix my SATA/SEMB problems? http://bugzilla.kernel.org/show_bug.cgi?id=11579 (but I haven't verified the patch yet)
User16: bugzilla.kernel.org bug 11579 in Serial ATA "Libata SATA hard drive detection" [Normal,Resolved: code_fix]
User9: User12 is that a blocker for installability?
User9: oh, if the patch isn't verified yet, then the timeline probably doesn't work
User12: slangasek, it prevents installing on a bunch of WD SATA hard disks -- the kernel doesn't recognize them as hard disks
User9: the kernel in question is already uploaded, and needs to be accepted for building by tomorrow in order to make this work out time-wise
User12: ah, too bad
User12: I'll test the patch RSN anyway, it'd be nice to get this fixed in an SRU
User17: User9 ok I'm on it, I have one bug I need to kill thats powerpc-specific as well, so this is good news, thanks.
User12: (although it probably requires an updated ISO image, too, hmm)
User9: User12 yeah, which would have made it useful to have in for final :/
User17: User9 ...or I could if the git commits were pushed to kernel.ubuntu.com.
User9: User18 ^^ linux-ports folks need those kernel commits :)
User18: slangasek, TheMuso The patches itself are there. Just a sec I forward Tims mail with the ids
User18: I am currently locally building that kernel to get the abi files for the merge back
User17: User18 Not really useful, as I list the exact changelog bits from mainline in the ports upload'
User17: I could generate it however, so I'll see what I can come up with.
User18: TheMuso, would the exported patches be ok? You could apply them with git am
User17: User18 that would be fine, means I rebase by hand, i.e no script, but thats ok.
User17: seems the RSS for gitweb is not updating which is why I thought some of the patches weren't there.
User14: User18 I just updated bug 321474 to remove the v-failed/regression tags
User16: Launchpad bug 321474 in linux "[Intrepid] Update kernel to Linux 91.69.162.6" [Medium,Fix committed] https://launchpad.net/bugs/321474
User14: User18 is there a plan when to release the intrepid kernel to -updates?
User18: pitti, Yes, I definitely wanted to go over the open stuff to see where we stand and have Intrepid and Hardy moved to updates soon
User18: TheMuso, I created a local topic branch for that upload and have to merge it back as soon as I got the abi files. Then I'll push everything
User18: TheMuso, Mail is away
User17: User18 thanks
User17: User18 re your email regarding intrepid ports, I'll read it again on the weekend and look into it then.
User18: pitti, The when: is early next week ok for you or would it be better this week?
User18: TheMuso, NP, it has been behind quite some time now. So a little longer won't hurt
User14: User18 I don't mind, the actual copying is trivial
User14: User18 I see two regression-proposed bugs: bug 337929 and bug 311716
User16: Launchpad bug 337929 in linux-backports-modules-2.6.28 "ieee80211_regdom=EU now causes oops after latest update" [Medium,Fix released] https://launchpad.net/bugs/337929
User16: Launchpad bug 311716 in linux "The slider brightness Applet has value inverted after the last update (2.6.27-11)" [Medium,Confirmed] https://launchpad.net/bugs/311716
User14: User18 no v-failed any more
User14: if we could clarify those two, then we'd be good to go
User14: User18 oh, and no regressions reported against the hardy update
User18: pitti, The regdom thingy should be somewhere. But it might be in the patches queued up. I have to check. With brightness problems I fight a bit. Trying to get info about the specific issue as all are mixed up. But from the general feeling that is not worse than the version in updates now, just not better.
User18: pitti, Oh, right the regdom bug is for lbm. I see andy asked for feedback which seems to have arrived now. But it is not yet uploaded to proposed
User14: User18 ah, so it needs another lbm upload first?
User18: pitti, yes
User18: pitti, I put it onto my list to get done soonish.
User18: pitti, About the inverted brightness: as it is that way on 2.6.27-11 and (maybe as I have not clear feedback) the same in proposed. Would it be ok to move proposed to upadates anyway? I even think the inversion issue should be fixed in the proposed.
User19: The linux-backports-modules-intrepid-generic in ship-live seems to be bogus; anybody minds if I drop it?
User18: lool, What means bogus?
User19: It's not in jaunty anymore
User19: User18 The fact that's a package not existing in jaunty is listed there seems wrong, I'm not saying tehre are bugs in the package  though :)
User18: lool, Oh, is that the meta-package
User19: eagle-usb-utils isn't in jaunty either
User19: User18 Not really, it's a task listing additional packages to install in the live CD I think
User19: eagle-usb-utils isn't in jaunty anymore either; looks like I could cleanup this seed
User18: lool, I pretty much think so. The nameing with the release in it looks like that
User18: It would then be linux-backports-modules-jaunty-generic
User17: User18 hrm ok, since you haven't also uploaded other patches that are in the jaunty tree, theres no point rebasing. I'll just use that ext4 patch fix, and do another bug fix I need to do, and that will be it.
User19: stgraber: Hey, we really need the ARM images added to the tracker
User14: User20 hm, should I remove the current intrepid-proposed update-manager due to lack of feedback, or do you want to test it yourself? (bug 292179)
User16: Launchpad bug 292179 in update-manager "Intrepid upgrade removed EVMS but should not have allowed upgrade" [Medium,Fix committed] https://launchpad.net/bugs/292179
User18: TheMuso, that new kernel only consists of that config change in lpia and the ext4 fix (compared to the last release)
User17: User18 from there on in, any SRUs that are likely to be useful for ports can just be pulled as patches directly, no tree rebasing.
User17: User18 yes I know
User19: stgraber: Could you please add an entry in Ubuntu for desktop armel imx51 babbage (that's a live) and split the netboot ones with one per flavor (versatile, ixp4x, iop32x)
User19: stgraber: Also, UMPC needs dropping and UNR should be its own toplevel project (and server as well BTW)
User14: User20 (I'd prefer the latter, of course)
User17: User18 what I'm saying is that there are other commits in the jaunty tree that haven't been uploaded, so I don't need to rebase, and for SRUs, commits will only need to be pulled where they are applicable to ports
User9: User19 why is there any need to reorganize the products?
User19: User9 Well the current situation is inconsistent, the MID and UNR images are listed in different ways, but they are built in the same way
User19: User9 But I can understand if you prefer avoiding any reorg at this point
User19: stgraber: ^
User9: User19 ah, well; UNR is built from main, which also sets it apart from MID presently?
User19: User9 UNR is built from universe as well; it includes cheese for instance
User18: TheMuso, A complete rebase would pull things not yet uploaded, yes. So it is not useful here. When we are doing sru's I guess both approaches are ok. With rebasing you get all things, but if you prefer you can cherry pick what you find applicable/useful
User9: User19 oh
User17: User18 yeah the cherry-picking will likely be what I'll do.
User19: User9 This might be a bug though, not one I expect to be fixed before release though, there are ~24 binaries from universe or so
User18: slangasek, I just had the full test-compiles done for that proposed kernel and just saw lpia ftbs due to a missing module. I look into that and get back to you. Maybe the package I uploaded should get dropped
User9: User18 ack, let me knwo
User18: slangasek, Yeah, the problem was the change for CONFIG_PACKET from m to y. Which needs a little tweaking with the modules list
User20: User14 I can do it myself if, but probably not today
User14: User20 doesn't need to happen today, I was just wondering if it makes sense to keep it in -proposed
User9: User18 rejecting this upload, please reupload at your discretion
User18: slangasek, ok, thanks
User14: User20 especially because I assume we'll need more u-m SRUs soon
User18: TheMuso, If you are not picking the config change for lpia, you will be ok
User17: User9 mind having a quick look at bug 355344? Since another ports upload is forthcoming, I'd like to get this fixed now, rather than have to do an SRU.
User16: Launchpad bug 355344 in linux-ports "crtsavres.o is required for kernel module builds" [Undecided,Confirmed] https://launchpad.net/bugs/355344
User17: User18 I'm not, since lpia is not built from ports at all
User9: User17 sorry, can't do it right now
User17: User9 ok I subscribed ubuntu-release to it anyway
User14: User20 ubuntu-vm-builder is in a similarly sad state :(
User20: User14 ok, I put that on my list as wel
 * pitti hugs mvo
User14: I'm currently doing a cleanup round for -proposed
User19: User63 Around?
User19: User63 We'd need some help in getting the installation instructions in shape for UNR
User19: User63 We have some bits in the middle of https://wiki.ubuntu.com/UNR and some reqs on https://help.ubuntu.com/community/Installation/SystemRequirements
User14: User9 there's a new tzdata update (http://launchpadlibrarian.net/25523792/2009e-2009f.diff) with a trivial, but urgent diff; would you rather have this as an SRU, or can I upload it to jaunty?
User9: User14 jaunty
User14: ok, thanks
User14: User9 oh, doko uploaded a tzdata as well, I'll look at it and integrate
User14: ah, installs a missing file; seems safe enough
User14: User22 I reject your tzdata upload, I'll integrate it into the 2009f one
User21: User20 poke
User22: User14 ok, thanks
User23: pitti, TheMuso should have hardware that will be able to reproduce and test the package from -proposed for bug 297245
User16: Launchpad bug 297245 in xserver-xorg-video-intel "[i965] Dell Studio 15 White Screen on X startup" [High,Fix committed] https://launchpad.net/bugs/297245
User23: he's got the one system I had that could do it
User17: User23 I'll isntall intrepid on it tomorrow and test that.
User23: TheMuso, it's actually a hardy proposed package i think in question
User17: User23 oh
User17: well it will be hardy then
User23: TheMuso, you don't need to install to test it, it will fail off a hardy live disk, and you can install the deb in the live mode to verify X comes back to life
User9: User23 morning
User17: User23 good enough, thanks
User17: I'll do that tomorrow and report back
User9: User23 mesa has just been accepted; it's a .5h build, then a 1.5h wait for the publisher, then I'll reroll mythbuntu
User23: slangasek, g'morning.  dog kept waking me up all night, so i figured i might as well stay up :)
User14: User38 for bug 283316, is "sudo udevadm monitor --udev" really the correct thing to debug the udev rules? I only get some "change" event on the USB host, not the actual rules processing (the tracks/vol_id detection is probably the part which causes this)
User16: Launchpad bug 283316 in udev "CD-ROM tray closes automatically after eject" [High,Fix released] https://launchpad.net/bugs/283316
User9: User23 heh
User23: slangasek, sounds good.
User23: TheMuso, thanks
User9: User23 testing resources will be available around then?
User23: slangasek, i'll be able to, not so sure anyone else is up yet though
User9: User23 well, that gives them another 3h to wake up :)
User9: User23 you and fader seem to have been the main testers, anyway
User23: slangasek, yeah at least for those that report it.  there's a handful of people that we've been getting testing dailies and reporting whether things are broke for their situations, but can't seem to get them reporting to the iso tracker yet
User9: heh, ok
User17: User9 BTW I won't be able to get linux-rt sorted until a new linux-source package is in the archive, since that doesn't currently use a git repo, and build deps on the linux-source-2.6.28 package to build
User9: ok
User24: Any Packagebuild or bugfixes needed here?
User20: User21 /poke
User21: hi
User14: User38 nevermind, --environment was missing
User21: So I've seen quite a few changes for the kernel set as "fix committed" - is a new kernel gonna roll out for the release candidate?
User9: no
User25: slangasek, so one time back to the ltsp change ... formerly the amd64 server + i386 client installations didnt have to touch dhcpd.conf, while they had to rebuild their chroots for i386 the conffile was preconfigured for i386 and didnt have to be touched ...
User25: slangasek, as i understand conffiles the change in the package will quietly replace the existing dhcpd.conf for these users
User25: (on upgrades)
User25: which means their clients will silently stop booting
User9: User25 conffiles> correct; the flipside seems to be that amd64-on-amd64 is the only thing you can actually configure out-of-the-box right now, and that common case fails?
User9: User7 could you elaborate on why you consider bug #361765 a bug?  AFAICS, the task still exists
User16: Launchpad bug 361765 in tasksel "DVD alternate install still offers "Edubuntu Desktop"" [Undecided,New] https://launchpad.net/bugs/361765
User25: right, but doe sthat justify to break all existing amd64->i386 setups (which is a huge amount imho)
User9: User25 discuss that with stgraber?
User25: i did, i just wanted a second opinion
User25: the problem is known since breezy and since we didnt have a proper solution we kept it the way it was until tonight
User9: ah
User7: User9 I think it's just the term
User25: i'd rather perfer to work out a proper solution than breaking it for many people on RC day
User26: User25 I don't think the fix has gone in yet has it slangasek?
User9: User25 then that's a good argument for rejecting it, but I would like you to come to an agreement with stgraber instead of me being a mediator for that
User9: User7 i.e., "edubuntu" vs. "Ubuntu Education Edition"?
User25: yes, he will come here once he is online again (he is commuting atm)
User7: User9 yes
User25: davmor2, nope
User25: davmor2, its waiting for the freeze to fall, thats why i brought it up
User26: User25 Okay.
User25: dholbach, the dvd installs edubuntu-desktop
User9: User7 ok, makes sense
User25: as a package/task
User25: and by the definition RichEd set up "Ubuntu Education Edition" != edubuntu
User25: (though dont ask me what "Ubuntu Education Edition" is actually after his definition :) )
User25: but the two are very distinct on all websites so you need to update these as well
User9: hrm?
User9: I have no idea what definition that is.  As far as I was ever told, Ubuntu Education Edition was a new name for edubuntu.
User25: http://www.ubuntu.com/education was referring to edubuntu as a distro ... www.edubuntu.org was referring to ubuntu in education as something different from edubuntu
 * ogra checks if that was fixed/changed already
User25: edubuntu is still in the menu on ubuntu.com but apparently the text referring to it was removed now
User25: there is still http://www.ubuntu.com/products/WhatIsUbuntu/edubuntu though
User25: that should point to http://www.ubuntu.com/education
User7: User25 https://bugs.launchpad.net/ubuntu-website/+filebug :)
User25: slangasek, the prob is that the actual strategy was never made clear to anyone by rich so there is a lot confusion
User25: dholbach, i'm not doing edu stuff and am busy up to my ears in arm, can you file it ?
User7: User25 I don't know much about the edubuntu situation, just noticed it during the installation
User25: (that should really be discussed with LaserJock rather)
User25: dholbach, the transition rich had to do is only half way done, i have no idea who has taken over his role but if we change it on the DVD it should be changed everywhere for a professional look
User7: User25 I'm not sure we'll find the right answer here in #ubuntu-devel
User25: no idea
User25: i dont mind if it stays as is, just pointing out the overall inconsistency
User12: is the queue with uploaded packages that aren't entering the archive due to the freeze visible somewhere?
User9: https://launchpad.net/ubuntu/jaunty/+queue?queue_state=1
User27: User12 http://launchpad.net/ubuntu/jaunty/+queue
User27: ...and choose "Unapproved"
User12: thanks
User27: Or save slangasek's link if you're the bookmarking sort of person.
User27: :)
User12: I'd like to save the bookmark where I can easily find out such things :)
User27: It's called #ubuntu-devel :)
User27: You may have heard of it.
User27: :p
User9: irc://chat.freenode.net/%23ubuntu-devel
User28: it's part of the secret knowledge passed on from one developer generation to the next one :)
User12: I'm not sure oral history is the best way to document things
User12: but I'll ask more things again :)
User28: I don't know how well google has indexed http://irclogs.ubuntu.com/
User29: wget and grep work though.
User30: wgrep!
User31: hi
User31: can someone help me set up development environment the easiest way?
User31: I need boost package. Is it called libboost in ubuntu?
User32: apt-cache search boost
User31: ah, thanks
User31: I've found one package with version number attached after libboost.
User31: Is it advised to call that one, or should I proceed with libboost-dev only?
User29: User31 It depends on what version you want.
User30: vlada_, generally, version numbers in package names refer to ABI versions, versionless -dev packages pull in the most recent headers corresponding to the most recent API/ABI in the archive
User29: User30 Generally, yes, but not in the case of boost
User29: User31 ^^
User33: User19 regarding bug 362071, are we actually using lpia for any alternate ISOs?
User16: Launchpad bug 362071 in linux "CONFIG_PACKET should be "y" on lpia; breaks DHCP in alternate installer?" [Medium,In progress] https://launchpad.net/bugs/362071
User2: User33 I filed it after getting a bug report from a user who was doing so.
User2: User33 actually, I think they were using a netboot image
User2: nevertheless, http://cdimage.ubuntu.com/ports/daily/current/jaunty-alternate-lpia.iso exists
User33: User2 is it being considered RC?
User19: User33 A bunch of people seem to be trying to install Ubuntu flavours with the lpia arch via the alternate images
User19: User33 I guess they think lpia is best for their atom or whatever
User2: User33 not quite, but there was an ext4 bug that we wanted to fix anyway
User2: User33 (Medium bugs aren't RC)
User2: I discussed it with slangasek last night
User9: not publishing the alternate is also an option, if the kernel update is considered untenable; but the ext4 issues are fairly high-profile as well, and the delta is very manageable here
User14: meh, svn.debian.org/wsvn is just about the worst svn browser I've ever seen
User14: I just want to look at a file...
User34: User14 heh, I feel your pain
User30: they updated wsvn to a version which can't browse source
User30: use viewvc
User9: superm1, User35 mythbuntu build going now
User35: User9 Thanks
User36: is the rc to be released today?
User31: thank you all
User31: I have another strange problem
User31: cmake generates this message:
User31: -- The CXX compiler identification is unknown
User31: CMake Error: your CXX compiler: "CMAKE_CXX_COMPILER-NOTFOUND" was not found.   Please set CMAKE_CXX_COMPILER to a valid compiler path or name.
User31: every other pagkage seems to recoganized
User7: User9 do you think bug 334657 is release-critical?
User16: Launchpad bug 334657 in qt4-x11 "Subpixel/Lcd mode with VRGB/VBGR makes qt4 applications on Jaunty unreadable" [Medium,Confirmed] https://launchpad.net/bugs/334657
User9: User7 is it really only VBGR/VRGB that are affected?  That seems like a blatant configuration error, then?
User7: User9 I have no idea - ccm (in #ubuntu-bugs) told me about it and asked how to get more attention to it
User9: (you don't use the vertical subpixel settings unless your pixels are laid out vertically; which for most people they aren't0
User7: seb128, Riddell: any idea about bug 334657?
User16: Launchpad bug 334657 in qt4-x11 "Subpixel/Lcd mode with VRGB/VBGR makes qt4 applications on Jaunty unreadable" [Medium,Confirmed] https://launchpad.net/bugs/334657
User15: User7 why would I have any idea about qt?
User15: no
User15: I've no clue about fontconfig, fonts or qt
User37: hi there
User7: User37 slangasek asked: "is it really only VBGR/VRGB that are affected?  That seems like a blatant configuration error, then?"
User37: User7 in my tests it is and all users seemed to report so
User37: User7 it happened directly after an upgrade to jaunty for me
User9: User37 why did you have VRGB set?
User9: that's not a default, and it's not the subpixel orientation that most users have
User37: User9 actually that was a result of lcd (laptop) display tuning for getting better font results - as it is quite easy to reach this menu in ubuntu and you dont even need admin rights for it, i think a bunch people tested it
User37: User9 and might still have turned it on as it had no negative side effect
User9: well, it's still a misconfiguration if you click a setting that doesn't actually match your subpixel layout, and if it looked good at all that was an unintended side-effect in the first place
User9: so I don't see that this is a critical bug
User9: superm1, User35 mythbuntu 20090416 up
User35: User9 Thanks, I'll start grabbing it
User9: superm1, User35 can you give an estimate of how long it'll take to get the tests covered?
User35: User9 I think I can get the i386 ones done in 1-1.5h once I have it downloaded
User9: User35 how long's the download take? :)
User35: User9 I'll let you know in just a moment :)
User9: ok
User35: User9 rsync says about 15 minutes for the download
User9: cool
User37: User9 well actually vrgb is broken now. that means at least it will hit users who intentionally configured it for rotated displays and those who turned it on by chance. so the question seems more if it might have impact to a remarkable amount of users after release - be it by misconfiguration or intention, in fact both will be presented unusuble qt applications and might have no clue at all on how to fix it
User38: User39 what would you like to know?
User9: User37 can you give me a simple test case with which to reproduce the bug, given that I'm running Ubuntu with no Qt apps currently installed?
User39: User38 Can you point me to docs in the wiki?
User38: User39 what are you trying to do?
User39: I want to force r8168 to be loaded before r8169.
User38: User39 there is no r8168 driver
User39: Oh, crap, that's right.  This system is actually Debian.  Sorry.
User38: User39 off to #debian with you then ;)
User37: User9 I assume no
User39: User38 sorry about that.  I forgot that I sometimes am on machines that *aren't* running Ubuntu.
User9: User37 hmm?
User37: User9 at least "qtconfig" is enough as a test application
User11: User38 network is started up both by udev and init, but why?
User38: User39 though in general, first check whether your device is supported by the other driver (modinfo r8168)
User9: User37 ok, grabbing
User14: User39 curiously, I sometimes forget that there are machines out there which aren't running Linux.. :)
User38: User11 physical devices are started by udev, logical devices by init
User9: User37 in any case, even if the conclusion is that Qt is Really Broken, this is likely to be a matter for an SRU rather than an emergency pre-release fix
User39: User38 I'm bugging people in #debian now, but in this case r8168 and r8169 both support the chip in question, but r8169 is buggy on it while r8168 works fine.
User39: User38 Meanwhile, the *other* chip on the system requires r8169.
User37: User9 then go you to you display settings and enale "lcd" mode and "vrgb" (while no qt app is running)
User37: User9 then start qtconfig
User11: User38 well, ifup -a is run twice here, since /e/n/interfaces has eth0
User9: augh, just turning on VRGB hurts my eyes
User38: User39 ah, then you need both 8168 and 8169 loaded
User11: at least the services in if-up.d are run twice
User38: User11 ifup -a should only be run once
User38: User11 udev does not run it, it will run ifup eth0
User38: User39 in that case, you're going to have to poke things in /sys/bus/pci/drivers/r8169 and 8168
User11: User38 right, true.. but the services are restarted
User38: User11 shouldn't be
User38: User11 if the device is up, it won't be run again
User9: User37 I cannot say with certainty that what qt is doing there is actually wrong for true VRGB
User11: nfs-common is run three times here (obviously a bug, it shouldn't do that in rc2/S20)
User9: wait, yes I can, I can rotate my output :)
User38: User11 are you sure they're not just getting run again because you don't actually check multiple devices?
User38: User11 they'll be run for "ifup lo" *and* "ifup eth0" remember
User37: User9 well qtconfig looks unusable, right? in all display directions
User39: User38 That seems ... unreasonable.
User38: User39 why?
User39: User38 Well, I just can't help but feel that I have to know an awful lot of implementation details to do something that seems pretty simple.
User39: User38 Between udev/modprobe/sysfs ...
User38: User39 changing drivers is not supposed to be "simple"
User38: you're not supposed to need to worry about it at all
User39: User38 Oh, well that's true.
User39: User38 Any docs on the particular pokings that need to occur?
User9: User37 ah, yes, it's still unusable when I rotate my monitor (and not just because it makes my neck hurt)
User11: User38 ah, excellent..
User38: User39 there's lots of documentation, e.g. in the kernel source
User38: User11 there's a reason we don't start services in that directory ;)
User9: User37 so it's certainly a valid bug, but we certainly can't commit to fixing this before release when there's no known fix yet
User11: User38 hmm, you mean the ones in if-up.d shouldn't be run?
User39: User38 Would it be unreasonable to, e.g., blacklist both r8168 and r8169 and then put both in /etc/modules?
User37: User9 okay then. If that does not fit into release critical thats fine for me. I just wanted to bring this up to somebody who can say so as it did not get any attention so far and I wanted to prevent that it just got overseeing.
User38: User39 wouldn't make any difference
User37: User9 thank you for the taking the time
User38: User39 both would load, and the existing rules for binding would still take place
User9: User37 no problem :)
User37: User7 and thank you for getting me in contact :)
User38: User11 they're not services usually, they're tasks
User7: ccmno worries
User7: User37 no worries :)
User38: User11 ie. they poke or prod or do something when a network device comes up
User38: User11 we don't start/stop services based on the presence or not of network devices
User38: User39 the kernel makes the decision which driver gets which device
User39: User38 Things currently work if I rmmod both, modprobe r8168, and then modprobe r8169.  I was under the impression that drivers "claim" devices.
User38: User39 ah, that's more interesting then - yes you can force that
User38: though that should be forceable with a tweak to modules.order
User39: User38 Ah, perfect.  Let me read about that.
User38: ie. edit /lib/modules/$(uname -r)/modules.order and make sure r8168 is before r8169
User38: (assuming both claim your device, that will make 8168 "win")
User39: User38 If depmod gets run will my changes be overwritten?
User38: User39 no, only a kernel upgrade would overwrite your changes
User38: use dpkg-divert to prevent that
User39: User38 Great, thanks for your help.
User39: I'm still hoping that one day I will understand udev, modprobe, and kernel interactions.  But I think it would take a few days of reading.
User38: User39 there's good books on it which are only slightly out of date <g>
User39: User38 You're pulling my leg, right?  Does such a book truly exist?
User38: User39 "Linux Device Drivers" by Greg Kroah-Hartman
User39: User38 Oh, I have an old old copy of that, I think.
User11: User38 yes, figured as much. maybe I just need to hack around the mountnfs issues for now, and make sure this works properly when sysv-initscripts are replaced by upstart events ;)
User38: User11 karmic, hopefully
User11: User38 yeah, looking at the specs
User38: User39 http://lwn.net/Kernel/LDD3/ is the current edition
User38: User39 ch.14 is the relevant one, though there are improvements there that the book misses
User39: User38 I think I bought my copy about 5 years ago.  I'll have a look at the recent edition.
User38: User39 LWN is an excellent resource for catching up on the changes since
User39: User38 Okay, thanks again.
User38: (in summary, rather than all the _PRODUCT, _ID, etc. nonsense, the kernel now exports a single MODALIAS string that describes the device uniquely
User38: and modules have aliases that wild-card match these strings
User38: so if we do 'modprobe $MODALIAS' we get whatever module(s) think they can support that card)
User9: User23 ping?
User40: pitti, hi
User9: User35 hmm, I forgot that I'd already neutered the sync-mirror script - you don't actually have mythbuntu 20090416 yet
User9: (because I failed to fully publish it)
User35: Ah, heh... okay, I'll stop testing :)
User9: publishing now
User35: Should I just grab it from cdimages via http?
User9: User35 whichever way you'd like to grab it - just make sure you're grabbing the 20090416 serial
User35: User9 roger that... I'll just grab it via http
User14: hey tkamppeter, how are you? had a good travel back?
User40: Yes, and I have a new SRU, for Jaunty and for Intrepid, bug 357732
User16: Launchpad bug 357732 in ghostscript "cups always prints with the default page size" [Undecided,New] https://launchpad.net/bugs/357732
User40: The patch is small, perhaps the Jaunty version can directly get in after the RC.
User34: W31
User34: bah, sorry
User14: User40 should rather become an SRU
User40: pitti, uploaded to Debian BZR of CUPS
User14: User40 ok, thanks
User40: pitti, how to proceed for the Jaunty SRU?
User14: User40 we should create a jaunty branch anyway
User40: pitti, also uploaded upstrream now.
User14: User40 "uploaded"?
User40: Upstream is http://www.openprinting.org/download/printing/pdf-printing/
User14: ah, that part :)
User40: pitti, you thought that upstream is Debian?
User14: User40 no, I thought that you got cups upstream commit rights now
User31: can somebody tell me how can I get c++ executable
User31: gcc is already installed?
User30: gcc is a C compiler
User31: -? +!
User30: g++ is for c++
User30: install build-essential.
User31: didrocks: thanks
User31: I've never thought these could be separate packages
User23: slangasek, pong
User9: User23 hi, mythbuntu images are up and waiting :)
User23: okay cool thanks
User35: User23 I'm testing the i386 ones atm
User35: (Just FYI)
User23: fader_, cool, i'll grab amd64 then
User23: i've got amd64 hardware that failed that open luckily enough
User35: Works out well then :)
User40: pitti, bug 357732 is prepared for a Jaunty SRU. An Intrepid SRU is not needed (here the bug does not occur).
User14: User40 thanks, this will be a good reminder
User40: bug 357732
User41: User15 Do you have any suggestions for a workaround for bug 361112?  I'm convinced it's a GTK/metacity bug as we definitely call set_transient_for.
User15: User41 better to ask mvo about wm issues
User41: sure thing.  mvo ^
User20: User42 looking now
User42: thanks!
 * jtholmes is away: for about 3 hours
User20: User42 could you please try http://paste.ubuntu.com/152178/ ?
User42: will do
User20: User42 I will be away for a bit for dinner but I will read backlog
User42: ok
User42: User20 no such luck
User38: User12 Matrix Keysigning Party?
User38: we all wear PVC, Bondage Gear, Sunglasses and come with large guns?
User4: now THAT'S a keysigning party :)
User4: WHOOO I GOT video-intel TO HANG AGAIN!!
User4: compiz's fade-in animation for the Firefox awesomebar did it in this time.
User38: User4 there's no prize for that, you know? :)
User4: User38 so that's why I'm not filthy rich yet :)
User38: getting video-intel to not hang is where the prize is at
User4: now that's no fun.
User25: jdong, well, at least it hangs for you ... for me it does that:
User25: Swap:      4803392    4352308     451084
User4: awesome
User4: does it put itself out of misery soon thereafter?
User25: until i hit OOM at some point and the whole machine hangs
User4: aww.
User25: though i'm adventurous and use UXA
User4: apart from hanging after 30 minutes of use, 90% probability of crash-after-resume is my other problem.
User4: this is under UXA
User4: EXA has completely stopped working for me in Jaunty
User4: (when compiz attempts to launch I get a GPU lockup)
User25: works here just not fast
User38: UXA is full of lock-up bugs
User38: really no prizes there
User25: yeah
User25: but i somehow got used to see xchat through my terminal windows while working
User25: no UXA no compiz for me
User9: User23 how's it looking for you?
User35: User9 Sticking my $0.02 in, i386 looked great
User23: slangasek, not sure yet.  my download took awhile, so i'm just testing now
User9: ok
User23: fader_, what graphics hardware did you test with?
User23: fader_, not sure if you saw with your disconnect; what graphics hardware did you test with?
User35: I tested in virtualbox... not sure what it emulates
User23: vesa
User23: and mythtv-setup was fine for the last step correct?
User35: User23 Correct... I didn't see any problems in any of the setup screens
User23: fader_, okay cool; good
User14: User40 I thought bug 357732 wasn't needed for intrepid? You requested an intrepid task; also, the jaunty task is needsinfo, is it still waiting on something?
User16: Launchpad bug 357732 in ghostscript "cups always prints with the default page size" [Undecided,Invalid] https://launchpad.net/bugs/357732
User39: User38 FWIW, blacklist r8168, blacklist r8169, and putting r8168, r8169 in /etc/modules does do the trick.  initramfs needs to be regenerated, of course, and your root fs can't be on a network filesystem.
User39: User38 modules.order doesn't seem to be used/present on any systems I have available here, BTW.
User39: User38 (but I didn't look that hard)
User23: slangasek, i'm having a hard time authenticating with iso tracker for some reason (getting 403 errors), but the test turned out mostly right.  the bug we were trying to fix is fixed, but it uncovered another (in ubiquity) that is lower priority.  so i'd say push rc, and i'll have the ubiquity bug fixed for final
User38: User39 ok
User9: User23 ok, thanks
User14: User19 notify-osd bzr branch has two uploads which aren't in jaunty; and the second is unreleased
User14: User19 the second one has major changes, I hope you didn't intend them to go into jaunty?
User19: User14 The first is in the queue
User19: User14 the second is just in progress stuff not worth an upload
User14: User19 ok, that's for karmic then; I'll branch off a jaunty branch and commit the stuff DX asked for for jaunty
User19: User14 The changes are trivial, but they might show a big diff; happy to defer to karmic
User40: pitti, I have updated bug 357732 now. I have requested the Jaunty and Intrepid tasks before I found out that the bug is not present in Intrepid. The Intrepid task I have set Invalid now. I have also set the CUPS/Jaunty task to "In progress" now as the reporter has done the requested tests and the fix is uploaded upstream and commited to Debian.
User16: Launchpad bug 357732 in ghostscript "cups always prints with the default page size" [Undecided,Invalid] https://launchpad.net/bugs/357732
User6: User14 hi, I have a friend experiencing the volume-notification part of bug 338837, but he's running notify-osd past 0.9.5 which supposedly fixed it
User16: Launchpad bug 338837 in notify-osd "New notification does not work if icon theme is changed from Human" [High,Fix released] https://launchpad.net/bugs/338837
User6: does anyone have a T60 that can reproduce this: 362463 ?
User32: bug 362463
User16: Launchpad bug 362463 in notify-osd "Volume change notifications no longer displayed in Jaunty" [Undecided,New] https://launchpad.net/bugs/362463
User43: pitti, User9  https://wiki.debian.org/XStrikeForce/InputHotplugGuide
User32: User6 I can reproduce that here.
User44: Pici - you see anything on the session bus?
User32: User44 dbus-monitor? No. I get activity for changing the brightness, but not from volume changes/mutes.
User44: i'd be tempted to reassign that to gnome-settings-daemon then
User44: it's not a notify-osd bug if there is no messages being sent to it
User6: User44 what's the method for debugging this?
User6: Pici, User44 dmandell is the filer of 362463
User6: User45 can you run "dbus-monitor" and see if you get messages for volume changes?
User6: User45 Pici was not seeing dbus notifications, so it seems like this is a lower regression than just notify-osd
User14: User6 can you please follow up in the bug and talk to MacSlow about it?
User45: Sure
User6: User14 sure, though I'd like to have more specific details.
User14: User43 want me to do anything with that guide? (ECONTEXT)
User45: No messages when I change my volume.
User6: User45 okay, cool.  can you add that detail to the bug report?
User45: Yup.
User6: chrisccoulson, User14 what is actually responsible for sending those dbus messages?
User43: User14 nope, just reference
User14: User6 that's done by libnotify1
User14: User6 programs usually link to that, and this converts the libnotify API calls to d-bus messages, which notification-daemon or notify-osd pick up
User14: User6 but I doubt that there's a problem with the dbus side
User14: I guess it just fails to draw the bubbles
 * pitti -> dinner
User6: the drawing works, but the app linked to libnotify1 isn't sending... but I don't know what app that is on a T60.  :)
User14: User6 oh, I see; that's an app problem then, and dbus-monitor should show whether it's actually sending the calls
User6: User14 right, I just don't know how the button-press maps all the way into dbus.
User6: User14 and it's clearly HW specific.  2 T60 people see it, and I don't.
User6: User14 and their volume buttons actually function.
User3: User6 Should I add openafs-client.NEWS entries to all of the debdiffs for bug 356861?
User16: Launchpad bug 356861 in openafs "OpenAFS Security Advisories 2009-001 and 2009-002" [Undecided,In progress] https://launchpad.net/bugs/356861
User6: User3 we tend not to, but you can if you want.  :)
User6: User46 ah-ha, there you are.  trying to track down the root cause of bug 362463
User16: Launchpad bug 362463 in notify-osd "Volume change notifications no longer displayed in Jaunty" [Undecided,New] https://launchpad.net/bugs/362463
User3: User6 *nods* Ok. Since the intrepid one is the only one that needs changing, I'll pull it from there for consistency :)
User3: Hmm...actually, I take that back. I think I do want them in there so people know you need to upgrade the kernel modules
User46: User6 My guess would be gsd would be the next place to look.
User46: User6 The person to ask about that is davidbarth, who doesn't seem to be in this channel.
User46: User6 #ayatana
User6: User46 what can dmandell do to diagnose that?
User6: User46 he's not in #ayatana either :(
User46: User6 Hmph.  There goes passing it off :)
User6: User46 any ideas on how to diagnose gnome-settings-daemon ?
User47: add some fprintf hooks in it
User47: =p
User46: User48 The bug we're talking about is bug 362463
User16: Launchpad bug 362463 in notify-osd "Volume change notifications no longer displayed in Jaunty" [Undecided,New] https://launchpad.net/bugs/362463
User46: User6 No, not really :(  I'm hoping that bratsche does :)
User6: User46 could debian/patches/16_use_synchronous_notifications.patch have done it?
User48: I'll take a look.
User6: User46 that's the only thing that seems to touch notifications recently.
User6: User48 cool, thanks
User46: User6 Well, that should make them waynehicks@example.org.  So it should have to be there.
User6: heh
User46: User6 It may have changed though, and that might be the issue.
User48: User6 You know, I think this may have been removed deliberately because some people (including myself and dobey) were complaining that it's annoying to hit the "volume up" button and then see a notification that basically says "you just hit the volume up button, as you thought you did."
User6: User48 but this still happens for me on my machine.
User6: User48 i.e. it's specific to the T60 or something.  also, I thought that was the point of those notifications?
User6: User48 it gives you an indication of where you are on the spectrum of volume, min, max, etc
User6: User48 I would imagine mpt would freak out if volume-change-notifications were _removed_.  :P
User48: I just tested, and when I do volume up key.. I get the volume progress bar kind of notification.. but I no longer get the one that just says "you hit the volume up button" or whatever.
User48: Let me go test on my Thinkpad.
User6: User48 right, we're debugging a total lack of the progress bar notification.
User48: Ah, I see.
User48: Okay hang on.
User48: I misunderstood.
User6: np :)
User48: I'm getting the progressbar notification on my T61
User48: Let me update and make sure I'm on the latest package.
User6: User48 dmandell (and Pici) are seeing the problem, so anything you can have them do to help diagnose would rock (if you can reproduce it yourself).
User48: I'm updating now.
User45: top
User48: User6 I just did an update and restarted my T61 and the volume progress notification is still working for me.
User6: User48 okay, please work with dmandell, he's the one seeing the issue.  :)
User6: heya mneptok
User49: User6 ahoyhoy!
User49: User6 you going to be in town around the middle of June?
User49: (PDX)
User45: User48 Anything I should do to debug?
User6: User49 I think so, yes, drop me a line.  :)
User48: User45 I'm not familiar with this code yet.  Let me take a look in it.
User45: Ok.
User48: dbarth did the gsd patches I think, but he's not around right now.
User48: User45 You're up-to-date right?  And you reset after your last update?
User49: User6 roger roger
User45: User48 I updated yesterday to see if the problem had been fixed, rebooted after the update.
User48: Okay, just checking.
User45: I can do it today to rule that out as a problem.
User48: I'm looking through the code, but I'm not really sure what to be looking for yet.  I should talk to dbarth probably since he's more familiar with it.
User14: User6 oh, it's about the volume buttons?
User14: User6 the path is roughly like this:
User14: User6 keypress -> kernel -> evdev event KEY_VOLUMEUP -> X.org -> X.org key Event XF86VolumeUp -> gnome-settings-daemon -> call libnotify to produce volume up notification -> dbus -> notify-osd picks it up and draws bubble
User14: a|wen-: hi
User50: User14 where does the actual sound volume adjustment occur in that pipeline?
User14: User50 that's also g-s-d, triggering the mixer when it receives the keypress
User50: User14 cool, thanks.
User14: sbeattie, User6 if you strace -p `pidof gnome-settings-daemon` and press the button, you should see some open("/dev/snd/controlC0", O_RDWR) fiddling
User14: and in dbus-monitor there should be something like http://paste.ubuntu.com/152308/
User14: i. e. g-s-d sending to dest=org.freedesktop.Notifications the notification-audio-volume-high message
User14: a|wen-: right; it's much easier (and rare) to reject something from the queue than to have the uploader wait for another round of bug ping pong
User14: a|wen-: however, that's standard practice for main; if motu-sru wants ack-before-upload, that's totally fine for me
User14: a|wen-: just let me know what you decide, so that I stick to it
User14: a|wen-: right now, my practice is that when I see an universe upload in the queue, I look at the bug and check if it's ack'ed; if not, I sub motu-sru and ask for ack
User44: dmandell - for the volume notification issue, it might be useful to do "killall gnome-settings-daemon; gnome-settings-daemon --debug --no-daemon" and attach the output to the bug report when you hit the volume key
User44: g-s-d is quite verbose in debug mode
User45: User44 No output at all from hitting volume key
User44: very strange
User44: if you completely kill gnome-settings-daemon and then hit the volume key, then does the volume change?
User44: it shouldn't, but i just wonder if you've got something else that grabs the key (very unlikely)
User44: i should check to see if i get debug output on volume change actually;)
User44: i get this output each time i hit the volume key:
User44: ** (gnome-settings-daemon:28950): DEBUG: Using volume step of 6
User44: you don't see that no?
User12: Keybuk, I keep forgetting that movie exists, ever since the sequels
User51: User12 http://xkcd.org/566/ (the bottom one)
User15: User45 there?
User45: seb123: I'm back
User45: seb123: Went to lunch.
User15: User45 I was not there before but I read the bug, what hardware do you have? do you event for those keys in xev?
User45: User44 The volume buttons on my T60 stlil work with gnome-settings-daemon disabled.
User44: right#something else has to be grabbing the volume button
User44: wierd
User45: seb123:  I'm just a normal user, I don't think I'm doing anything weird, how would I check xev?
User45: User44 Per the bug, this worked in Jaunty until fairly recently, I haven't made any config changes in that time, just apt-get updates.
User15: User45 open a command line and type "xev"
User44: dmandell - my volume doesn't change when i kill gnome-settings-daemon
User15: User44 hi, you get the bug too?
User44: no, it works fine for me
User45: when I start gnome-settings-daemon --debug --no-daemon, I see the following:
User45: ** (gnome-settings-daemon:25566): DEBUG: Unable to parse: 'XF86AudioMedia'
User45: Not sure if it has anything to do with anything, but it's audio related so I thought I'd bring it up.
User44: dmandell - what does xev show when you press the key with no gnome-settings-daemon running?
User15: User45 should not, could you run xev and see what events you get for those keys?
User15: User44 could be bug #357673 but it doesn't have lot of details, still good to debug it
User45: nothing in xev
User16: Launchpad bug 357673 in gnome-settings-daemon "No notification when sliding audio volume on X31" [Low,Incomplete] https://launchpad.net/bugs/357673
User15: User45 is g-s-d running?
User15: does stopping it makes a difference?
User45: User15 yes
User45: (running)
User44: you should kill it first
User15: User44 you think that g-s-d grab events and do nothing with those?
User45: no, killing it doesn't make a difference.
User44: seb128 - i think there is something else on the system grabbing the key
User52: hmm, did Gnome switch to git today?
User15: ok, so sounds similar to #357673
User44: dmandell says that the volume still changes with no g-s-d running at all
User15: User52 they are in the middle of it not sure if it's done yet
User15: User44 his laptop might have those cabled, ie acting on an hardware level
User52: User15 does that mean any bzr mirrors or bzr-svn branches are going to not work now?
User15: User52 that would be a question for #launchpad rather I guess
User44: seb128 - quite possible, but they worked at some point before
User52: User15 right, just thought you might know
User15: User44 before today or before a linux or xorg update? ;-)
User15: User52 no, I don't use bzr imports, I use svn directly usually
User15: it's faster and less buggy (no outdated imports)
 * chrisccoulson finds it very confusing to understand how keypresses get from the hardware to an application
User52: User15 ah, but I guess you'll have to switch to git or find a bzr <-> git method
User15: User52 I'm not using bzr to work on GNOME so I've nothing to switch really
User15: User52 we only have the debian directory in bzr for desktop packages and we use tarballs
User45: User15 the timeframe of bug 357673 approximately matches my own.  I think I lost volume notifications at around the same time.
User16: Launchpad bug 357673 in gnome-settings-daemon "No notification when sliding audio volume on X31" [Low,Incomplete] https://launchpad.net/bugs/357673
User44: dmandell - could you switch to a terminal (CTRL+ALT+F1), and run "sudo showkey -k" and press the volume button
User44: do you see any keycodes when you do that?
User52: User15 ah, I thought you were doing more upstream stuff so that you'd often want VCS checkouts
User52: User15 anyway, I'll ask #launchpad
User15: User44 https://wiki.ubuntu.com/Hotkeys/Troubleshooting is quite detailed
User44: thanks seb128 - i'll have a read of that
User15: User45 you might want to follow instructions on https://wiki.ubuntu.com/Hotkeys/Troubleshooting too
User51: I didnât read the bug report, but i think some package changed something so that the volume control keys donât control software volume *at all*, since they canât be prevented from controlling the hardware volume. Thatâs probably why thereâs no indicator.
User45: User44 nothing happens
User45: no keycodes
User44: dmandell - that's wierd, so the kernel is not producing any keypress event at all
User15: User45 do you still have old linux versions installed you can boot?
User51: User44 Thatâs probably an intentional workaround.
User45: User15  I may, hold on.
User44: thanks ion_ - is there a reference to that somewhere? do you know what changed?
User51: hotkey-setup (0.1-23ubuntu10): * Drop the override of the hotkey mask for ThinkPads.  This is currently used for brightness keys, volume keys, and the ThinkVantage button: - overriding the volume keys causes double-stepping of the volume, because the volume was also being adjusted in the hardware mixer, which we can't disable - so we don't want these keys exposed for now. LP: #355300.
User44: ion_ - thanks
User44: dmandell^^^
User44: looks a likely suspect for your issue
User15: and that was uploaded around the time where it broke
User15: bug #357673 is on 2009-04-08
User16: Launchpad bug 357673 in gnome-settings-daemon "No notification when sliding audio volume on X31" [Low,Incomplete] https://launchpad.net/bugs/357673
User6: User51 what's the correct fix for this?
User51: User6 I havenât investigated the issue, but probably either finding a way to disable the hardware mixer control, or making the keys control the indicator but *not* software volume.
User51: The latter one would probably be a bit of a kluge.
 * kees 's head spins
User6: User51 so prior to that fix, pressing volume keys on that hardware would double-step?
User51: Yes
User51: The behavior used to be such that like 80% of the volume indicator would be equivalent to total silence and the last 20% would suddenly raise the volume.
User6: icky.  :)
User53: can you try deselecting the relevant tracks using system> preferences> sound> devices> default mixer tracks ?
User53: s/relevant tracks/relevant mixer elements/
User51: Which makes sense if you plot [0:1] x*x
* slangasek changed the topic of #ubuntu-devel to: Archive: release freeze | Ubuntu 9.04 RC candidate released! | Development of Ubuntu (not support, not app development on Ubuntu) | #ubuntu for support and general discussion for dapper-intrepid | #ubuntu-motu for getting involved in development | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu.com/HelpingWithBugs
User2: User9 "RC candidate"? :-)
User54: heh
User3: Courtesy of the Department of Redundancy Department :)
 * jdong starts seeding the .torrent torrent
User3: Oh, do torrents need seeds? I have bandwidth I can throw at the problem, too
User55: User3 throw it, and see if there are catchers
User56: User25 about status of irda-utils bugs?
User57: I am remastering a Ubuntu Server 8.04 LTS CD with a preseed file. I would like to include some packages on the CD to avoid grabbing them from the internet. Can anyone help me or tell me when I can get help?
User3: User57 You want to look at https://help.ubuntu.com/community/InstallCDCustomization
User57: User3 thats where I started
User58: User33 What happened to the animal theme for the desktop background?
User30: akgraner, good question. i kept the default wallpaper for hardy & intrepid, but jaunty has pushed me towards nabbing something else
User58: User30 I was waiting for it, just downloaded the updates and was notified that the RC was done...Was hoping the last update would have the artwork.
User58: well the animal artwork I mean...
User59: User58 hi
User59: I hear you were asking about default artwork?
User60: User58 hi
User58: User59 hi
User58: User59 yes...I was asking about the artwork
User59: sorry I missed it
User59: I hear through the irc grapevine you're looking for a bunny with antlers?
User59: :)
User33: User58 I wouldn't go so far as to say there is a theme...the wallpaper has changed in different ways for each release.  these days, the design team develops it and we just drop it in
User58: User59 yes...I was hoping with last updates I installed, when I did the reboot a Jackalope would appear...I was a little disappointed...
User59: too bad
User59: I'm sorry you're dissapointed
User58: I liked the charm of that..was an announcement I missed.
User59: User67 is there not a different background that would suit with one of the alternate themes?
User59: User58 I don't think you missed an announcement
User59: like mdz says, we just help out the art team by dropping in their great work
User33: User58 why did you expect to see a jackalope on your wallpaper?
User52: extrapolation from a data set of 2?
User58: User59 maybe I'm just to new...well there was ipex and a heron...
User59: yeah
User58: so I guess I just expected a jackalope
User59: User58 you're right, the totally abstract background is a break from tradition
User59: but I think there are some good jackalope backgrounds out there
 * ScottK would have enjoyed Bassalope, but is many releases too late for that.
User61: join #launchpad
 * ScottK hands ikus060 a '/'
User59: I personally like how the new background has elements that are picked up elsewhere, like the default search page and such
User59: I think kwwii, our resident artist is in Germany, so it's late there, but he'll be able to connect you with some of the community submitted themes that have the jackalopes
User58: User59 I thought something that would break a tradition would have been discussed, that's why I asked if I missed something....
User52: User58 well, the animal theme was new for Hardy
User59: User58 honestly, I don't know where it was discussed, I know the current background has been in the product for quite a while, since the week before visual freeze
User59: I wish I tracked this more, but I think there's a way for community members to submit themes and such, so I know it's a totally public deciscion
User58: User59 yes the current one as been there I just thought the final *pop* would be the animal showing up...that's all...
User54: is it possible to have comments in the control file?
User59: hehe
User33: User58 8.04 was, I believe, the first release to have animal-themed wallpaper.  if there was a tradition, the people making the wallpaper didn't know about it :-)
User58: User59 I'll go on a virtual hunt for the jackalope...just wish I had known it wasn't going to be there..I was *really* waiting to see it...
User29: User54 yes.  leading '#'
User58: User33 see I blame on being the newbie..:)
User58: blame it I mean
User29: rickspencer3 and User58 There is a package called community-themes
User59: User58 I invite you to come back tomorrow in (what is your) morning
User59: ScottK - thanks
User58: cool thanks!
User58: User59 ok..
User58: User59 what time and for what?
User59: User67 will be here, he's a really good guy and is generally in charge of our artwork, perhaps you will meet in Barcelona
User54: User29 ok cool :)
User29: User54 I use it all the time to stub out misbehaving binaries.
User62: did i miss something? is there going to be a 9.06?
User54: User29 cool :)
User2: User62 ...
User54: User29 i'm working on repackaging OOo and using it for better documenting
User58: User59 ok  thank you, I'm afraid I won't be able to make Spain...:(
User59: oh bummer
User59: you know me and Pete work together right?
User59: my wife couldn't make Barcelona either
User58: User59 I do now
User62: User2 someone posted to -devel about a problem with 9.06 installing netbook-remix
User59: User58 let me know how the background works out for you
User59: ttyl
User58: User59 I will, Thanks..:)
User54: User58 maybe you can make it to 10.04 UDS :)
User54: User58 it should be somewhere in the US
User58: User54 I hope one day...:)
User2: User62 typo
User2: or possibly abject confusion
User58: User54 if not I've already been talking to Outback steak houses for release parties..:)
User63: User19 I know that Dougie Richardson was interested in helping out with UNR documentation, I'm unlikely to be able to help until the end of Sunday but if you post to ubuntu-doc I'm pretty sure you'll get a bite
User2: User62 the mail is very confusing and suggests that perhaps they were getting an image from somewhere entirely different, not us
User62: probably
User58: thanks ya'll for info...be back tomorrow..:)
User60: User58 what theme colour would you like for KK? not sure if we are going Green (that would be too much openSUSE)
User64: User58 http://kiriyard.com/2009/03/sarusaslu-jaunty-jackalope/
User58: User64 me goes to look
User19: User63 We posted, but are held for moderation I think
User19: User63 Thanks
User58: User60 I need to think about that question...
User58: User64 Thanks!  Great site...:)
User60: humm we are going out of raibow colours lol
User65: User58 Outback Steak House for a release party? Oh, there has to be something better ... :-)
User60: already used most of the brownish
User64: User58 no problem
User60: suse is grean, redhat is redish
User60: and KDE uses all it can from blue and black
User58: User65 there are but the Koala theme...seemed to go with it...and the bar areas are cool....:)
User60: User58 are you imagining kk yellow? LOL
User63: User19 did you post with an Ubuntu or Canonical address?
User65: Argh, yellow is bad.
User65: Yellow would require developers to wear sunglasses to use the release
User19: User63 ubuntu
User63: User19 nothing in the moderation queue
User63: User19 those addresses should be whitelisted anyhow
User19: User63 Might have gone through then -- I'm not sub-ed
User19: User63 Right
User60: User65 ehehe
User63: User19 I don't see anything
User19: User63 http://article.gmane.org/gmane.linux.ubuntu.doc/12370
User19: largish thread already
User19: User63 It's in the middle of it, sorry
User2: User19 FYI, pi-makelist-vfat seems to have broken with the partitioned armel images
User63: User19 ok, I see that, but it doesn't look lik a request for help. Better to start a new thread and clearly request assistance :)
User19: User2 I think you had fixed that; it borke again?
User2: User19 if I remove the 2>/dev/null | sed from the end, I get http://paste.ubuntu.com/152384/
User2: definitely broke, we're seeing zero-sized .list files
User19: User2 That's bad; that's when a tool doesn't want LBA but only CHS addresses for partitions or verifies that they match both
User25: erm
User2: can I leave it with you?
User25: did you add a ~/.mtoolsrc ?
User2: yes
User19: User2 Yeah except I don't know what to do
User2: see debian-cd/tools/pi-makelist-vfat
User2: User19 you say that as if I do ;-)
User19: I guess I have to compute CHS and LBA compliant addresses; but I don't know how parted picks them
User19: The thing is that parted seems to change the disks' CHS depending on the partitions you create
User19: That is if you "parted mkpart" twice, you see different CHS values for the disk
User2: if you can't figure it out, I can have a look tomorrow, maybe
User2: I know where to look for parted's CHS handling, at least roughly, but I don't know offhand how it behaves or how to control it
User19: I'll try to fix it; I was hoping never to have to do that but it seems I was lucky until now
 * ogra doesnt see the mtools_skip_check=1 in the MTOOLSRC ...
User25: i think mtools need that for all image operations
User25: if you dont use actual devices
User19: User63 Point taken; will write a new email asking explicitely
User63: User19 roger. If nothing happens by the weekend, I'll lend a hand
User19: User25 That looks like a good setting to avoid touching this stuff altogether  :-)
User25: heh
User19: User63 I'll wait til Tobin tries out various image writing tool and include his description in the list of things to help with; thanks
User63: User19 ok
User3: Looking at bug #356861, is the security team not going to handle the Jaunty upload? So I should find a sponsor?
User16: Launchpad bug 356861 in openafs "OpenAFS Security Advisories 2009-001 and 2009-002" [Undecided,In progress] https://launchpad.net/bugs/356861
User6: User3 for jaunty, you need to clear it with motu-release since jaunty is frozen.
User66: could anybody help me setup bzr to work with a proxy that requires authentication? =/
User2: User66 #bzr is probably a better place to ask
User3: Any motu-release types around to OK?
User19: User2 Sorry which image borke for armel?  live or alternate?
User66: User2 it was down a while ago, but I guess it's up now... thanks!
User2: User19 I was looking at desktop, but both seem to have the problem
User2: User66 that could only have been the server; individual channels on the same IRC server can't really be down independently
User66: User2 whatever it was, it wasn't connecting :)
User53: User3 i've pinged a -release member in -motu
User19: User25 What was the syntax to use skip_check in mtoolsrc?
User25: lool, well, whats said in the error message ;)
User25: mtools_skip_check=1
User19: User25 I should learn to read really
User57: I do I prevent ppp-udeb to be loaded by the ubuntu installer OR how do I skip the detection with a preseed?
User57: How do I prevent ppp-udeb to be loaded by the ubuntu installer OR how do I skip the detection with a preseed?
User19: ogra, User2 No, the skip_check isn't enough
User19: damn
User25: but its definately needed if you work with images
User25: so keep it
User19: User25 Why?
User25: no idea, but i cant work with images with mcopy or mdir if i dont have it set ... i think it was explained in the manpage somewhere
User25: All the Mtools commands perform a few sanity checks before going ahead, to make sure that the disk is indeed an MS-DOS disk (as opposed  to,  say  an  ext2  or  minix
User25: disk). These checks may reject partially corrupted disks, which might otherwise still be readable. To avoid these checks, set the MTOOLS_SKIP_CHECK environmental variable or the corresponding configuration file variable (see section  global variables)
User19: Yes it wasn't needed so far
User19: So I'd better keep the safety checks if disabling them isn't enough and they used to pass
User57: cody-somerville>Ubuntu 8.04 LTS Server
User25: i never managed to work with mtools on images without them
User25: i remember i used to set MTOOLS_SKIP_CHECK in former scripts i did, nowadays i just have it in mtoolsrc
User57: cody-somerville: I remastered the CD image with some extra packages and now it's failing detection pppoe concentrators. Which is BAD because I want the process to be fully automated.
User57: cody-somerville: the worst part is I don't use pppoe
User57: cody-somerville: no never
User57: cody-somerville: only since I added extra packages
User57: cody-somerville: I can't seem to find what d-i directive to use to skip it
User57: cody-somerville: I wish there was a list
User57: really
User57: crap ok
 * calc is beginning to think that the only reason multiple OOo can't be installed at the same time is due to buggy packaging (nothing in upstream itself)
User4: User54 is there ever a better reason for why you can't install the same package to two prefixes?
User54: User4 well its already essentially doing that by default, the debian packaging just changes it to be in a non-versioned prefix
User54: at least afaict so far
User54: OOo doesn't exactly follow the FHS
User54: which makes it fairly easy to do the multiple install
User4: meh the FHS is a "recommendation"
 * jdong watches the pitchforks come
User54: User4 sticking arch indep data into /usr/lib isn't exactly a good idea
User4: ok that's a bit painful.
User54: User4 and as far as debian is concerned FHS isn't just a recommendation its required
User54: of course some debian packages are thus buggy when it is too painful to try to fix them
User54: there are 6 noted exceptions to FHS in policy
User4: right.
User4: I see the merit, but it does make packaging a lot hairier
User4: how do you put up with OOo packaging anyway? isn't there a good 6-8 hours of pipeline latency when you build a package? :)
User6: User14 I seem to have both /etc/default/apport and /etc/default/apport.default :(
User44: kees - there's a bug report for that already isn't there?
User54: User4 for a cached build it takes ~ 1-2hr
User6: User44 oh, dunno
User54: User4 for the buildds it takes ~ 36hr before they are all done (armel is really slow)
User4: ah I see
User4: at least caching makes it bearable then
User44: kees - bug 361543
User16: Launchpad bug 361543 in apport "/etc/default/apport mistakenly installed as /etc/default/apport.default" [Medium,Fix committed] https://launchpad.net/bugs/361543
User6: User44 thanks
User54: User4 yea
User54: User4 aiui there is a better c++ linker that might help as well in binutils but it is still experimental
User67: lol, I put mascots in the wallpapers and kinda felt the heat for it, and now we don't use them and people miss them, funny that
User67: if it makes anyone feel better there is already a bunch of work going on in the ubuntu-artwork team creating koala pics ;)
User67: personaly, I prefer my desktop without a mascot
User54: User67 yes... no matter what you do it is wrong ;-)
User3: I thought the Ibex was really well done. I swear I looked at the background for at least 2 months before even realizing it was supposed to be an Ibex
User4: User67 I'm thinking animated wallpapers
User4: like maybe with a jackalope and if you click it it runs across and shatters some desktop icons
User4: courtesy of compiz?
 * ebroder twitches
User68: Anyone here familiar with the new notify-osd?
User68: I am thinking of bug 338695 where lowresimages appears in the bubbles, in the case with pidgin it appears that they do not actually have a highresversion of the icon in question and therefore we see a lowresicon, would the way to go in this case be to file a bug against pidgin for not providing scalable images, or at least highresversions?
User16: Launchpad bug 338695 in rhythmbox "low res icons for notifications" [Undecided,New] https://launchpad.net/bugs/338695
User2: User57 your remastering has probably set incorrect Priority fields; compare the Priority fields in your Packages files against those in the archive
User2: User57 also look through the installer's syslog to see which udebs it's loading; it generally includes a brief explanation of why
User2: cody-somerville: http://lists.debian.org/debian-boot/2004/07/msg01207.html
User2: in brief, by default it loads Priority: standard and above, and anything installed explicitly using an anna-install command (and the dependencies of both of those, of course)
User2: or the Enhances thing I mention; I forget whether I ever looked into how that really behaves
ubuntu-devel
Ubuntu IRC