/srv/irclogs.ubuntu.com/2009/02/10/#ubuntu-devel.txt

btQuarkhello :D00:54
btQuarkany idea in what ubuntu the a dri2-enabled radeon driver might appear?00:55
RAOFbtQuark: You'd probably be better off in #ubuntu-x, but the answer is "9.10, most likely"01:16
btQuarkw00, there is a channel only for the x nice :D01:17
btQuarkthe fglrx is horribly cruel01:18
btQuarkbig fail01:18
Dante_JGreetings room.03:51
* Dante_J waves03:51
RAOFDante_J: Incidentally, have you looked for/filed launchpad bugs on these issues?  That'd be the normal way to raise such things.03:56
Dante_JHi RAOF, I did scan through launchpad, but these Vuls are rather large one's that are cross distro and in some cases cross platform (Firefox). I took for granted that there would be a Ubuntu security team that would keen on top of vulnerabilities with mitigating patches available.03:58
Dante_Jand when I look at https://lists.ubuntu.com/archives/ubuntu-security-announce/ there are no patches mentioned for All of February, this seemed to be to be highly unusual, as though some kind of infrastructure or process was broken. The patches for Vulns are out there being applied by others.04:00
Dante_JAnd as I mentioned in #ubuntu-motu, Hardy is used by corporates and lab maintainers specifically because it's LTS. When you're primary browser is not patched now for about a week after the upstream patch was made available, it seems unusual to me. http://secunia.com/advisories/33799/04:02
ScottKDante_J: I think an update is coming soon.04:03
ScottKLaserJock: I thought Bug #323447 was one you might want to have a look at.04:03
ubottuLaunchpad bug 323447 in kdeedu "Klatin not available in intrepid" [Undecided,Won't fix] https://launchpad.net/bugs/32344704:03
Dante_JScottK: for Firefox? thank you. what about sudo, and NSS and others?04:04
ScottKYes, for Firefox.  I know our security team keeps track of such things and generally prioritizes them for resolution.  It does take time to integrate the upstream fixes and get them tested.04:05
Dante_JRegarding sudo: http://www.auscert.org.au/render.html?it=1046204:05
dtchen(accounting for travel to/from recent sprints)04:05
AmaranthI wish the sudo one gave more details so you could see how serious the bug actually was04:07
* Amaranth doesn't feel like looking into diffs04:07
Dante_JIn #ubuntu-motu I mooted a comparison of https://lists.ubuntu.com/archives/ubuntu-security-announce/ with https://www.redhat.com/archives/fedora-package-announce/ and that there were a number of packages patched by fedora that have not been in Ubuntu. Firefox & sudo prominent among them.04:08
ScottKDante_J: Hardy doesn't have a vulnerable version.04:08
Dante_JScottK: of Firefox or sudo?04:08
ScottKSudo04:08
ScottKhttp://web.nvd.nist.gov/view/vuln/search?execution=e2s204:08
Amaranthand firefox updates take some time04:09
ScottK      sudo | 1.6.9p10-1ubuntu3.3 | hardy-updates | source, amd64, i38604:09
AmaranthSince we don't just update to the latest version of firefox because they always include non-security changes as well04:09
ScottKAmaranth: Actually we do.04:09
AmaranthScottK: When did that change?04:10
* Amaranth has been gone for a bit04:10
ScottKWe stay within the major version, but Hardy has 3.0, so it'll get the 3.0.whatever.04:10
Amaranthhuh04:10
ScottKAbout the time Mozilla corp said you can't ship anything other than what we say you can ship if you want to call it firefox.04:11
AmaranthSo intrepid?04:11
AmaranthBecause I know at least pre-hardy that wasn't how it worked and I thought that was only done once in hardy but I know they got a lot more strict about such things recently04:12
AmaranthEither way, firefox updates take time, lots of testing needed there04:12
ScottKYes.04:13
ScottKRmadison says 3.06 is in Jaunty already.04:13
Amaranthjaunty can break, no one cares that much04:13
ScottKSo I imagine its coming soonish.04:13
Amaranthsure04:13
AmaranthJust saying it needs some time04:13
ScottKAgreed.04:13
ScottKAlso we ended up getting stuck on LTS support for Firefox in Dapper.  Asac is lead of a distro based 'upstrea' project for mozilla 1.8/Firefox 1.5.04:14
ScottKAdd an 'm' in there somewhere.04:15
Dante_JAmaranth: ScottK: Thanks for the information, I certainly appreciate it.04:16
ScottKDante_J: In the future though it'd probably be decent of you to spend a couple of minutes searching the web before getting too excited.04:16
Dante_JI did, that's why I'm here. Other distros, and not just Fedora have been patching more aggressively than Ubuntu.04:17
ScottKThe CVE that gave the versions affected for sudo was referenced in the web page you gave me.04:17
Dante_Jand the dearth of patches in Ubuntu of _anything_ for February seemed unusual to me. That's all. So I'm here to check nothing is broken and all is ok.04:18
Dante_Jslow is better than broken.04:18
Dante_Jbut when things get too laggy, then the difference narrows.04:19
keesDante_J: the sudo update is coming, as is firefox.  there was a week-long meeting that ate the first week of Feb with regard to security updates.04:22
ScottKReading some of the bugs, I'm not immediately convinced our default configuration in Intrepid would expose this bug.04:22
* ScottK is certain kees knows though.04:23
keesDante_J: and, as ScottK just mentioned, the sudo issue isn't very high priority, but certainly will be fixed.04:23
ScottKThat would be another reason it might be delayed.04:24
Dante_Jkees: Thank you kindly for the info. It's appreciated.04:24
keesDante_J: the full list for main is here: http://people.ubuntu.com/~ubuntu-security/cve/open.html04:24
keeseach CVE links back to the Ubuntu CVE entry with priorities, notes, patches, bug links, etc.04:24
Dante_JWow, I've been looking for the Ubuntu CVE tracker before! Great link, thanks!04:25
Dante_JA brilliant help!04:25
keesno problemo.  :)04:25
Dante_JI'll pass this on to the AusCERT chaps in case they're not aware. Very nice. :)04:26
Dante_JDo you mind if I pass it on kees ?04:27
keesDante_J: sure, doesn't bother me; it's the reality of our tracker.  :)04:28
Dante_JIt's a useful resource, especially for a security group keeping tabs on who has patched what. eg. http://www.auscert.org.au/render.html?cid=104:29
* kees nods. The raw data might be interesting too (that's linked from the bzr tree at the top of the url I gave)04:30
Dante_Jand lets face it, Ubuntu is now important infrastructure for a growing number of people, so this information is valuable.04:30
keesI don't envy cross-distro CVE fix tracking -- it's hard enough just tracking one distro.  :)04:30
keesindeed04:30
Dante_Jamen brother !04:30
* Dante_J Dips his hat in respect for the good work done here.04:37
Dante_JCheers people, thanks for your help.04:37
Dante_Jkees: Thanks to you especially.04:38
LaserJockScottK: sorry, was afk, thanks for taking care of it04:39
ScottKLaserJock: No trouble.  I only hit it because I was intrigued by the tad 'needs kde3'04:39
ScottKLaserJock: It does seem that someone might want to write up a "If you used to use Klatin ..." wiki page or seomthing.04:40
ScottKsomething even.04:40
LaserJockScottK: I think I'm going to do that in the Release Notes04:40
ScottKOK.  Well we'd want it for the Intrepid release notes ....04:41
ScottK;-)04:41
LaserJockScottK: yeah, well ...04:41
LaserJockman, I really wish there was a way to extract out separate patches for debian/04:46
dholbachgood morning05:28
ion_ing05:31
LaserJockkees: you still up?06:13
nixternalgo to bed LaserJock !!!06:22
LaserJockpfft06:27
=== bluesmoke is now known as Amaranth
pittiGood morning07:24
directhexis it? looks pretty crappy out07:25
pittiyeah, just starts raining07:26
* lool waves07:51
pittihey lool08:04
asacScottK: fwiw, the main reason for ffox updates being late this time was us being at a sprint when they released. usually we release the day after upstream releases :)08:58
asacAmaranth: ^^ ;)08:59
seb128superm1: hi, why did you open a g-c-c task on bug #319725?09:24
ubottuLaunchpad bug 319725 in dell "[Studio XPS 13, Inspiron 531, Studio 16] gnome-settings-daemon crash" [Undecided,Confirmed] https://launchpad.net/bugs/31972509:24
loolKeybuk: configure.ac:23: error: Autoconf version 2.63 or higher is required09:48
loolKeybuk: We're lagging!!09:49
lool:-P09:49
lool(pulseaudio)09:49
seb128Keybuk: there is a libtool sponsoring request waiting for you for a while btw09:51
=== sabdfl2 is now known as sabdfl
apwanyone know why we have no alternate installer cd's today?10:18
apwcjwatson, who 'owns' the iso build process?10:22
amitkI wish there were jigido images for amd64 desktops too10:24
apwthere are alternate installer jigdo's by the looks fo things for amd6410:25
apwamitk, though i have found once you have one cd image, they rsync pretty well10:27
maxbI assume there's no desktop jigdos because so much of the desktop cd is the non-jigdo-able livefs10:31
StevenKmaxb: Right.10:31
StevenKapw: The 'ubuntu-cdimage' team owns the CD builds10:32
apwand where does one find them?10:32
maxbthough I'd still find a desktop jigdo convenient for saving the few hundred MB of packages which aren't in the livefs10:32
StevenKapw: launchpad.net/~ubuntu-cdimage lists the members10:32
StevenKapw: But I'm checking10:33
cjwatsonsometimes CD builds fail for one reason or another10:33
apwheh steve and colin ... is there anything they don't do10:33
cjwatsonmaxb: it's a few tens of MB, not a few hundred10:33
StevenKAnd what cjwatson said10:33
cjwatsonmaxb: if it were a few hundred, it'd be worth it10:33
apwStevenK, apparently you are on the hook too :)10:33
StevenKapw: Which Steve, there are at least in that team :-P10:33
StevenK*at least two10:33
apwindeed.  i was thinking on slangasek10:34
cjwatsonhttp://people.ubuntu.com/~ubuntu-archive/cd-build-logs/ubuntu/jaunty/daily-20090210.log <- today's build log10:34
cjwatsonI expect I broke it in some silly way10:34
* StevenK waits for it to download, fully expecting that cjwatson has fixed the problem before it loads fully10:35
apwthats like massive10:35
cjwatsondid somebody change the kernel ABI again?10:35
StevenKYeah, -7 was ACCEPTed on Friday, I think10:35
cjwatsonyes - and SOMEBODY NBSed the old packages before we updated d-i10:35
cjwatsonplease don't do that10:35
slangasekapw: "is there anything they don't do" - I don't touch the kernel ;)10:36
cjwatsonI'll update d-i now, which will fix it10:36
StevenKcjwatson: Shall I update the platform seed?10:36
apwslangasek, cirtainly doesn't include sleeping10:36
cjwatsonStevenK: let me do it together with d-i10:36
slangasekmumble10:36
StevenKcjwatson: Sure10:36
cjwatsonStevenK: were you the NBS-remover in this case?10:37
slangasekcjwatson: no, that was me10:37
StevenKcjwatson: I've not logged into cocoplum for two days due to flying and such10:37
cjwatsonok, please be less trigger-happy :)10:37
slangasekcjwatson: or should I make it a policy to upload d-i at the same time, instead?10:37
StevenKWhy does everyone think NBS is always me? :-)10:37
slangasekI nuked them because I knew the new kernel was accepted, and having them there makes the NBS list unreadable10:38
slangasekfwiw, we should probably document the kernel NBS specialness in ArchiveAdministration10:38
cjwatsonslangasek: if you take care of d-i at the same time, certainly - but the old kernel definitely shouldn't be removed until d-i is updated to the new one, otherwise we lose out on daily-build testing time10:38
cjwatsonStevenK: it usually is ;-)10:38
slangasekcjwatson: well, ok10:39
cjwatsonI'll document that10:39
apwcjwatson, how come we have live and not alternate cd's i'd expect both to be affected10:39
apwgiven that ironically the latter is useful without being bootable and the former not10:40
cjwatsonapw: 'cos the alternate CD requires a package upload to change kernel versions, and the live CD doesn't10:40
StevenKapw: Since the alternate is locked to the kernel ABI, the live isn't10:40
apwhmmm ... sounds liek the alternate needs to learn something from the live to me10:41
apwanyhow, glad its fixed.  i can see why you love it when we bump the abi10:42
cjwatsonit's a radically different build process, not easily changed to take account of this10:42
cjwatsonfact is that the installer ships objects which are on archive.ubuntu.com, and any such object requires an upload to change10:42
cjwatsonwe used to have automatic daily builds of the installer, although even those didn't take account of ABI changes so when that broke with the switch to Soyuz we stopped bothering10:43
cjwatsonapw: thanks for the note10:43
apwis there something the kernel team should be doing there?  as a step after linux-meta or something?10:43
cjwatsonapw: you guys already mail ubuntu-installer - I just hadn't caught up on mail10:44
apwgood enough, as long as we are not failing process10:44
cjwatsonI might do a quick CD rebuild later - I was waiting for today's CDs myself to test some things10:45
cjwatsonslangasek: (in general I have no objection to the set of people who upload d-i all the time not being just me ;-) )10:46
slangasekright :)10:46
* directhex uploads d-i10:48
cjwatson... for a good reason10:51
Keybuklool: we could sync that from experimental11:09
loolKeybuk: I'm happy if you think that's ok11:10
loolI certainly am not confident to ask that myself11:10
Keybuklool: let me look at the changelog, if I'm happy, I'll do it11:10
ogracjwatson, is there a reciepe online to properly do a testbuild of d-i locally ? dpkg-buildpackage -b seems to not work for me11:14
ogra(i just want to have the netboot binary blob for nslu2 in the end)11:14
cjwatsonogra: how does it fail?11:16
ograit cant find anna11:16
cjwatsondo you use a local mirror?11:16
ograhmm, and it apparently uses my local sources.list11:17
ograheh, yeah11:17
ograhow did you guess :)11:17
* ogra switches that to ports.u.c11:17
cjwatsoneither fix your local mirror to include main/debian-installer, or create a file build/sources.list.udeb.local in the unpacked d-i tree and put 'deb http://archive.ubuntu.com/ubuntu jaunty main/debian-installer' in it11:18
cjwatsonoh, or ports11:18
cjwatsonor perhaps better, copy build/sources.list.udeb to build/sources.list.udeb.local and edit to taste11:18
ograi'm fine switching over ... i just reinstall things to often here to not use a local mirror in general11:18
cjwatsonlikewise, but my local mirror includes d-i :)11:18
cjwatson(funny that)11:19
ograheh11:19
=== ziroday` is now known as ziroday
Keybuklool: looks ok, will upload when make check passes11:20
ograpfft ... now it fails with bootchart-udeb ...11:21
ograbut seems to pull properly from http://ports.ubuntu.com jaunty/main/debian-installer11:21
Keybukwe dropped that11:22
cjwatsonogra: pull newer source; I removed bootchart-udeb in the most recent upload11:22
ograah11:22
StevenKI seem to recall bootchart-udeb in NBS11:22
* cjwatson looks at /usr/lib/pkgconfig/gdk* in confusion11:22
cjwatson/usr/lib/pkgconfig/gdk-directfb-2.0.pc includes cairo-xlib in Requires; /usr/lib/pkgconfig/gdk-x11-2.0.pc doesn't11:22
ograOH ! .... i just noticed for the first time that the jaunty-changes mail contains a direct link to the source packages ... how convenient ...11:23
cjwatsonor d-i is in bzr11:24
cjwatsonif you're going to hack on it anyway you might as well just have a checkout11:24
ograindeed11:24
ogracurrently i'm blindly poking around anyway testing out some theories11:24
ograi'll surely do use bzr for a fix in the end11:25
ograogra@beagle:~$ ls /bin/11:32
ogra-bash: /bin/ls: No such file or directory11:32
ograhmm, i wonder if i should get worried11:32
StevenKogra: echo /bin/*11:32
ograall there ...11:32
ogralooks like libc broke during a dist-upgarde11:33
StevenKOkay, then something /bin/ls links against is missing/broken11:33
ograyeah11:33
ograit properly unpacked libc6 2.9-0ubuntu711:34
ograin the next line i get: dpkg (Unterprozess): Konnte rm nicht zum Aufräumen ausführen: No such file or directory11:34
ograso it cant exec rm directly after unpacking ...11:34
StevenKDoes /lib/ld-linux-*.so exist?11:35
ograogra@beagle:~$ echo /lib/ld-linux-*11:35
ogra/lib/ld-linux-*11:35
ograhmm11:35
StevenKogra: That means no. :-)11:37
ograi dont really care about the system ... takes me 5 min to uncompress the rootfs tarball on the disk ...11:38
StevenKogra: Sure, but I'm curious how it got to that state ...11:38
ograbut i suspect that shouldnt happen during a dist-upgrade :)11:38
StevenKogra: It's recoverable, if you don't mind using echo or a statically compiled cat ...11:39
ograhttp://paste.ubuntu.com/116422/11:39
ograsorry, its german ...11:39
ogralooks like ldconfig is barking at me earlier11:40
ograif anybody is interested in gathering more info from that system, i'll keep it around (not needed anyway atm)11:46
=== tkamppeter_ is now known as tkamppeter
cjwatsonseb128: there's something wrong with our gtk+ patches, that isn't broken in Debian unstable/experimental. /usr/lib/pkgconfig/gdk-directfb-2.0.pc includes cairo-xlib in Requires; /usr/lib/pkgconfig/gdk-x11-2.0.pc doesn't12:16
cjwatsonseb128: it looks like this is a bug in debian/patches/003_gdk.pc_privates.patch, which adds cairo-xlib in the non-explicit-deps case (only used by the directfb build at the moment)12:17
cjwatsonseb128: do you know anything about this?12:17
seb128cjwatson: upstream did add this requirement recently, let me look at how I updated the patch12:25
cjwatsonseb128: I think I might have an idea12:25
seb128cjwatson: what else would you expect?12:25
* cjwatson waits for dpkg-source to get a move on12:25
cjwatsonseb128: I'm thinking of http://paste.ubuntu.com/116434/12:27
dholbachkees: tjaalton just told me that you made my laptop give me only black screens if it boots with "splash" - no idea what he exactly means by that... something with initramfs/usplash?12:27
cjwatsonwhich would result in cairo-xlib ending up in Requires.private of the x11 backend, and not at all in Requires/Requires.private of the directfb backend, which I think is correct?12:28
tjaaltonkees: you updated usplash12:28
Keybukdoko: so, about the java compiler failure on the buildds12:28
Keybukdoko: https://launchpad.net/ubuntu/+source/bootchart/0.9-0ubuntu8keybuk3/+build/858530/+files/buildlog_ubuntu-jaunty-i386.bootchart_0.9-0ubuntu8keybuk3_FAILEDTOBUILD.txt.gz12:28
tjaaltondholbach: the new kernel initramfs got the new usplash first, so the old kernel worked until you regenerated the image12:29
dholbachtjaalton: ah ok12:29
seb128cjwatson: yes, that looks good to me12:29
cjwatsonseb128: ok, I'll do a test build to make sure - shall I upload if it DTRT?12:30
seb128cjwatson: yes12:30
seb128thanks for spotting the error!12:30
cjwatsonno problem, the d-i buildd spotted it really ;-)12:30
dokoKeybuk: buildd only, or local build?12:32
Keybukdoko: buildd only12:32
Keybukbuilds just fine locally in a chroot12:32
KeybukUnable to locate tools.jar. Expected to find it in /usr/lib/jvm/java-6-openjdk/lib/tools.jar12:33
Keybukand12:33
dholbachkees: mjg59 says usplash should do the same thing as "vbetool vgamode 3" *shrug*12:33
Keybuk/build/buildd/bootchart-0.9/build.xml:41: Unable to find a javac compiler;12:33
Keybukcom.sun.tools.javac.Main is not on the classpath.12:33
Keybukseem to be the key bits12:33
Keybukyet it build-depends on java-gcj-compat-dev | java-compiler12:33
cjwatsonisn't that the wrong build-dep now?12:35
cjwatsonhttps://lists.ubuntu.com/archives/ubuntu-devel-announce/2008-July/000460.html12:35
cjwatsonshould use default-jdk-buildddep12:36
cjwatsondefault-jdk-builddep12:36
Keybukwhy jdk?12:36
Keybukoh, I see12:36
dokoKeybuk: I'll upload a new version using default-jdk/default-jre, and setting JAVA_HOME12:37
Keybukok, thanks12:42
ograwow the /usr/share/doc/debian-installer/armbooting.txt really targets ancient stuff :)12:45
loologra: You might be more interested in doc/devel/hardware/arm/nslu2/README12:47
dokoKeybuk: bootchart built12:55
Keybuk\o/12:56
asacjames_w: hmm. debcommit doesnt do the --fixes lp:xxxx magic for me anymore13:00
pittimeh, latest X.org updates break X on GM945 (black screen, nothing in log)13:03
pittibryce, tjaalton: ^ did you hear similar reports already?13:03
beunopitti, same here13:04
beunosince yesterday or the day before13:04
pittivesa works for now13:04
beunopitti, BUT, if you login with the older kernel (2.6.24-21), it works13:06
pittiinteresting13:06
pittiI didn't try 2.6.27-6 yet13:06
beunoI tried it, and it looks less broken, but still doesn't work13:06
beunoI've also been having the wierdest problem with the wireless. It intermintently stops working (transmiting) for 4-5 seconds, and then works again13:07
beunoit does the same thing on different APs/internet connections13:07
tjaaltonpitti: usplash is broken13:11
pittitjaalton: happens without usplash, too13:12
ografor me it worked after dropping the flash13:12
ogra*splash13:12
tjaaltondunno then13:12
* ogra does definately to much ARM work13:12
tjaaltonsiretart: you are probably aware of the annoyance in emacs that you cannot turn off the splash screen in site-start.el.. any way to allow that in the ubuntu package?13:36
Mithrandirtjaalton: you can't?  That's silly.13:36
tjaaltonMithrandir: it's infuriating..13:36
tjaaltonhttp://www.gnu.org/software/emacs/manual/html_node/emacs/Initial-Options.html13:37
MithrandirI have (setq inhibit-splash-screen t) in my personal .emacs, though13:37
tjaaltonthat works13:37
tjaaltonbut there are thousands of users here..13:37
brycepitti: yes I'm getting the same thing, on -intel13:38
Mithrandirmake /usr/bin/emacs a shell script that calls the real binary with `--no-splash'13:38
brycepitti: is there a bug id already?13:38
pittibryce: I didn't file one yet; there might be13:38
bryceI looked yesterday but didn't see one13:38
tjaaltonbryce: there are a couple of issues.. one is that usplash is broken and then the one that pitti is seeing13:39
pittitjaalton: in what way? usplash WFM13:39
brycethe problem I'm seeing is definitely not usplash; also it goes away if vesa is specified13:40
tjaaltonpitti: yes, but it fails to give back the display13:41
tjaaltonMithrandir: that's a possibility, but a bit ugly :)13:41
bryceI suspect it must be an update between thursday and yesterday13:41
tjaaltonbryce: have you tried booting without splash?13:46
brycetjaalton: not yet13:46
* bryce tries13:47
brycetjaalton: huh, came up fine13:51
brycepitti: have you tried booting without usplash?13:52
pittibryce: yes13:52
tjaaltonbryce: like I said :)13:52
pittibryce: same problem13:52
brycetjaalton: is there a bug id on the usplash bug?13:52
tjaaltonbryce: not sure13:52
brycetjaalton: who all is seeing the usplash issue?13:53
kirklandpitti: do you happen to know if there's a wake-on-lan package in main?  etherwake and wakeonlan both are in universe13:53
=== sabdfl1 is now known as sabdfl
brycehttps://bugs.edge.launchpad.net/ubuntu/+source/usplash/+bug/32723013:54
ubottuUbuntu bug 327230 in usplash "Lost all graphics on "Jaunty" after last update." [Undecided,Confirmed]13:54
tjaaltonbryce: dholbach did13:54
brycelet's see what happens booting an earlier kernel13:55
dholbachbryce: it will work until you update the initramfs for that kernel13:55
tjaaltonbryce: usplash is included in the initramfs, so an earlier kernel with an earlier usplash works13:55
bryceah13:56
* surfaz is away: Estoy comiendo, escribir mi nombre para que el Xchat me avise13:56
dholbachsurfaz: do you think you could turn off auto-away in your irc client please?13:57
brycedholbach, tjaalton: you're right; earlier kernel boots fine13:57
brycedupes:  #327610 #327505 #327498 #327444 #32728613:59
tjaaltonyay for having no assigned maintainer ;)14:00
bryce:-/14:00
bryceis there a usplash change we can revert?14:00
Keybuklool: new autoconf in14:01
loolKeybuk: thanksely14:01
Keybukbryce: I think usplash last changed in 184214:01
bryceKeybuk: also on Feb 4th14:01
brycekees probably isn't awake yet though14:02
Keybukhmm, interesting14:02
bryce  * libusplash.{c,h}, usplash.c:14:02
bryce    - Move pulsate and animation pipes into libusplash to unblock animations14:02
bryce      while waiting for stdin (LP: #326709).14:02
bryce    - Process animations between commands to avoid falling behind when14:02
bryce      running in verbose mode.14:02
bryce    - Drop unneeded signal-blocking code.14:02
Keybukit could be unrelated to the patch, but a rebuild that caused it14:02
* bryce nods14:02
brycehowever, there was also a change Jan 21st14:02
bryceso it would have been rebuilt at that point, right?14:03
bryceI still have the previous deb, let me test that14:04
bryceinteresting that for many, this is indistinguishable from an X blank screen14:07
bryceyep, earlier .deb boots fine14:07
=== sean_ is now known as allquixotic
Fenariofreeflying, ping14:25
cjwatsonseb128: I happened to notice that your Maintainer address in gtk+2.0 is @ubuntu.org rather than @ubuntu.com14:30
pittislangasek: oh, just stumbled over https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch ..14:30
pittikirkland: WOL> not that I know of14:31
pittikirkland: if we need one, there's always the MIR route :)14:31
seb128cjwatson: ups, I changed the debian to ubuntu too quickly ;-)14:31
lamontI need a tool to dump a palm-pilot addressbook etc that doesn't blow its brains out when it hits the corruption that is present in my DB...14:33
=== ssweeny_ is now known as ssweeny
loolseb128: Better than debian.com   :-P14:42
seb128;-)14:42
seb128lool: btw since you are there, how busy are you this week? ;-)14:42
loolseb128: What's the highest level of business you know?14:43
seb128lool: would be nice to get pygobject and pygtk updated to their current version, since we are mostly in sync with debian experimental and like working on those ;-)14:43
loolseb128: Ok; I'm noting that down14:43
seb128lool: thanks ;-)14:43
loolseb128: I have insurance, trip report, activity report, and 4 interviews to do this week14:43
loolAnd I'm on IRC!14:44
seb128lool: theorically those updates should not be too hard14:44
* lool /quits14:44
loolOk14:44
seb128I say theorically because you had issues on previous rounds ;-)14:44
seb128thanks!14:44
loolYeah, I wasn't really lucky with pygobject/pygtk so far14:44
loolseb128: I had a conversation at FOSDEM that these will likely be superseded14:44
seb128lool: what, pyg* using gobject introspection?14:45
loolYes14:45
seb128lool: that will require code changes in applications though I guess, no?14:45
seb128ie the api will be different14:45
loolI don't know14:46
pittitseliot: bug 287470 is still open for -173 in jaunty; should that be closed, or does it really need an upload?14:46
ubottuLaunchpad bug 287470 in nvidia-graphics-drivers-177 "package libgl1-mesa-glx 7.2-1ubuntu1 failed to install/upgrade: poging tot overschrijven van `/usr/lib/libGL.so.1', wat ook in pakket nvidia-glx-177 zit" [High,Fix released] https://launchpad.net/bugs/28747014:46
kirklandpitti: cool, i'll put one together, thanks ;-)14:47
racarrlool, seb128: It's not really clear. pybank isn't really actively developed. The API right now is different though14:48
racarrBut very similar, and probably could be the same14:48
loolI guess we could replace pygtk/pygobject with a thin impedance matching layer and ask people to move to the new API14:49
loolAnyway, future stuff I'm not working on and wont work on :)14:50
EagleScreenI have a dude. I am going to do a change in package qtparted, it uses dpatch patches in debian/patches, so I fisrtly will make a dpatch patch with my changes, and later a debdiff with the difference between old and new package, my question is if the changes in the changelog file must go in the dpatch patch, or only in the debdiff patch14:51
bardyrnden14:52
tseliotpitti: the bug report can be marked as "fix released" now14:52
loolEagleScreen: In the debdiff14:52
pittitseliot: great, thanks14:52
seb128tseliot: hey14:52
loolEagleScreen: The dpatch is to hold upstream changes; anything below debian/ shouldn't be in a dpatch and will appear in the debdiff14:52
tseliotseb128: hey14:52
EagleScreenthanks14:53
seb128tseliot: how is the gnome-desktop update going? need any help on that one?14:53
tseliotseb128: I'm still fighting with a few patches, I'm trying to solve the problems with the display capplet and I will let you know about the rest14:53
seb128ok14:54
seb128tseliot: what problems with the capplet?14:54
tseliotseb128: the aspect dropdown patch doesn't apply any longer14:54
seb128tseliot: can you try to get the update done first and then look at the other issues (if that's xrandr 1.2 drivers, etc)? so that would unblock the soname transition and the gnome-settings-daemon and gnome-control-center updates14:54
seb128tseliot: ok, let me know when the update is ready then, I will do some bug triage until then ;-)14:55
tseliotseb128: the g-c-c has the highest priority and I can already give you my patches for gnome-desktop but I would really like to get g-c-c to build first14:56
tseliotalso patches for the network capplet fail to apply, etc.14:56
seb128tseliot: I'm not that much in a hurry, ping me when you will have g-c-c ready and tested14:56
tseliotseb128: ok14:57
pittitkamppeter: interested in joining the desktop team meeting in #u-desktop?14:58
pittitkamppeter: (... at 16:30 UTC)15:01
EagleScreenthen ANY change under debian/ in debdiff?15:02
EagleScreenwhat about updating debian/patches/00list? also in debdiff?15:02
cjwatsonupdating debian/patches/00list in a dpatch would be ... exceptionally twisted15:03
cjwatson(and generally wouldn't work)15:03
EagleScreenthanks Colin15:04
=== bluesmoke_ is now known as Amaranth
EagleScreencjwatson dod you remember15:06
EagleScreenBug #133072:15:06
ubottuLaunchpad bug 133072 in console-setup "tty console doen't show characters with accent" [Undecided,Confirmed] https://launchpad.net/bugs/13307215:06
EagleScreenThis report is public15:06
cjwatsonEagleScreen: yes - have you tried the update to console-setup that's available in intrepid-updates now?15:08
cjwatsonas of December or so15:09
EagleScreensurely yes15:09
EagleScreenconsole-setup 1.25ubuntu4 (intrepid-updates)15:10
EagleScreenit fixes the problem, but it is necessary to run it each time I start Ubuntu15:11
EagleScreenI mean running sudo setupcon each time15:12
EagleScreenmay be some script during boot shuld run it15:13
superm1seb128, that's the app that is crashing in the current development version, gnome-display-properties in jaunty which is part of gnome-control-center15:29
seb128superm1: ok, I figured that after pinged, that was confusing to have one gnome-settings-daemon and one gnome-control-center task there15:30
cjwatsonEagleScreen: setupcon's already run at boot, actually15:30
cjwatsonEagleScreen: so yet another thing is going wrong. sigh15:30
cjwatsonEagleScreen: I'm not sure what you mean by "it fixes the problem", then, since you go on to say that it doesn't fix the problem15:31
cjwatsonEagleScreen: and yet we have already confirmed separately that it does fix a very similar problem for other users15:32
superm1seb128, yeah those other tasks might want to be adjusted as it was found in intrepid initially15:32
EagleScreenwhen I boot Kubuntu 8.10, tty console cannot change ñ, vocals with accent and other charactes such as €15:32
looldoko:   * Use dpkg-architecture -f instead of -a for cross builds.15:33
cjwatsonupgrading to the console-setup in intrepid-updates, and if necessary running update-initramfs -u, should arrange for the console to be set up before usplash starts15:33
cjwatsonEagleScreen: are you using any other unusual customisations, such as splashy?15:33
looldoko: Are you sure you want to drop -a?  How is the architecture going to be set?15:33
EagleScreeni am not using splashy15:34
EagleScreenafter I run sudo setupcon tty result fixed, all that characters can be typed and showed15:34
cjwatsonin any case, that bug is only barely comprehensible since several people have added essentially unrelated issues to it15:34
looldoko: The problem was that in the old code "DEB_HOST_GNU_TYPE=i486-linux-gnu dpkg-architecture -aarmel -qDEB_HOST_GNU_TYPE" would return i486-linux-gnu15:34
cjwatson(lesson for the future: don't do that)15:34
looldoko: If you add -f and ignore the env, "DEB_HOST_GNU_TYPE=i486-linux-gnu dpkg-architecture -aarmel -qDEB_HOST_GNU_TYPE -f" returns arm-linux-gnueabi15:35
lool(which is the fix I proposed)15:35
cjwatsonEagleScreen: I could do with a copy of your initramfs to investigate15:35
dokolool: please feel free to fix it. I think I misunderstood you.15:35
loolIf you remove -f and -a, then it becomes "DEB_HOST_GNU_TYPE=i486-linux-gnu dpkg-architecture -qDEB_HOST_GNU_TYPE -f" => i486-linux-gnu, where -f is useless and you're not cross-architecturing15:35
EagleScreenyes I will give you as you want15:36
looldoko: Sure will do15:36
freeflyingFenario: pong15:36
* lool sighs at pushing binutils15:36
EagleScreencjwatson I have discovered one new thing. I log into tty console, I run sudo setupcon and characters are fixed, but if I log out and I log in again, characters are broken again.15:39
looldoko: Do you keep binutils in a VCS?  thanks for the other fixes BTW!15:45
looldoko: pushing15:45
dokolool: no. I should do that ... started a repo locally, but it's out of date15:45
loolOk, just wanted to make sure the Debian tree will get the fix as well15:46
pittithekorn: seems bug.subscribers.add() now started giving "Wrong XPath-Expr while parsing Subscribers.__xml.edge.stable" on all bugs?15:49
pittithekorn: do you want a bug report for that, or already know it?15:49
cjwatsonpitti: I filed a bug15:49
cjwatsonbug 32762015:49
ubottuLaunchpad bug 327620 in python-launchpad-bugs "fails to parse subscribers on edge" [Undecided,New] https://launchpad.net/bugs/32762015:49
pittiah, thanks15:50
thekornpitti, cjwatson, oh, will try to fix it today, thanks for reporting this15:52
cjwatsonI also started writing a launchpadlib version of the same program15:52
* pitti was just going to propose that, too15:52
thekornyes, using launchpadlib is a good idea, because the more javascript snippets will be added to launchpad the more likely py-lp-bugs will fail to parse the pages16:02
cjwatsonindeed16:02
keesbryce, Keybuk: hrm, I can't reproduce the usplash glitch. is it intel only?16:06
Keybukkees: I've not reproduced it either16:07
keesbryce: if you revert my usplash change and rebuild usplash, does it still hang?16:08
tseliotseb128: some patches: http://albertomilone.com/ubuntu/gnome/jaunty/sebfiles.txt16:08
* kees will be back after breakfast and exercise...16:08
tseliotseb128: unfortunately I couldn't make g-c-c build because (as you will see) other patches failed16:09
seb128tseliot: did you work on the gnome-desktop update too (ie packaging changes for the soname update)? or just on the patches update?16:10
seb128tseliot: you can probably comment the patches which don't apply if you want to test locally16:11
tseliotseb128: you will find the patches for gnome-desktop there. It builds16:11
seb128tseliot: I will get mvo to update his proxy changes if those don't apply to the new version16:11
tseliotseb128: ok16:11
seb128tseliot: ok, are you interested to do the packaging changes for the gnome-desktop update too or should I pick you patch update and do that now? I'm fine doing it, I just want to get that uploaded to unblock other things ;-)16:12
tseliotseb128: sure, I can do it myself and ask you to merge from my branch16:13
brycekees: if I revert your change and rebuild usplash, it works fine16:14
seb128tseliot: you want to do it or prefer to work on other thing? I'm fine either way, the annoying part was the patch update ;-)16:14
brycekees, good morning16:14
tseliotseb128: I doubt I'll do anything else today, therefore it's not a problem at all16:15
seb128tseliot: ok, so feel free to do it and ping me when it's ready I will sponsor the upload16:15
tseliotseb128: ok16:16
brycekees: I've also tried rebuilding debs of your .28 locally and installed and booted them16:19
brycekees: which then reproduces the black screen issue on boot.16:19
brycebrb16:19
LaserJockmvo: edubuntu ping16:22
mvoLaserJock: oh, right16:24
LaserJockkees: what does the "needs triage" bit on the CVE tracker mean exactly?16:31
apwsuperm1, this bug #319725 ... got a reference to the bzr branch anywhere16:32
ubottuLaunchpad bug 319725 in dell "[Studio XPS 13, Inspiron 531, Studio 16] gnome-settings-daemon crash" [Undecided,Confirmed] https://launchpad.net/bugs/31972516:32
verwilstinfo database3516:37
verwilstoops :D16:37
EagleScreenhow can I apply a debdiff patch?16:46
LaserJockpatch -p1 < <debdiff> I think works16:47
LaserJockit might be -p0 though, I can never remember16:48
EagleScreeni am trying that16:48
LaserJockEagleScreen: so what's it having an issue with then?16:48
EagleScreenyes, just patch is not being applied16:50
LaserJockEagleScreen: do you have the right version of the source package you're trying to apply it to16:51
EagleScreenI think yes16:51
LaserJockEagleScreen: what kind of errors is it giving? is it unable to find the files or is it missing hunks?16:52
EagleScreenany output error16:52
EagleScreeni am in the decompressed folder of the package16:53
LaserJockoh16:53
LaserJockdo it one level up16:53
EagleScreeni was running this: patch -p1 < ../qtparted_0.4.5-4ubuntu2_to_0.4.5-4ubuntu2.1.debdiff16:54
LaserJockso cd ..16:55
EagleScreenis it always necessary doing it one level up? i also tried -p016:55
LaserJockyes16:55
LaserJockwell, I guess it wouldn't *have* to be one dir up16:56
LaserJockbut you might need -p2 or further16:56
EagleScreennow i am one level up16:57
=== cjwatson_ is now known as cjwatson
EagleScreeni have run patch -p1 < qtparted_0.4.5-4ubuntu2_to_0.4.5-4ubuntu2.1.debdiff16:57
EagleScreenis it ok?16:57
LaserJocksure16:57
LaserJockjust play around with the -p until it works ;-)16:57
EagleScreenbut i am reading the sources and they dont seem to be changed16:58
EagleScreeni will have to play..16:58
LaserJockyou will know when it worked16:58
EagleScreeni have tested from p0 to p417:00
LaserJockand it still gives you errors?17:00
EagleScreenit doesn't give me any error, just does not change nothing in the sources17:05
=== Fenario is now known as Fenario-afk
LaserJockif it doesn't give you any errors then it should have applied17:07
LaserJockEagleScreen: so perhaps the changes aren't where you think they are?17:07
LaserJockwhen you apply the patch it should tell you which files it modified17:08
EagleScreenit tell me nothing17:09
LaserJockEagleScreen: you're sure you're running it on 0.4.5-4ubuntu2 and not 0.4.5-4ubuntu2.1?17:10
EagleScreenyes, sure, i tell you that the sources are not changed17:11
EagleScreencan I make a diff patch against a .dsc file in place of a debdiff patch?17:11
EagleScreenthe decompressed folder is in ~/devel/qtparted-0.4.517:12
EagleScreenand the patch is in ~/devel/qtparted_0.4.5-4ubuntu2_to_0.4.5-4ubuntu2.1.debdiff17:13
LaserJockyou can make a debdiff by doing: debdiff <first .dsc file> <second .dsc file17:13
EagleScreenyes that is the way I made the debdiff17:14
LaserJockok, but running patch doesn't give you anything my guess is that you got the wrong version17:14
EagleScreenlets see..17:14
LaserJockor perhaps you didn't actually make any changes in the ubuntu2.1 source package17:15
EagleScreenqtparted has seven patches yet, in debian/patches17:15
EagleScreenthey are in dpatch format17:15
EagleScreeni have added one more, using dpatch-edit-patch17:15
EagleScreenand changing with ti the .dektop file17:16
LaserJockok, and if you look at the debdiff that shows up?17:16
EagleScreenyes it is, wait a moment..17:17
EagleScreenoh no! the patch file is empty!17:18
EagleScreenI dont undestand why17:18
EagleScreena debdiff file is just a plain text file isn't it?17:20
LaserJockyep17:21
EagleScreenok now I have the right patch17:22
EagleScreennow it is well applied with: $ patch -p1 < ../qtparted_0.4.5-4ubuntu2_to_0.4.5-4ubuntu2.1.debdiff17:24
LaserJockEagleScreen: great17:24
EagleScreenthanks17:25
keesbryce: well, crap.  I did try to split up my changes into logical commits to bzr.  I'll try to reproduce on my intel hw, and if I still don't see it, I'll build some versions of usplash for you with progressively more commits in it.17:40
keesLaserJock: it means that the given release of a package hasn't been checked for the vulnerability.17:40
LaserJockkees: and who generally checks? can anybody do that?17:42
keesLaserJock: absolutely anyone can check.  the whole repository is in public bzr.  There's even an extensive README on how it all works.  https://launchpad.net/ubuntu-cve-tracker17:43
LaserJockkees: awesome, thanks. I was looking at moodle :/17:44
keesLaserJock: yeah, moodle is a mess.17:44
LaserJockkees: I think CVE-2008-5619 should be resolved in jaunty when I merge17:44
* kees nods17:44
LaserJockkees: but I'll look at the previous releases to see if it's vulnerable17:45
keesit's the back-porting and testing that's going to be a pain.17:45
* kees nods17:45
LaserJockkees: luckily Debian has fixed a *ton* of moodle bugs and security issues17:46
=== asac_ is now known as asac
LaserJockkees: I filed a MIR on smarty as Debian has removed the moodle copy and replaced it with a dep17:47
LaserJockthey did the same for yui but I don't see it going into main for Jaunty as it requires javascript-common and wwwconfig-common17:47
LaserJockfor Jaunty+1 maybe we can work with the new Debian maintainers to get rid of more of the embedded libs17:48
brycekees: mdz mentioned you also have seen the crash for bug 324368 -- do you have steps to reproduce it?  (just checking for the null ptr doesn't seem to be a sufficient fix)17:50
ubottuLaunchpad bug 324368 in xorg-server "Xorg crashed with SIGSEGV in XisbRead()" [Unknown,Confirmed] https://launchpad.net/bugs/32436817:50
keesLaserJock: excellent17:51
keesbryce: I haven't been able to reproduce it yet.  it only happened once.17:51
keesbryce: I suspect it was related to me yanking out a projector before/during/after a resume.17:52
brycekees: ah17:52
keesbryce: but, I'm not really sure what the sequence was.  :(17:52
superm1apw, it's on the bug18:12
=== thekorn_ is now known as tthkorn
=== tthkorn is now known as thekorn
=== surfaz is now known as surfaz[24h]
=== surfaz[24h] is now known as surfaz[24
=== surfaz[24 is now known as surfaz
superm1apw, https://code.edge.launchpad.net/~superm1/gnome-control-center/vendor-fallback/+merge/350818:18
apwsuperm1, thanks. being dense clearly18:18
superm1apw, no, i agree that it's quite easy to overlook the bzr link on bugs.  i've done it myself too :)18:18
apwso basically its, "yeah ok, but i have some conflicting changes already in the pipe, lets redo it on top"18:19
apwso i don't need to keep this laptop with the bug, it can come back to you18:20
superm1apw, if you see anything else on it that you'd like to address in using it you can hang onto it for a little longer, otherwise sure send it back18:21
keesbryce: hrm, no luck reproducing usplash weirdness18:22
hwildeanybody have a good tool to view cpu load per thread for multithreaded apps ?18:49
ogracjwatson, still around ?18:52
cjwatsonogra: yes18:53
ogracjwatson, i'm trying to find out why our nslug image doesnt work ...18:53
* ogra does a c&p from -arm18:53
ogra<ogra> til/pad $(TEMP)/initrd.gz.nslu2 6291440 # size of partition - 16 for header .... thats debian ...18:53
ogra<ogra> util/pad $(TEMP)/initrd.gz.nslu2 5636080 # size of partition - 21 for header .... thats ours18:53
ogracjwatson, where does that 21 come from ?18:54
ograthe partition changes seem all ok, but i dont understand why our header is 21 bytes instead of 1618:54
cjwatsonogra: bzr up18:56
ogra(thats from build/config/armel/ixp4xx/netboot.cfg btw)18:56
mnabilguys , i'm creating custom ubuntu live cd , how can i add a script to be run in the startup ?18:56
cjwatsonogra: lool pointed that out earlier on #ubuntu-installer; I had understood the 16 to be blocks rather than bytes and so miscorrected it. It's fixed in bzr18:56
cjwatsonmnabil: where in the startup sequence?18:57
ion_Aah, S:Startup-Sequence18:57
ogracjwatson, ah, k, well, i'm not sure yet its the fix we need, i just wanted to know where the 21 comes from :)18:57
ograi think the headers are hadcoded in slugimage so the size shouldnt vary18:57
* ogra goes and rolls another testimage18:58
cjwatsonogra: I set it back to 16, it was just my mistake19:01
ograah19:01
ograwell, lets see :)19:01
ograthat whole setup is weird and scary19:01
ograas it comes from debian19:02
* ogra wishes LP would actually work :/19:04
mnabilcjwatson, sorry for late, i mean startup of the shell19:10
mnabilcjwatson, like clonezilla if you know it19:10
cjwatson"startup of the shell"?19:11
cjwatsonyou mean a rescue shell?19:12
cjwatsonyou need to be very very clear on exactly where you want to put it in the startup sequence19:12
* ogra curses ... damned i just deleted my kernel image and inbetween a new d-i built19:15
mnabilcjwatson, the live cd is without autologin , i need it to login to for example 'ubuntu' and the run the script19:21
cjwatsonmnabil: so you want to put it into the GNOME session?19:22
cjwatsonmnabil: the live CD that *we* ship does autologin; if yours doesn't, then you must have broken something19:22
mnabilcjwatson, i dun have any GUI installed in the live cd , it gives only a console login19:22
cjwatsonmnabil: we set up autologin on the console too19:23
mnabilcjwatson, cool, it has already autologin , but i  just wanna script after autologin19:23
mnabil*wanna run19:23
cjwatson"want to"19:23
cjwatsonmnabil: perhaps you should create an init script with a symlink to it somewhere in /etc/rc2.d/ that runs whatever you want to run19:24
mnabilcjwatson, k, "wanna run " :)19:24
cjwatsonmnabil: you don't have to log in for that; init scripts run as root, and if you want to you can drop privileges19:24
allquixoticAnyone know if UXA will be enabled by default for Intel cards in Jaunty GM? The 2D performance difference is night and day between EXA and UXA with the Xorg/Mesa/DRI stack used in Jaunty.19:24
cjwatsonallquixotic: Bryce has been investigating it, but at the moment it's very unreliable on all but a few cards19:25
mnabilcjwatson, thanks alot :)19:25
cjwatsonallquixotic: https://wiki.ubuntu.com/X/UxaTesting19:25
=== beuno_ is now known as beuno
allquixoticcjwatson: Cool. I haven't had a single graphics system related crash and I've been running it for days on a GM965. If it can't be stabilized on all Intel chips, I would want to advocate either a whitelist, a blacklist, or at _least_ a Release Note documenting how to enable it for people who've got the right card(s).19:26
bryceallquixotic: at this stage it's simply too unstable.  I've emailed keithp and jesse for advice on either improving performance on EXA or improving stability on UXA, but no reply so far.19:26
bryceallquixotic: look at the url cjwatson posted; there isn't a strong enough correlation to stability and chipset to warrant black/white listing.19:27
bryceallquixotic: I'm not comfortable listing it in release notes at the current level of (in)stability19:28
bryceallquixotic: if you would like to help bring UXA up to a point where we can consider it more strongly, I would love having your help in upstreaming the UXA bugs filed against xserver-xorg-video-intel19:29
allquixoticbryce: Interesting reports in the wiki. The only complaints on any 965 (Crestline) based hardware are that it crashes after resume (and I can't reproduce that), and that it has font issues19:29
brycethat is currently the gating issue19:29
allquixoticbut the font issues is something like: you minimize Firefox, and for a split-second you see partially rendered window contents as it's coming up19:29
allquixoticthat's minor, I wouldn't even call that a defect, really19:29
bryceallquixotic: I've seen freezes on 965 as well19:29
allquixoticHave you? Under what situations?19:29
allquixoticI've been running it fully loaded on a ThinkPad X61T, uptime 3 days, suspend/resume every few hours, OpenGL 2.1 games, tons of Firefox tabs,...19:30
allquixoticonly crash I had (3 days ago) was Cisco VPN related, not graphics19:30
bryceallquixotic: also there are only *4* test cases listed there for 965; hardly what I'd call a definitive sampling.  I'd like to see more 965 cases first.19:31
allquixoticbryce: I will add an entry to the wiki with my findings (very very positive performance-wise, and no stability issues whatsoever) and I might try to reproduce others' problems for the sake of either resolving the bugs if they're valid, or figuring out a different root cause (user could be mistaken about what's causing their woes)19:31
bryceallquixotic: of the 4 cases, 1 reports freezing, 2 report crashes.  I think you're crazy concluding that there are hardly any stability problems there!19:32
bryce;-)19:32
allquixoticI'm just worried that user testing and reporting problems is a bit slippery because some of their claims of graphics-related issues could be related to other subsystems. My intent would be to get more info from the reporters and try to determine _whether_ their concerns are indeed graphics related.19:33
cjwatsonallquixotic: well, on this 965 system (exact same PCI ID as others that claim to work to a greater or lesser extent), I get a startup sound but a black screen on boot; the system is fine with whatever the default acceleration method is, AccelMethod is precisely the only change19:38
cjwatsonso I can't say I'm terribly impressed so far19:38
allquixoticcjwatson: Is it a desktop, or a laptop?19:38
cjwatsonlaptop19:38
allquixoticWhat architecture and how much RAM?19:38
hwildeso anybody have a good tool to view cpu load per thread for multithreaded apps ?19:39
cjwatsonallquixotic: FWIW, the testing on that page is mostly from developers (albeit not X developers), so they should generally be well-practised at distinguishing issues19:39
cjwatsonallquixotic: i386, 1GB19:39
allquixoticcjwatson: So you're using the -generic flavored kernel and not server?19:39
cjwatsonallquixotic: yes19:39
allquixoticOk. I was just checking -- currently the DRI2/UXA stuff is very broken with PAE19:40
directhexhwilde, htop i think19:40
directhexwait, per THREAD? no idea19:40
hwildeyaeh exactly :/19:40
allquixoticSo even if we did have a whitelist, it would have to be for either i386/4GB, or x86_6419:40
hwildedirecthex, there has to be some way to figure out which thread is cpuing tho ...  i can't be the only one to ever need to debug this19:41
allquixoticcjwatson: I'm on a GM965 laptop myself, but I'm using x86_64... Much of the code involved _is_ architecture dependent, so maybe that is part of your issue19:41
cjwatsonI'm sure it may be, but I'm on a very common configuration here so I think that is relevant input19:41
cjwatsoncode that only works on amd64 is slightly more use than a chocolate teapot, but not really enough to get enthusiastic about :-)19:42
directhexwho uses fringe arches like m68k and i386? o_o19:42
keescjwatson, Keybuk: it seems this patch broke usplash for some people: http://people.ubuntu.com/~kees/usplash-testing/sig.patch19:42
keescjwatson, Keybuk: any idea why?19:43
allquixoticcjwatson: Of the entries for PCI ID 8086:2a02 (GM965 Crestline), there is one mixed (bryce), two negative, and two positive. I think I'd like to start with reaching seb128 to debug why it crashed for him on resume, as that's definitely not the case here19:43
keesdrawing is external to the alarm handler now, so it didn't look like those were needed any more19:43
cjwatsonallquixotic: count me as negative for the same ID19:44
allquixoticseb128 and portis25 didn't file launchpad bugs associated with their negative reports...19:45
allquixoticor they didn't link them19:45
cjwatsonkees: I'm not sure, but what's the cost of just reverting it?19:46
bryceallquixotic: thanks for your look at investigating these problems.  Getting seb128's issue captured in a bug report and forwarded upstream would be a good step19:46
cjwatsonI'll file one later, but had better upgrade first19:47
keescjwatson: none, it's already going into the archive.19:47
bryce(cjwatson: your blank screen issue might be the usplash issue kees is presently uploading a fix for)19:47
keescjwatson: I just wanted to see if there was some general knowledge in this area I was missing.19:47
cjwatsonbryce: could be, but it doesn't happen with EXA19:48
cjwatsonand usplash itself displays fine19:48
allquixoticbryce: I was a GM945 laptop owner for 2 years, and almost a full year of GM965 torture... I regularly grab git master from upstream and test things out when Ubuntu isn't on the forefront; I was testing GEM and nagging upstream on crashes when we were still using the grand old aperture rendering mode19:48
allquixoticSo this is very familiar territory to me19:48
brycecjwatson: yeah usplash was displaying fine for me, but I could confirm that removing it from the kernel boot line made the issue go away19:49
cjwatsonI see, OK19:49
brycecjwatson: OTOH pitti is seeing a similar blank screen issue for which usplash has been ruled out19:49
cjwatsonlook, EXA's performance is certainly dreadful at the moment; I just think we should be ironing out a few more problems and *then* talking about making it the default19:49
bryceallquixotic: excellent, thanks for your help!19:49
cjwatsonjust seems like we're putting the cart before the horse a little bit19:49
bryceallquixotic: fwiw, I too have been very impressed at the performance improvement for UXA, but as X maintainer would like to see the overall stability significantly improved before I'm really comfortable supporting it (even for limited numbers of chips)19:50
allquixoticmy experience is that Zhenyu Wang at Intel is one of the guys assigned to hack on stable, whereas the others are variously working on master, one of the in-development feature branches, or occasionally, stable19:50
allquixoticso maybe we could also bug him for help19:50
bryceI am also uncertain I want to support EXA on some chips, and UXA in some others, since that makes twice as much work to manage :-)  (and we already have plenty of bugs against -intel as it is)19:51
allquixoticgoing on sheer frequency and content of commits, Zhenyu puts a lot of work into the stable branches of xf86-video-intel19:51
bryceyep19:51
allquixoticoh, another relevant data point we need to collect about _any_ -intel problems19:51
allquixoticis a compositing window manager enabled or no?19:52
bryceI really wish they had more engineers supporting the stable release.  they seem to pump out releases with what seems like limited amounts of testing (esp. against 8xx chips)19:52
allquixoticsome problems manifest only with, or only without compositing... helps narrow the hunt for upstream, if nothing else19:52
cjwatson(no, in my case, but not really relevant since the black-screen is at gdm)19:52
brycehmm19:52
allquixoticI think Intel is trying to unofficially deprecate the 8xx chips. I mean, they're old, and using all this transparency and compositing "with" those cards basically throws a large amount of work at the CPU instead... and the associated CPU with an 8xx chip is not going to be stellar either19:53
allquixoticthey support them in spirit, but in practice, their work is gonna go at the latest cards19:53
allquixoticNvidia does the same19:53
brycethat's fine, but it doesn't help us19:53
brycea huge chunk of our bugs in -intel launchpad are 8xx stuff19:54
allquixotichas there been consideration of dropping "official support" for 8xx according to Ubuntu's hardware compatibility list?19:54
bryceallquixotic: but you're right at Intel's focus; it seems almost not worthwhile to bother forwarding the 8xx bugs.19:55
allquixoticif not now, definitely in the future that will be something to consider19:55
bryceallquixotic: I think many people would be upset by that19:55
allquixoticbut unless we want to have 8xx cards load xf86-video-vesa and use DRI's swrast....19:55
bryceallquixotic: Ubuntu targets educational use cases which have old hardware, as well as server use cases where on-board graphics is not unusual to be 8xx based19:56
allquixoticif upstream won't fix it, and Canonical doesn't have Intel hardware gurus...19:56
allquixoticwhat's to be done?19:56
bryceyeah I know19:56
brycewe need community people to step up to the plate, as happens with -ati, -nv, -nouveau, -radeonhd, etc.19:56
allquixotic-vesa and swrast will always be an "option" to get them a display, but losing 3d rendering because upstream is offering features that are too new for old hardware to support -- where the hardware could do basic 3d just fine in previous releases - is a serious regression19:57
bryce-fglrx drops support for old chips, but -ati still supports them going all the way back19:57
allquixoticand I've always been an advocate of software NOT standing in the way of functional hardware for any reason19:57
brycetrue, although a number of the 8xx bugs are even more basic than 3d... like just booting X19:58
bryceallquixotic: I told Intel (well, jesse) that as a minimum if they do proceed with dropping support for more 8xx chips, that they need to first release docs for the chips, so the community has all they need to do support19:59
allquixoticwell, for now, the best I can do is bring bugs to the attention of upstream, and try to provide focused, verified bug reports... unless the bug is very basic and easy to spot in code... I'm a systems programmer, but I haven't done hardware interface hacking before, either in userspace or kernel19:59
brycedropping official support without releasing register documentation ----> FAIL19:59
allquixoticand I'm sorry to say I can't help at all with the 8xx stuff because I don't own an 8xx20:00
* bryce nods20:00
bryceyeah same here, just ranting...20:00
allquixoticthey haven't released register docs on 8xx?!20:00
allquixoticwow.20:00
allquixotichave they done it for the 915+ chips?20:01
allquixoticbryce: If upstream were to make a new release, when would be the cutoff for pulling it into Jaunty?20:07
allquixoticWould be nice to see if Intel pushes 2.6.2 or so to help with these issues20:07
bryceI would be willing to pull a 2.6.2 even up to beta20:07
brycealthough alpha-6 would probably be the latest I'd be willing to consider defaulting on UXA20:08
brycebut even that is pushing it pretty late to get adequate testing20:09
allquixoticbryce: Can we do something similar to what Fedora does with "preview" features, if we can't enable by default? They include it, and mention it, but disavow support etc for those who enable it...20:10
bryceI guess, what specifically do you have in mind?20:11
bryceallquixotic: what I want to avoid is that it seems Intel frequently puts out a new tech that is advertised as solving a whole mess of issues, but has lots and lots of regressions, and then they stop giving support for the older tech20:12
bryceso we get left between the choice of two buggy options, and -intel users find themselves hating the world20:12
allquixoticbryce: IIRC, Fedora basically discussed Kernel Mode Setting (a different feature, but the same process applies) in Fedora 9 - for ATI - and they told people how to enable it, but turned it off by default20:13
bryceoften we move to the newer tech with the hope that soon upstream will fix all the remaining issues soon enough, but often that doesn't quite happen20:13
allquixoticbryce: OTOH, I really like the Intel performance on 8.10 :) The -intel desktop experience isn't bad on my mom's GM945 with metacity compositing20:14
bryceindeed we're still waiting on some issues from the XAA -> EXA issue, and already upstream is moving EXA -> UXA ;-)20:14
allquixoticI think whatever you went with for 8.10's stack was a win in terms of performance20:14
allquixoticfeatures, maybe not, but it's silken smooth for Firefox surfing20:14
=== thunderstruck is now known as gnomefreak
* ScottK tosses in a grumble about compiz hacks that break other WM.20:15
allquixoticI see your point about Intel's ever-evolving stream of unstable innovations, and at some point the innovation itself needs to turn toward stability and performance20:15
allquixoticI have a gut feeling that the GEM/DRI2/KMS plateau will be a point of significant stabilization and performance20:15
allquixoticbut if I were an Intel developer and I have a schedule to (for example) get KMS "ready" by Q1 2009, I would be focusing on dealing with issues related to having the entire feature set enabled20:16
allquixoticwhich means that 9.04's feature set becomes the ugly duckling that lacks KMS, and half the Intel guys haven't touched that path for weeks20:17
brycehere's one UXA bug - 32235620:17
ogracjwatson, are there chances that the nslu2 d-i initrd.gz could grow over 4M (its 3.3 currently) i think i found our issue in debian bug 45188220:18
ubottuDebian bug 451882 in apex-nslu2 "Increase CONFIG_RAMDISK_SIZE" [Normal,Closed] http://bugs.debian.org/45188220:18
ograseems they raised the ramdisk size to 6.2M ... that cuts down the available kernel space to less than 2M20:18
allquixoticbryce: CONFIG_HIGHMEM64G implies PAE. Intel has been "loudly" proclaiming that users should not try to use UXA with that configuration20:19
allquixoticSo that bug is a "known; being worked high priority" as far as I am aware. Could be ready for 2.6.2, who knows20:19
bryceallquixotic: ok, can you update the bug to that effect?  If you can include a url to the official statement from them on that, it would help.20:19
allquixoticit was on the ML, let me dig20:19
bryceor a link to an upstream bug report would be nice20:19
allquixoticbryce: Updated20:24
allquixotichttps://bugs.launchpad.net/xserver-xorg-video-intel/+bug/32235620:24
ubottuUbuntu bug 322356 in xserver-xorg-video-intel "[i965] xorg on intel freezes on startup when using a kernel with CONFIG_HIGHMEM64G and AccelMethod is set to UXA " [Undecided,Confirmed]20:24
bryceallquixotic: thanks20:24
ryuhi20:42
LaserJockslangasek: you around?21:05
slangasekLaserJock: hi21:05
cjwatsonogra: hard to say for sure, but I'm sure you could take it back down a bit21:07
cjwatsonhmm, now I get the black screen with EXA too. blast. I'll try with new usplash tomorrow21:08
ebroderDoes anyone know if I can find the git repo for Ubuntu's xserver-xorg-video-ati changes? (I'm trying to track down LP bug #289026)21:10
ubottuError: Could not parse data returned by Launchpad: timed out (https://launchpad.net/bugs/289026/+text)21:10
ebroder(X fails to start on Radeon HD 2400 Mobility (Ubuntu 8.10 RC)) since ubottu didn't find it)21:11
maxbHmm, I just had to do a "Partial upgrade" rather than a normal update-manager run - shouldn't libgpod4 declare "Replaces: libgpod4-nogtk" ?21:17
bryceebroder: there is no git repo for -ati21:19
bryceebroder: use upstream's git repo for -ati21:19
bryceebroder: or look in the xserver git repo (directions for X git usage at http://wiki.ubuntu.com/X/)21:20
bryceheya Rocket2DMn21:20
ebroderbryce: Ok. What are your thoughts on trying to track down this particular bug for an SRU? Should we work on the backport instead?21:20
Rocket2DMnhey bryce21:21
bryceebroder: a backport is more likely to go through21:25
bryceebroder: however if you can identify a sufficiently minimal patch that can be shown to have no regression risk, then maybe an sru would be doable21:25
ebroderbryce: Yeah....that, uh, sounds kind of hard. I think I'll probably work on the backport21:26
brycesounds goo21:27
bryce+d21:27
=== Riddelll is now known as Riddell
=== bluesmoke is now known as Amaranth
=== Igorots is now known as Igorot
=== thunders1ruck is now known as gnomefreak
cjwatsonjelmer: I'm trying to GPG-verify your subvertpy sync, but the key used to sign it (060F66E5) doesn't seem to be on the keyservers22:38
cjwatsonjelmer: could you please push it somewhere?22:38
jelmercjwatson, it's a subkey that's on my main key (1EEF5276)22:39
cjwatsonah. funny that subkeys.pgp.net didn't return it22:39
cjwatsonoh, drat, something weird with the firewall22:40
cjwatsonok, got it now22:41
* ogra gives up in desparation ... 22:53
ogra:(22:54
MoeHello ..22:55
MoeI'm wondering if pitti is around22:55
Moealright, doesn't seem to be the case22:56
Moegood night22:56
directhexMoe, pitti occasionally lets his feeble human side show, and succumbs to his biological need to sleep. the plan is to patch that out in the next beta23:01
cjwatsonOTOH, directhex sometimes forgets to read part messages ;-)23:05
directhexcjwatson, i saw he parted, but decided my reply was too damn good to go unbroadcasted23:06
CaesarShould I discuss Hardy backport requests here, or in another channel?23:44
maxbCaesar: Depends whether it's main or universe I guess.23:52
* Caesar checks23:53
CaesarAll three are in universe23:54
maxb#ubuntu-motu then23:55
Caesarrighto23:55
Caesarthanks23:55
maxb(I think)23:55

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!