/srv/irclogs.ubuntu.com/2008/06/25/#ubuntu-devel.txt

=== asac_ is now known as asac
zulim back as well00:10
zulkees: ill upload it and do the testcase if you want00:11
zulslangasek: sorry I wasnt available I was getting some dental work done and was at the dentist00:15
zulslangasek: um dental work done and family commitments00:15
keeszul: that'd be great, thanks.00:16
emgentHi ember01:36
emberhey emgent, sup01:36
slangasekzul: ah, so kees volunteered you sight-unseen, ok then... :)01:51
zulslangasek: im trying to test the debdiff now after I get this dapper vm setup01:52
Rudd-Oguys01:54
keesslangasek: well, I'd volunteered zul and mathiaz since they've had the most apache-touching recently and I was already swamped with equally time-critical things.  :)02:00
[Relic]how long does it take between a report and the time someone actually looks at fixing something?02:08
StevenK[Relic]: It depends, usually. What's the bug number, I'll have a quick look.02:09
[Relic]basically it is snatching a c file from a newer kernel module and inserting to bring ubuntu 45nm core temp support  ->  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/23511902:10
ubottuLaunchpad bug 235119 in linux "Coretemp outdated / can't show 45nm core temps" [Undecided,New]02:10
StevenKAhhhh.02:10
[Relic]I run blender which is CPU rendering so I really want to know my core temp.  I know multiple people have verified it can work if lm-sensors 3.0.2 sensors detect and the new coretemp.c with the model x17s are brought in02:12
[Relic]I need a bigger back buffer when they do that  :(02:43
Rudd-Ocan I float this idea guys? http://software-libre.rudd-o.com/Streams_vs._documents02:44
ScottKSeems a bit OT here.  More of an upstream thing.02:46
* davidm is away: 02:52
pwnguinRudd-O: ever heard of plan9?02:53
RAOFRudd-O: Is that in response to bryce's blog post?03:21
calcheh i got a bug report about openoffice from the head of osnews03:29
calcthe name sounded familar so i googled it and found out it was her03:30
StevenKcalc: In Launchpad?03:30
calcStevenK: yea03:31
StevenKcalc: Bug number? :-)03:32
pwnguinEugenia?03:32
calc24255703:32
calcyea03:32
pwnguinbug #24255703:33
ubottuLaunchpad bug 242557 in openoffice.org "I can't uninstall openoffice without destroying my system" [Undecided,Invalid] https://launchpad.net/bugs/24255703:33
calcprobably should just find the original bug where it is filed and merge it rather than invalid03:33
pwnguincalc: im not sure if it counts as invasion of privacy, but I found knuth's LP account03:38
persiaPolling it for activity is maybe an invasion of pricacy, but LP accounts have become part of our public faces.03:42
lamontso... lets say that I have a raid 6 device that I want to do an install on, and an up-and-running hardy box to plug it into...  is there a wubi-like thing, or do I get to reboot the machine and do the install from there?03:43
emgentmorning people03:47
persialamont: debootstrap?03:51
lamontwell, yeah.03:51
lamontI want all the rest of it to turn it into a hardy desktop machine03:51
lamontpreferrably without doing all those steps manually03:51
lamont(because that sucks)03:51
lamont(all 6  or 7 times I've done it before...)03:51
persiaOK.  debootstrap target; chroot target /bin/bash; apt-get install ubuntu-desktop03:52
lamontthat's about 16 steps short of clueful03:52
persiaWell, yes.  It could use a pretty GUI python wrapper, and misses a few bits.03:52
persiaHow about booting the ISO in a VM attached to the device?03:53
lamont"few".  heh03:54
persialamont: What?  Do you really want such niceties as a locale, or host definitions?03:56
lamontdefault first user, partitioner, etc03:59
persiaRight.  `kvm -hdc /dev/sdq ubuntu-hardy.iso`04:02
RAOFOr virt-manager.  I've found that nice.04:03
persiaErr `kvm -hdc /dev/sdq -cdrom ubuntu-hardy.iso`04:03
persiaRAOF: For installing Ubuntu Desktop on a bare RAID device?04:03
RAOFStart the interface as root and I'm pretty sure you can use a raw device as the target.04:04
RAOFkvm also works, of course, and may be more obvious given a browse of the man page ;)04:05
* pwnguin should try out kvm now that ubuntu-mobile is offering an image04:19
lamontdoes the -generic kernel have kvm support, or does that require the kvm kernel?04:51
RAOF-generic has kvm support.  Is there a kvm kernel?  Do you mean -xen, or -openvt, or something?04:51
persia-generic supports kvm as a guest, and runs within kvm04:52
pwnguinhmm04:52
pwnguinDaniel T Chen 2005-08-07 Expired on 2007-08-1604:52
persiaYour hardware must support kvm though.  Otherwise virtualbox and kqemu are alternates (but you have to build your own kqemu modules from source)04:53
=== LucidFox is now known as GamingFox
=== nenolod is now known as happinessturtle
lamonthrm... 3TB ext3 FS on RAID5 takes a while to create... :-(05:54
lifelesswin 2006:03
wgrantIt's such a badly named command.06:03
RAOFNah.  It's awesome.06:07
RAOFlifeless: Can I win 30? :)06:07
lifelessthat would #squeak06:07
* StevenK wonders about Unicode code points for small caps06:08
=== GamingFox is now known as LucidFox
dholbachgood morning06:30
=== happinessturtle is now known as nenolod
dholbachbryce: still there? :)06:30
=== dholbach_ is now known as dholbach
pittiGood morning06:59
StevenKMorning pitti07:00
nxvlgood $TZ_TIME_OF_DAY07:00
pitticjwatson_: chiark> my server moved to a new IP, could that gbe it?07:00
pitticjwatson_: s/gbe/be/07:01
dholbachtjaalton: do you keep X packages in bzr/git/something?07:01
dholbachtjaalton: if not, I'm going to drop our patch on xserver-xorg-input-vmmouse (as the scaling was fixed in the new upstream release too and fixing the scaling twice broke the mouse in kvm for me)07:02
nxvlpitti: oh, btw, i already upload the debdiff for openvpn07:07
pittinxvl: debdiff?07:07
pittiit's a (fake)sync, isn't it? not much of a diff07:07
nxvlBug #24253707:07
ubott2Launchpad bug 242537 in openvpn "Please sync openvpn 2.1~rc7-5 (main) from Debian unstable (main)." [Wishlist,Confirmed] https://launchpad.net/bugs/24253707:07
nxvlpitti: yep, but i don't have any other way to upload my work07:08
nxvlpitti: the diff is the debian changes aplied to our old package07:08
pittinxvl: ah, I see; heh, I could just have done it myself, but thanks07:08
nxvl:D07:08
* pitti uploads07:08
nxvlit was just a bitsize fix07:09
nxvljust one line07:09
pittinxvl: uploaded07:12
nxvl:D07:13
nxvlthanks07:13
dholbachhi seb12808:13
seb128hello dholbach08:13
brycedholbach: yeah08:18
dholbachbryce: did the xserver-xorg-input-vmmouse upload myself - hope that was OK08:19
* pitti hugs dholbach for the vmmouse fix -- the previous version drove me mad in intrepid :)08:19
brycedholbach: sure that's probably fine.  I was just looking at that bug earlier08:19
pittihey seb128, bonjour08:20
seb128guten tag pitti08:20
DarKnesS_WolFi'm trying to build a gdal package with gdal support but i am getting this error in hardy , feisty gutsy it did work fine08:28
DarKnesS_WolFhttp://pastebin.ca/105558708:28
DarKnesS_WolFi'm building using that command dpkg-buildpacka08:29
DarKnesS_WolFge -rfakeroot08:29
DarKnesS_WolFi'm building using that command dpkg-buildpackage -rfakeroot08:29
pittiRiddell: oooh! https://svn.pardus.org.tr/uludag/trunk/PolicyKit-kde/08:35
pittiRiddell: just read a mail on hal@ that it is near completion08:35
=== shadowxp is now known as shadow
* ogra wonders why Keybuk set bug 98955 to fix committed ...08:57
ubott2Launchpad bug 98955 in upstart "logd not running" [Medium,In progress] https://launchpad.net/bugs/9895508:57
berzerkasorry for question not strictly related to ubuntu development, but i think you devs might be the only ones able to answer: how is the CAP_SYS_RAWIO capability handled in ubuntu? i am developing a userspace USB driver and read with ioctl from /dev/bus/usb/*/*. on my gentoo machine, no problem. on ubuntu i get "Operation not permitted" and the only thing i can imagine is that the RAWIO capability is disabled. on the other hand, it doesn't even09:08
berzerkawork using sudo. any ideas?09:08
dholbachberzerka: you could try in #ubuntu-kernel09:09
berzerkadholbach: oh, right. thank you!09:09
dholbachnp :)09:10
=== tkamppeter_ is now known as tkamppeter
=== mdz_ is now known as mdz
dholbachthekorn: bug.activity is GREAT - thanks09:52
seb128dholbach: what is that?09:52
dholbach>>> import launchpadbugs.connector as Connector09:53
dholbach>>> Bug = Connector.ConnectBug()09:53
dholbach>>> bug = Bug(242667)09:53
dholbach>>> print bug.activity09:53
dholbach[<hito 2008-06-24 14:06:00 UTC 'bug'>, <ikuya-fruitsbasket 2008-06-24 14:24:00 UTC 'bug'>, <ikuya-fruitsbasket 2008-06-24 14:55:00 UTC 'bug'>, <arnegoetje 2008-06-25 07:17:00 UTC 'scim-anthy: status'>]09:53
dholbach>>>09:53
seb128dholbach: ah, nice ;-)09:55
thekorndholbach, oh, good to hear it's working and you like it10:02
thekornbut this shows me that I have to update the wiki more often10:02
dholbach:)10:02
=== cjwatson_ is now known as cjwatson
cjwatsonpitti: could be - what's the new IP, and I'll pass it on?10:07
pitticjwatson: 213.9.93.7010:08
pitticjwatson: (host piware.de)10:08
cjwatsonpitti: ah yes, doesn't match slave0.ns.chiark.greenend.org.uk10:08
StevenKHeh, wasn't piware moved like a week ago? :-)10:09
cjwatsoncan take a little while to notice slave NS misconfiguration10:11
cjwatsonthe cron job that whines about it on that system is weekly, I think10:11
StevenKAh.10:12
pittiwhich reminds me, I should set the DNS TTL back to a day (currently an hour)10:16
Keybukogra: because a "fix" has been committed ?10:16
* StevenK checks what his TTL is, since he recently moved his domain too10:17
dholbachArneGoetje: does the anthy patch apply for you? it doesn't for me10:19
ArneGoetjedholbach: against the hardy version?10:21
ArneGoetjedholbach: works for me10:21
ograKeybuk, well, removing the code is not actually what i would call a fix :)10:21
ogra(unless i understood the upstream commit wrong)10:22
dholbachArneGoetje: sorry - my mistake, I'll update it to be "intrepid" instead of "hardy10:22
ArneGoetjedholbach: ?10:22
dholbachArneGoetje: the changelog says 'hardy'10:23
dholbachArneGoetje: ah - we have a newer version in intrepid - that why it does not apply10:24
ArneGoetjedholbach: correct10:25
dholbachthe patch needs a bit of updating then10:25
ArneGoetjedholbach: in that case, I'll test if the bug still applies for intrepid10:25
dholbachwell, we can't upload to hardy any more (or it needs to follow StableReleaseUpdates)10:26
ArneGoetjedholbach: bug fix?10:26
dholbachstill it'd be hardy-proposed instead of hardy and it needs to go into intrepid first anyway10:27
dholbachhttps://wiki.ubuntu.com/StableReleaseUpdates10:27
ograMacSlow, 01_fix_missing_semicolon.patch ? thats sweet :)10:27
ArneGoetjedholbach: my guess is that the issue has been fixed in intrepid already... but I'll check that10:27
MacSlowogra, mvo found that one actually10:28
Keybukogra: it closes the bug10:28
dholbachArneGoetje: gracias10:28
ograKeybuk, it doesnt fix logging, so i'd disagree10:28
Keybukogra: where "Fix Committed" means that the bug will be made invalid10:28
MacSlowogra, I didn't even see this failing initially with all the tons of output pbuilder creates10:28
Keybuksince there's no "Something that will make this bug Invalid Committed" status ;)10:28
ograwell, isnt it to be fixed in upstart in the end ? and isnt the final fix to have a proper boot log ?10:29
Keybukno10:29
MacSlowogra, Keybuk: I informed the debian maintainer and also filed a bug upstream with the patch attached... as it was still not fixed in trunk... odd isn't it... in over four months nobody ran into that10:29
* ogra doesnt get the logic10:29
ograMacSlow, well, i poked on that package quite often in the past and slangasek as well ... seems nobody of us ever spotted it10:30
MacSloware we meant to keep confflags-gnome and confflags-gtk in debian/rules for goffice? debian only uses confflags and does not make a distinction between gtk- and gnome-related flags.10:31
ograMacSlow, xubuntu :)10:31
ograthey dont want gnome libs10:31
MacSlowmvo, sorry for implicitly stealing your credit regarding the semicolon-patch regarding planner!10:32
MacSlowogra, so how should I go about merging that? just put everything in confflags?10:32
ograMacSlow, ask one of the xubuntu people i'd say, they likely have touched that before and created that diff10:33
mvoMacSlow: no worries10:33
seb128you likely want to keep the ubuntu changes the way they are10:33
ogranot sure if there is more involved than confflags10:34
seb128debian doesn't build a gtk variant10:34
ograthere might be additional patches10:34
MacSlowhm... ok... gnumeric is a tougher beast than anticipated... goffice (newer version needed for gnumeric) looks nasty to me merge-wise10:34
mvoogra, MacSlow: it seems to be releated/triggered by the new glib10:35
Keybukogra: I don't really have any solution for logging yet10:35
MacSlowmvo, yes... dependencies of goffice introduced the need for a newer glib10:35
Keybukremoving the claim of the feature is the best fix for now10:36
ograKeybuk, yeah understood, i just didnt get the logic first place10:37
MacSlowseb128, hm... debian enables static libraries for goffice... do we want that too?10:37
* MacSlow assumes not10:37
seb128usually we want what debian do if we don't have strong reason to not take the changes10:38
ograthere might be an entry in the changelog explaining it ;)10:38
Keybukogra: Fix Committed is a silly status really10:39
Keybukat least, according to the LP model10:39
ograyeah10:39
Keybukyou should be able to add bug tasks for a branch10:39
Keybukthen that branch could be marked Invalid/Wont Fix or something10:39
ograwell, cant you just mark it Invalid and make it hishlist for a new app ?10:39
ogra*whishlist10:39
Keybukthen when I make a release on that branch, the bug status should be automatically copied to the task for the upstream package10:39
seb128Keybuk: it's not when you have the packaging in bzr and if launchpad was updated automatically on commit10:39
Keybukseb128: err, ?10:40
Keybukseb128: that doesn't make what I said invalid10:40
seb128<Keybuk> ogra: Fix Committed is a silly status really10:40
seb128that was a reply to that10:40
Keybukseb128: the next line is more important ;)10:40
seb128right, but I was typing then ;-)10:40
Keybukin your use, and my model, committing would set the branch bug task to "Fix Released"10:41
seb128right10:41
Keybukreleasing would set the upstream bug task to "Fix Released"10:41
Keybukpackaging would set the distro bug task to "Fix Released"10:41
seb128hum, not really10:41
KeybukFix Committed is silly because you can do more than commit Fixes :p10:41
seb128fix released is when the update is pushed in the distribution10:41
Keybukright, that's what I mean - couldn't think of a good word :P10:41
MacSlowwhat does the -i option in dh_<command> in debian/rules?10:42
cjwatsonman debhelper10:43
cjwatsonMacSlow: ^-10:43
cjwatsonKeybuk: "fixed" would do it ...10:44
MacSlowcjwatson, ah thanks10:44
Keybukcjwatson: ?10:45
MacSlowseb128, for goffice we still don't want -dbg pakcages?! that's currently stated in a comment in goffice's debian/rules10:46
cjwatsonKeybuk: for a branch status, "fixed" would be sufficient and clearer, and would avoid seb's "is when the update is pushed in the distribution" objection which I guess is due to the "released" word10:47
Keybukcjwatson: ogra disagrees that "fixed" is clear10:47
cjwatsonogra: oh?10:47
Keybukcjwatson: an upstream upstart bug is marked "Fix Committed"10:47
cjwatsonKeybuk: oh, I'm not objecting to "invalid" also being an option10:48
Keybukbecause trunk no longer has any code relevant to the bug, so will make it Invalid10:48
Keybukah10:48
Keybukgot you10:48
cjwatsonogra: (never mind)10:48
Keybukyeah if you get rid of "Fix Committed" then you can rename "Fix Released" to just "Fixed"10:48
cjwatsonright, that's what I mean10:48
Keybukwhich is a much better name without any nasty overtones of "go get it now, pull, pull"10:48
seb128MacSlow: not sure, I've no real opinion either way10:49
seb128MacSlow: we have dbgsym so we don't need those, and since the ubuntu version builds several variants the dbg build might require changes10:50
MacSlowok10:50
ArneGoetjedholbach: the bug still exists in intrepid10:54
dholbachso in any case it needs fixing in intrepid first and the patch needs some changes10:55
wgrantpitti: You said in bug #228969 that libcairo was gone from Intrepid, but it survives to this day.10:57
ubott2Launchpad bug 228969 in libcairo "Remove libcairo from Ubuntu" [Wishlist,Fix released] https://launchpad.net/bugs/22896910:57
pittiwgrant: weird; I was sure I saw it in process-removals, hmm10:59
pittiwgrant: doing again then10:59
wgrantpitti: Soyuz does seem to often have issues with overrides, removals or syncs not sticking...11:00
wgrantThanks.11:00
pittidone11:02
=== sebner_ is now known as sebner
munckfishTheMuso: hi, did you see mail about the PS3 kernel yesterday?11:07
ArneGoetjedholbach: the patch itself (debian/patches/06_fix_vu_dpatch.dpatch) also works against the intrepid version and fixes the issue11:11
dholbachArneGoetje: right... the debdiff needs updating11:12
ArneGoetjedholbach: I will make a new debdiff for intrepid11:12
seb128ArneGoetje: I think I synced scim-hangul a bit too quickly the other day and some changes were still required, could you have a look and maybe reapply those if that's the case since you probably know better about those11:13
ArneGoetjeseb128: err... ok, I'll try11:14
dholbachArneGoetje: ROCK11:14
ArneGoetjedholbach: ?11:15
dholbachArneGoetje: "great" :)11:15
ArneGoetjedholbach: ah :D11:15
* ArneGoetje -> dinner, bbl11:16
=== sebner_ is now known as sebner
* pitti arghs at Python's optparse, which suddenly yields a "UnicodeDecodeError: 'ascii' codec can't decode byte" blabla exception11:30
pitti(suddenly -> after .mo files got installed)11:31
ograblabla exception ? oh, thats an evil error :)11:32
pittiafter some googling it seems I need to do some black magic with setting sys.stdout to a codecs wrapper, or something11:33
pittibut heck -- why should I even care???11:33
DarKnesS_WolFi'm building using that command dpkg-buildpackage -rfakeroot11:34
DarKnesS_WolFhttp://pastebin.ca/105558711:34
DarKnesS_WolFany idea ?11:34
DarKnesS_WolFthis is gdal package from apt-get source gdal11:34
dholbach.11:34
ogra;11:36
ion_؟11:37
cjwatsonDarKnesS_WolF: seems like a bug, if you're building it on the version of Ubuntu it was released for with all the build-dependencies installed11:39
=== halex_ is now known as halex
geserDarKnesS_WolF: you have a lib in /usr/local/lib which gdal links against11:53
cjwatsonoh yes, I can't read11:53
cjwatsonpitti: see e.g. http://bazaar.launchpad.net/~ubuntu-core-dev/debian-installer/ubuntu/annotate/cjwatson%40canonical.com-20080620095615-rf3zpj1maa556ro1?file_id=helptogfxboot.py-20071128181623-fb6n7sukjr5u2r1p-411:57
pitticjwatson: I saw some similar recipes, but those were all hacks which hardcoded a particular encoding11:59
pitticjwatson: I think it is http://bugs.python.org/issue293111:59
pittiI haven't tried the patch yet11:59
pitti(hm, that wasn't it)12:00
pitticjwatson: thanks for the pointer, anyway!12:00
pitticjwatson: I don't see why I should even care in my Python programs (from a 10,000 m perspective)12:01
pittithe output encoding is determined by the locale, and the input encoding is given in the .mo files and thus by gettext12:01
cjwatsonpitti: replacing 'UTF-8' with locale.getpreferredencoding() should deal with the hardcoding objection (not tested though)12:02
cjwatsonpitti: and I certainly agree the current situation is hopeless12:02
pittioh, good idea12:02
cjwatsonpitti: see also http://ewx.livejournal.com/457086.html for the last time I remember discussing this12:03
zulmonining12:05
pitticjwatson: hm, it still fails even with your recipe; *gnargh*; anyway, I'll try again after lunch12:12
ogracould someone poke MOM to get a fresh overview ?12:15
Keybukogra: ? mom is running fine12:23
Keybuklast update was 11 minutes ago12:23
ograKeybuk, how often ? would be good to raise the frequency12:23
Keybukhourly12:23
ograat least on days before import freeze that makes the overview easier12:23
ograhmm12:23
ograk12:23
Keybukthe frequency is not limited by malaise12:24
ograwell, i still see ltsp and moodle on there12:24
Keybukhow long ago did you upload the merged packages?12:24
Keybukmoodle has not yet been published12:24
ogramoodle was 15mins ago, ltsp 1h12:24
Keybukltsp was only published 20 minutes ago12:25
cjwatsonMoM can't really run faster than the publisher ;-)12:25
ograbah, add a time machine :P12:25
Keybukwhen MoM runs at 1105Z, it will see ltsp in the archive (assuming the mirror happens by then)12:25
ograright12:25
ograthats enough then12:25
Keybukit will pick up moodle once that has been published and mirrored, which may be as early as 1105Z, but may not12:25
ograyeah12:26
Keybukthe average MoM run takes between 50 and 70 minutes right now12:26
Keybukso it really can't go any faster12:26
ograi'm just lazy and dont want to compare changes with MoM all the time to find what to grab and whats gone12:26
ogra*-changes12:26
Keybukactually, the 1105Z was cancelled due to lock12:26
Keybukso the next run will be 1205Z (the 1005Z only just finished)12:27
Keybukogra: surely you have a vague idea which source packages you've touched in the last couple of hours? ;-)12:27
ograKeybuk, mine are done, i'm starting to grab others12:27
=== ara is now known as ara_lunch
kwwiimvo: erm, there seems to be a problem with the changelog of the ubuntu-artwork package (dch complains that the maintainer field is empty)12:35
kwwiimvo: as you were the last one to update it, I thought I should ask you ;-)12:35
mvokwwii: let me check12:36
kwwiimvo:  just look at the last two changelog entries and you'll see the problems12:36
Keybukbryce: so, err, around/12:39
KeybukI'm having a little X problem12:39
mvokwwii: please update, I fixed it in bzr12:42
mvokwwii: the " -- author ..." line was empty, emacs is less picky about it, I guess this is why I forgot about it12:43
kwwiimvo: excellent, thanks for the help :-)12:43
kwwiihow in the hell is one supposed to use bzr with launchpad these days? the crappy lp:~path stuff is simply confusing and shitty12:51
kwwiiboah, sorry for going off but this is silliness12:51
Keybuk?12:51
Keybukbzr branch lp:upstart12:52
kwwiihow is it that when I do a pull, make changes, commit and then try to push and it gives me grief about using http?12:52
Keybuksaves remembering a URL12:52
kwwiithe lp stuff is exactly what is messing it up it seems12:52
Keybukbecause you don't have permission to push to that branch?12:52
Keybukwhat's the branch?12:52
kwwiino, I do12:52
Keybukdid you at the point you branched?12:52
kwwii lp:~ubuntu-art-pkg/ubuntu-artwork/ubuntu12:53
kwwiiyepp12:53
Keybukbzr info says?12:53
james_wkwwii: you need to run "bzr lp-login <lp user id>" I expect12:53
kwwiikwwii@clive:~/bzr/test/u-art$ bzr push lp:~ubuntu-art-pkg/ubuntu-artwork/ubuntu12:53
kwwiibzr: ERROR: Cannot lock LockDir(http://bazaar.launchpad.net/%7Eubuntu-art-pkg/ubuntu-artwork/ubuntu/.bzr/repository/lock): Transport operation not possible: http does not support mkdir()12:53
james_wkwwii: and then "bzr push --remember lp:~ubuntu-art-pkg/ubuntu-artwork/ubuntu"12:53
lifelesskwwii: bzr launchpad-login12:53
james_wnewer bzr gives you a hint about this.12:53
kwwiiI just pushed another branch under ~ubuntu-art-pkg and it worked fine12:54
Keybuklifeless: doesn't it use $USER if not set?12:54
lifelessKeybuk: no12:54
Keybuklifeless: isn't that a bit silly?12:54
lifelessKeybuk: root cause - because it doesn't fallback to http on ssh login failure12:54
lifelessKeybuk: hey, $code-I-didn't-writely-urs12:54
lifelessKeybuk: or a better answer - incremental improvements12:55
lifelessKeybuk: if the non-fallback bug is fixed, using $USER becomes plausible12:55
wgrantBut wouldn't that mean it would ask all conceivable key passphrases even if you didn't have an LP account?12:56
ograkwwii, do you have  launchpad_username set in ~/.bazaar/bazaar.conf ?12:56
Keybukrandom bug of the day12:57
Keybukbootchart still runs in recovery mode12:57
ograhey, then you can see how fast you get to the rootshell ... thats a feature :P12:57
Keybukogra: and you see how long you were in the root shell12:58
Keybukand you see what you did while there, and how long that took12:58
Keybukand then you see how long the rest of the boot took after you resume12:58
ograhehe12:58
Keybukand then you see your disk full with a massive svg12:58
cjwatsonkwwii: you can continue to use the old-style bzr+ssh:// URLs12:58
cjwatsonkwwii: replace lp: with bzr+ssh:// in the above and it should work (as a means of getting you past the immediate problem)12:59
cjwatsonKeybuk: stop viewing your porn in recovery mode12:59
ogralol12:59
Keybukcjwatson: I'm trying to get X to work :-/12:59
ograand get a bigger disk ...13:00
Keybukmaybe usplash related13:01
donriis there any interest in making luks accessible to the masses in ubuntu?13:01
donriseems rather quiet on launchpad, https://blueprints.launchpad.net/ubuntu/+spec/ubiquity-luks-support13:02
cjwatsondonri: that's blocked on general support in ubiquity for other than plain block devices13:07
cjwatsondonri: we do need to do that anyway, e.g. for dmraid-support, but it's hard to give much attention to ubiquity-luks-support until that's in place13:08
donricjwatson: sorry, what? I don't understand.13:08
cjwatsondonri: plain block devices == /dev/sda1 and such13:08
cjwatsonas in ordinary hard disks13:08
cjwatsonin order to support luks, ubiquity needs to have support for more complicated block devices in general13:08
donriok...13:08
cjwatsonwhich is a fair amount of work to put in place, although it is on the plan13:08
donrii see, that's good.13:09
SEJeffsoren, ping from yesterday. I misread the patch for libvirt. Please ignore the comment in #ovirt13:09
wgrantcjwatson: Hasn't that been targetted to every release greater than or equal to Edgy?13:12
ograwgrant, and you still didnt send a patch :(13:15
sorenSEJeff: Alright, cool :)13:15
* soren goes to lunch13:15
SEJeffsoren, FYI: I'm trying to get ovirt wui running in Ubuntu. We'll see13:15
ograis anyone doing hotkey-setup  ?13:16
wgrantogra: I wasn't exactly complaining. Just wondering if it really was still coming RSN.13:20
ograwgrant, sure, it will if someone sends a patch (hint hint) ;)13:21
ograwgrant, its not that we dont want to do it, its a manpower issue13:21
donricjwatson: in which upcoming ubuntu release do you estimate it might be included?13:30
loollamont: Could you please add virtualbox-ose in Pas to lpia?13:31
lamontlool: "# Please email comments, corrections to james@nocrew.org, lamont@debian.org and/or adconrad@debian.org.  See ChangeLog for history."13:32
lamontfor tracking purposes and all that13:32
loolOkay13:32
=== ara_lunch is now known as ara
* lamont finds himself annoyed at the encrypted filesystem stuff13:34
loollamont: Mailed13:34
cjwatsonwgrant: *cough*13:34
lamont"/boot/grub/stage1 not read correctly"13:34
cjwatsonwgrant: actually not so much for edgy because we knew it was blocked on the partitioner reimplementation13:34
cjwatsondonri: hard to say at present, sorry; I think intrepid+1 would probably be a decent guess13:34
lamontlool: updated13:35
loollamont: Thanks; when do Ubuntu buildds notice?13:36
lamontlool: that'd be an infinity question (in about 3.5 hours when he should be around)13:36
lamontthe answer for debian is "generally within 24-48 hours"13:37
lamontnot sure how quickly ubuntu will notice13:37
loollamont: Ok; as long as it's automatic, I don't care13:37
lamontentirely13:37
jdstrandlucas: hi. I am doing the ruby1.9 merge for ubuntu, and was doing a schroot amd64 intrepid build before upload, and found that it hangs at test_copy_stream_rbuf(TestIO). Have you seen this before? (I saw your name in the changelog of the Debian package)13:39
jdstrand\sh: ^ have you seen this in your previous merges?13:40
donricjwatson: so 9.04? that's good, it's in october 2009 scary things start happening in sweden.13:41
cjwatsondonri: this isn't a commitment, just my guess as to when we'll have available time13:42
lucasjdstrand: no, I never saw that13:42
* jdstrand scratches head13:42
jdstrandlucas: ok thanks13:42
donricjwatson: of course, it isn't an obligation. I just think it would be very good, for sake of others. I personally already have a LUKS setup, but less technical people are likely scared away by lengthy technical guides.13:45
wgrantdonri: The alternate installer isn't too terrible, and does LUKS.13:46
donriI see lots of windows survivors trying out Ubuntu, and I think security is important. Especially in these days, especially here in sweden.13:46
donriwgrant: from what I understood from the wiki, it does dm-crypt and not luks/cryptsetup?13:46
wgrantdonri: It does LUKS.13:46
wgrantThough it does support dm-crypt for random swap keys, IIRC.13:47
donricool. still, windows survivors who "just surf and chat" likely think it is "too terrible"? I haven't tried the alternate installer though, admittedly.13:47
donriDoes the boot process of ubuntu itself support luks or does it only work for non-root partitions?13:49
wgrantdonri: I run LVM on LUKS for everything but /boot.13:49
donriYea, encrypting /boot isn't easy ;)13:49
siretartit is: boot from USB13:50
donribut can you have the stick encrypted then?13:50
donrianything something has to be non-encrypted, eh?13:50
ogradonri, as i said to wgrant above, every helping hand will speed it up ;)13:51
siretartdonri: no, the stick is removable, so no need to encrypt it13:52
donrithen you have to guard it 24/7 ... if you're paranoid. :P13:52
\shjdstrand: nope..13:52
donriogra: what could I do?13:53
ogradonri, talk to the ubiquity maintainer, he might know ... even if people dont work directly on the luks implementation but help out with other stuff that means he can get his hands free earlier :)13:54
ogradonri, evand is the ubiquity master ...13:54
donrievand: ping :)13:55
evanddonri: tbh, help would require a understanding of partman internals, though anyone with that knowledge is welcome to take a shot at the ubiquity portion of https://wiki.ubuntu.com/EncryptedFilesystems, and if they're successful I'll merge the branch.14:05
cjwatsonah yes, that ubiquity-luks-support spec probably ought to be marked as superseded by encrypted-filesystems ...14:07
wgrantWho has the power to alter blueprints like that?14:08
cjwatsonubuntu-drivers14:09
cjwatsonand the blueprint assignee/drafter/approver14:09
slangasekogra: what package am I supposed to have poked at? planner?  I don't think I've ever poked very deep at that one. :)14:09
cjwatsonI don't want to Just Do It though, the wiki page should be checked for useful things that could be in the EncryptedFilesystems wiki page14:09
cjwatson(but preferably not random implementation guesses from somebody who doesn't know the current implementation)14:10
ograslangasek, i didnt say deep :)14:10
=== enrico_ is now known as enrico
jdstrandkees: I don't suppose ruby1.9 was in the list of packages that FTBFS with your compiler hardening, was it?14:10
wgrantcjwatson: So bugs are very publicly editable but specs are ridiculously restrict beyond even the development team?14:10
cjwatsonwgrant: not my idea14:10
ograslangasek, but many people have touched it and nobody noticed the build error ever :)14:11
ograslangasek, i stole moodle from you if you noticed14:11
cjwatsonwgrant: IMO the practical solution is to stop this pernicious meme of telling people who file wishlist bugs to write specs instead ...14:11
wgrantBlueprint does seem to be pretty much dead these days.14:11
cjwatsonwhich I have been complaining about for years14:11
wgrantcjwatson: I've only seen some novice triagers doing that recently.14:11
cjwatsonmaybe my complaints found some ears14:12
wgrantHopefully.14:14
wgrantAnd hopefully Blueprint will see some development post-2.0...14:14
Rudd-Oguys14:17
Rudd-Ocan I interest you in a speculative development direction?14:17
Rudd-Ohttp://software-libre.rudd-o.com/Streams_vs._documents14:18
wgrantDidn't bryce blog about that a few hours ago?14:19
ograyep14:19
ograits on planet.ubuntu.com14:19
pitticjwatson: hah! I didn't get it to work with your recipe, but finally I found something simple: http://bazaar.launchpad.net/~pitti/jockey/dbus-backend/revision/34814:30
SEJeffsoren: ping. When you get back from lunch can you hop in #ovirt for a q & a with some redhat guys?14:45
slangasekkees: I thought there was supposed to already be a fix for bug #219914 in intrepid, did I misinterpret comments yesterday?14:48
ubottuLaunchpad bug 219914 in apache2 "mod_disk_cache enabled globally by default" [Undecided,Confirmed] https://launchpad.net/bugs/21991414:48
slangasek(the bug is still marked "confirmed" for intrepid)14:48
* ogra WOAHs loudly seeing https://lists.ubuntu.com/archives/ubuntu-users/2008-June/151143.html14:49
ion_ogra: :-D14:51
Rudd-Owgrant: yes, bryce blogged about it.  bryce's blog post sparked my article.14:51
Rudd-Owgrant: in fact, it's the starting point14:51
wgrantRudd-O: So I noticed when I read your article.14:51
wgrantogra: Nice. Very very nice.14:52
ftastgraber, i'm having troubles with pastebinit in intrepid: http://paste.ubuntu.com/22865/14:55
stgraberfta: known bug, we have a potential fix in our bzr branch14:57
stgraberfta: If you would like to test it, just download it from : https://code.launchpad.net/~pastebinit-developers/pastebinit/trunk14:57
ftastgraber, when is the next upload planed ?14:57
stgraberpastebinit is now packaged and maintained in Debian, so I'll see with the Debian maintainer14:59
stgraberit'll be in Intrepid for sure, I don't know when though15:00
ftaok15:00
pittikirkland: would you mind marking https://code.edge.launchpad.net/~kirkland/jockey/kirkland.214914 as merged or obsolete?15:16
cjwatsonpitti: ah, yes, that would work as long as all your output is via _15:23
kirklandpitti: yeah, sure15:23
kirklandpitti: it's obsolete, i think you solved that problem differently than the patch i suggested15:23
kirklandpitti: branch "deleted"15:24
wgrantogra: Look what you've got yourself into now with that XFree86 guy...15:26
Koonwgrant: I've posted an hardy debdiff for bug 24269015:29
ubottuLaunchpad bug 242690 in pam-pgsql "<Ctrl+C> might allow to bypass authentication" [Unknown,Fix released] https://launchpad.net/bugs/24269015:29
Koonwgrant: do you need a specific update for gutsy or will this one do ?15:29
Koon(though the FTBFS patch I had to apply for hardy is hopefully superfluous for gutsy)15:30
ograwgrant, well, i have some desease we call the "helper syndrome" in germany :) i feel pity for him :)15:32
wgrantogra: Well, yes, but this is particularly nasty...15:34
wgrantKoon: You'll need to supply a separate debdiff for each, in general. Make sure you give each a unique version number.15:34
Koonwgrant: ok, will do.15:34
wgrantKoon: Because we have the same version in multiple releases, the Hardy version should be 0.6.3-0ubuntu1.8.04.1, Gutsy 0.6.3-0ubuntu1.1.7.10.1, etc.15:35
wgrantEr, I put an extra .1 in the Gutsy version.15:35
wgrant0.6.3-0ubuntu1.7.10.115:36
ograwgrant, well, but not unsolvable, see my last mail ;) who knows, probably that works15:36
Koonwgrant: got it :)15:36
wgrantogra: We can hope.15:38
pittikirkland: ah, or that; cheers15:41
slangasekseb128: so do you have any more insight wrt my last comment on bug #207072?  is there some way to make gnome-panel happy here, while still making do_mount DTRT?15:44
ubottuLaunchpad bug 207072 in gvfs "nautilus does not display samba shares for machines inside an ADS network." [High,In progress] https://launchpad.net/bugs/20707215:44
slangasekbtw, I think I've found another regression, in at least the latest version of my patch; browsing workgroups seems to no longer work15:44
seb128slangasek: I've to run now, but nothing trivial that I know, the right way would be to use the async api15:46
seb128and libgnomeui has a similar issue15:46
seb128the fileselector widget15:46
slangasekseb128: so those are fixes that would have to be made to gnome-panel and libgnomeui, ok :/15:46
seb128yes15:46
slangasekthen I guess we'll have to scrap this for .115:47
seb128I guess so :-(15:47
seb128or use your first version15:47
seb128which doesn't do the libsmclient call and try password before anonymous15:47
slangasekI think that "my" first version still has the same problem15:47
seb128if that doesn't trigger password prompts for bookmarks, I didn't try15:47
seb128alright, so no easy fix before 8.04.115:48
slangasekbecause it does the smbc_opendir() on mount15:48
* slangasek nods15:48
seb128anyway I've to run, see you later15:48
Lrrrcjwatson: ping?15:49
Lrrrnvm...15:52
=== ubott2 is now known as ubottu
=== devfil_ is now known as devfil
slangasekbryce: I realize that we haven't had any sort of official freeze announcement for intrepid alpha-1 because we've been so scattered, so not to pick on you at all, but please don't change any more X dependencies in the next couple of days; it makes it hard to get releasable alternate CDs when xserver-xorg-video-all picks up new dependencies on drivers that haven't been promoted out of universe yet :)16:14
bryceslangasek: oh, sorry about that16:16
slangasekn/p, just means iterating the CDs again after the next publisher run16:17
bryceslangasek: the xorg change was the only remaining big piece I wanted to get in for alpha-116:17
slangaseksure16:18
slangasekso actually, to amend the above - if yo have any other X dependencies that need changing, please let me know when you upload :-)16:18
brycefor some reason based on last week's meeting, I thought we had until Thursday16:18
bryceok will do.  I also have a libx11 xcb change, but that'll be for hardy not intrepid16:19
slangasekI'm hoping to be able to /release/ alpha-1 this thursday16:20
slangaseksince otherwise we run up against the 8.04.1 release itself16:20
bryceokie doke.  I was planning on mainly focusing on bugs for a bit anyway.  I'll keep in mind not to hold uploads for a bit.16:21
keesjdstrand: it wasn't in gcc 4.2 -- is it blockeded on a FTBFS in intrepid now?16:24
keesslanI thought mathiaz uploaded the fix to intrepid?16:24
keesslangasek: ^^  (irssi lag fail)16:25
slangasekkees: well, apparently he has done so now, I just got a bug closure mail :)16:26
keesslangasek: ah-ha, excellent.16:27
stgraberRiddell: bug 238839, any idea what's causing it ?16:40
ubottuLaunchpad bug 238839 in italc "ICA process started multiple time in KDE" [Undecided,New] https://launchpad.net/bugs/23883916:40
Riddellstgraber: sounds like ICA should be intelligent enough to quit when it is started and other instance is already running16:42
stgraberRiddell: it shows a warning message so that's not good16:43
Riddellreplace the warning with a quit then16:43
stgraberand I don't see why KDE's session restore thing starts ica when it's originally been started from an autostart ...16:44
stgraberthings autostarted shouldn't be stored in the list of applications to restore at next login16:44
Riddellother apps don't have any problems with it16:45
=== mkrufky is now known as Guest59299
=== mkrufk1 is now known as mkrufky
jdstrandkees: well, my schroot ruby1.9 build doesn't work right, but the dchroot on ronne seems ok16:54
jdstrandkees: the ronne build just finished btw, so that's info hot off the press16:55
exodosIn some situations it is needed to run 32bit userland with 64bit kernel (we're running hardy under xen like this). Now you have to download deb packages and manually issue dpkg -i --force-architecture *.deb. In debian, in 32bit repositories they have package called linux-image-2.6-amd64, which is installing the latest 64bit kernel. Would it be possible to add similar funcionality to ubuntu?16:55
keesjdstrand: what failures are you seeing there?16:56
exodoswith Apt Super Cow Power life is much easier....16:56
kees(in your chroot, I mean)16:57
joaopintoexodos, if you need a 32 bits userland on a 64 bits system, you do a full 64 bits install, and do a chrooted 32 bits install16:58
jdstrandkees: it actually builds fine, but one of the tests fails. it is an innocuous looking little thing16:59
* jdstrand goess and gets it16:59
keesjdstrand: arch-sensitive?17:00
keesjdstrand: how long is the build/test cycle?17:00
jdstrandkees: well, amd64 schroot, and amd64 dchroot (ronne) act different, so I dare say no17:00
keesfortify has been known to cause runtime issues for unusual code.17:00
jdstrandkees: I'm kinda leaning toward my schroot not being right17:01
jdstrandkees: interesting, but I should have seen that in dchroot with dpkg-buildpackage-- correct?17:01
keesI can kick one off to check too -- anything special I need to do, or just build what's in the archive?17:01
keesjdstrand: I'd think so -- is the chroot up to date?17:01
jdstrandkees: try building the sid version on intrepid17:01
jdstrand(I was doing a merge)17:02
jdstrandit has the security fixes in it, and import freeze is tomorrow17:02
jdstrandkees: oh, and it doesn't take too terribly long to build17:03
keesjdstrand: okay, I'll kick it of17:04
keesruby1.9 1.9.0.2-1 ?17:04
jdstrandkees: yes17:05
keesjdstrand: kicked.17:05
jdstrandkees: the test that just hangs is test_copy_stream_strio_rbuf in test/ruby/test_io.rb17:05
jdstrandkees: http://paste.ubuntu.com/22893/17:06
keeswhile it's probably not related, I've had to set things like virtmem limits to get some builds from eating my system alive (gcc-4.3, I'm looking at you).17:06
jdstrandkees: oops, I meant test_copy_stream_rbuf17:06
jdstrandkees: http://paste.ubuntu.com/22894/17:07
jdstrandkees: anyway, it certainly doesn't look like it should hang, but it does...17:07
jdstrandkees: my ruby foo is amazingly low (but growing as of late), so I'm still working through it17:08
* jdstrand wonders if the dchroot is up to date17:08
=== |Xorothal| is now known as Xorothal
liwthis is a bit embarrassing... but what am I doing wrong? I took a package that uses dpatch, modified debian/rules and a few other files (none of the patch files), and now I can't run dpkg-buildpackage, because dpkg-source complains that the debian/patches/*.patch files change permissions and this is unrepresentable in a diff17:22
liwdpkg-buildpackage calls debian/rules clean, which calls dpatch, which changes the permissions, but how do I handle this?17:22
ion_That should not be a problem, just a warning. #ubuntu-motu is the correct channel for continuing this discussion, btw.17:22
cjwatsonliw: what's the error?17:23
cjwatsonliterally, I mean17:23
liwoh, oops, sorry, I should start reading errors from the top17:23
liwI had a binary file change in there, too17:23
liwworks now, thanks17:24
saftsackhttp://rafb.net/p/guZU8e56.html17:31
cjwatsonsaftsack: #ubuntu-kernel, or a bug report17:41
saftsackcjwatson, kk thank you17:42
keesjdstrand: that test hangs for me too.  :(17:48
gesermathiaz: Hi, I've seen that you uploaded apache2 to hardy-proposed. Please do also a rebuild-only SRU of apache2-mpm-itk (universe) so it gets rebuild with apache2 from -proposed.18:08
mathiazgeser: that needs to be acked by the motu-sru team IIRC18:16
mathiazgeser: could you file a bug for it (so that it doesn't get lost ?)18:16
gesermathiaz: can do18:23
jdstrandkees: ok, is is updating the dchroot (it had 555 updates)18:26
jdstrands/is is/IS is/18:31
jdstrandkees: I'm going to try it on hardy, and in the dchroot on ronne (when it gets done updating)18:33
gesermathiaz: bug #24301218:34
ubottuLaunchpad bug 243012 in apache2-mpm-itk "[SRU] apache2-mpm-itk uninstallable with apache2.2-common from hardy-proposed" [Undecided,New] https://launchpad.net/bugs/24301218:34
=== Xorothal is now known as nohelphere
jdstrandkees: 1.9.0.2 built fine on hardy18:56
=== nohelphere is now known as Xorothal
jdstrandkees: here is the list of packages that were updated http://pastebin.ubuntu.com/22928/ (gcc is among them)19:05
=== mkrufk1 is now known as mkrufky
kirklandslangasek: pitti: hiya, pam+debian_policy question for you......19:30
* slangasek hides under a pile of SRU paperwork19:30
kirkland:-)19:31
kirklandslangasek: shall i just email you and you can respond in due time?19:31
slangasekdepends, how deep of a question is it? :)19:31
kirklandslangasek: i think it's the typical one where i say, "hey i have a way to do $foo", and you say, "nope, that way to do $foo is highly illegal" and you bop me over the head with a whack-a-mole padded bat19:32
slangasekoh, ok - we can do that on IRC then :-)19:32
kirklandslangasek: i'd like to know the best way to echo "auth required pam_ecryptfs.so unwrap" >> /etc/pam.d/common-auth && echo "password required pam_ecryptfs.so" >> /etc/pam.d/common-password19:33
slangasekkirkland: ... by not doing so ;)19:34
kirklandslangasek: i think that debian policy would forbid me from modifying those files in the ecryptfs pam package19:34
slangasekyes19:34
slangasekjdstrand has a package that lets users enable particular pre-formed pam profiles19:34
kirklandslangasek: interesting, okay, so it absolutely has to be a manual operation by the administrator?19:35
slangasekI have a plot to reorganize how /etc/pam.d/common-* are managed, which I hope to implement in time for intrepid but this is still up in the air19:35
mathiazkirkland: slangasek is refering to the auth-client-config package19:35
slangasekalso, the trivial >> here may not work as expected19:36
kirklandslangasek: sure, that was for irc-simplicity only19:36
slangasekok :)19:36
kirklandslangasek: the shell script i have greps and seds things around to make sure it gets put in the right place in the stack, that there aren't more than one, etc.19:36
kirklandslangasek: but it's no where close to being acceptable19:36
slangasekright, to know what the right place is in an arbitrary stack, you basically need all the information you don't have yet because I haven't done my config rewrite19:37
slangasekhmm, maybe I could get the design for this fleshed out to where I could pawn the implementation off on you? :)19:37
kirklandslangasek: :-)  perhaps.........19:38
slangaseksince you seem to have a fetis^W affinity for hard PAM problems ;)19:39
kirklandslangasek: ugh, yeah, seems that way lately, doesn't it?19:40
ion_Ew, my fonts became blurry after a fontconfig update. It doesn’t seem to recognize lcdfilterlegacy anymore. :-(19:42
kirklandmathiaz: okay, thanks for the pointer, i'll go look at auth-client-config19:44
ograslangasek, not getting -nsc and -geod in will cost us a lot LTSP users19:51
ogra(we are the leading distro here, and slowly lose out on others due to not supporting the most commonly used X server since gutsy)19:52
slangasekogra: and therefore I should compromise the integrity of the SRU process to shoehorn in a last-minute, badly-done update with no justification given for part of the changes?19:53
ograslangasek, a lot of people have tested the packages from Q-Funks PPA and i doubt you can introduce a regression for something that didnt work at all before19:53
slangasekwhere does it say that the nsc package didn't work before?19:53
slangasekthat's not written in the SRU bug log, in the changelog, or in the patch header19:54
ograslangasek, well, i was hoping it would turn out good in the end, i have a good bunch of users waiting for the 8.04.1 CD for building their new LTSP19:54
slangasekit says that there's one particular PCI ID that nsc wrongly claims to support19:54
slangasekI'd be fine if dropping that ID was the only change being made19:54
ogrageode was completely borkesd since mid of the gutsy cycle19:54
slangasekI'm not talking about geode.19:54
ogransc and amd as well afaik19:55
slangasekI still need to review the geode SRU; this one is already in -proposed, and is well on its way - if there are any issues with it, we're better off fixing those now and following through on that SRU19:56
ograanyway i just wanted to raise that to your attention ... the decision is yours indeed and i largely agree with you but still am sitting between the chairs here19:56
slangasekbut the nsc upload is not ok to shove in at the last minute19:56
slangaseknot without a more substantial justification, and more substantial evidence that it doesn't regress anything19:56
sbeattieogra: it'd be useful if your users could try out the packages and report feedback on the bugs.19:57
sbeattie(packages in -proposed, that is)19:57
ograsbeattie, well, they have systems in production ... people with ltsp test envs are very rare19:58
ograand most of them still run feisty because of that breakage19:58
sbeattieyet they're willing to run a PPA?19:58
slangaseksbeattie: the package at issue here is one I'm not accepting into -proposed, because it's been uploaded well after the 8.04.1 freeze19:59
slangasekthe -geode package is fine - it looks like it just needs a minor review, another short round of verification, and then a push into -updates; it's the -nsc driver package that's the problem20:00
sbeattieoh, okay, I'll shut my mis-informed mouth, I assumed this was about bug 21963020:00
ubottuLaunchpad bug 219630 in xserver-xorg-video-nsc "please add "geode" to driver list in hw/xfree86/common/xf86AutoConfig.c" [Undecided,In progress] https://launchpad.net/bugs/21963020:00
slangasekbug #21411920:00
ograsbeattie, it is20:00
ubottuLaunchpad bug 214119 in xserver-xorg-video-geode "[HARDY] Koolu W.E. (ION A603) does not detect higher resolution than 800x600" [High,Fix committed] https://launchpad.net/bugs/21411920:00
ograthey are both related20:00
slangaseker, no - you're right, bug #219630 :)20:00
ograits pretty much the same20:01
slangasek219630 is the one requesting the nsc SRU20:01
ograbut Koolu is even worse, they ship ubuntu by default and already had probs in gutsy20:01
ograand they used to promote us loudly20:01
ogranot anymore though (even though they still ship with ubuntu afaik)20:02
slangasekand the fix for that is already in -proposed and on track for inclusion in -updates, so I don't see that there's a problem there20:02
ograyeah, thats geode ...20:02
jdstrandkees: interesting, updated dchroot on ronne worked fine20:04
sbeattieogra: feedback for the -geode would still help it get out the door.20:08
ograsbeattie, i thought geode was ok already ?20:08
slangasekI see that the -geode one is already verification-done, and was planning to copy it toda20:11
sbeattieOh, okay20:13
* sbeattie wishes tags could be applied to individual tasks rather than only just to bugs as a whole.20:13
keesjdstrand: hmpf :(20:17
jdstrandkees: yeah, bit of a head scratcher20:17
jdstrandkees: feels like a schroot thing20:17
Q-FUNKslangasek: please see my comments to bug #219630.  I'm really sorry that the fix got so complex, but it involved fixing 3 packages at the same time, plus packaging a new upstream to fix hardware issues.  not an easy task for anyone to handle.20:27
ubottuLaunchpad bug 219630 in xserver-xorg-video-nsc "please add "geode" to driver list in hw/xfree86/common/xf86AutoConfig.c" [Undecided,In progress] https://launchpad.net/bugs/21963020:27
slangasekQ-FUNK: "avoid PCI ID conflicts in X.org at all cost" - why?  does X crash horribly when it encounters this situation, or does it just pick one of the drivers?20:28
Q-FUNKslangasek: so far, it seems to simply fail to launch.20:29
slangasekmm, yuck20:29
Q-FUNKwhether this is because it unfortunately picks the wrong driver at random is beyond me.  I tried investigating this as much as I could and could not come up with a conclusive answer.20:30
slangasekwhich PCI IDs are conflicted over, by which sets of drivers?20:30
slangasekbryce: ^^ do you know the answer to the above, regarding Xorg's behavior when more than one driver tries to claim the same PCI ID?20:30
Q-FUNKslangasek: it mainly is xserver-xorg-video-nsc that claims ID numbers for hardware covered by -cyrix and -geode20:30
slangasekok, but only one of these PCI IDs that you're fixing up in NSC is the -geode ID, right?20:31
slangasekand the others are covered by cyrix, which so far has had no discussion in the bug log of regression testing20:31
Q-FUNKto make a long story short, the hardware changed owner 3 times and some legacy (unused) code remains from cyrix time in both -nsc and -geode.  my package of -geode skipped these right from the start, but -nsc kept them.20:32
slangasekI accept that dropping those PCI IDs from nsc is correct for intrepid, but there are a whole swath of problems with dropping them in an SRU that I don't think have been addressed yet20:32
Q-FUNKright, because cyrix is presumed to correctly handle cyrix hardware already.20:33
slangasekwhich packages support the chips with the 0x1078 vendor ID?20:33
bryceheya20:33
Q-FUNKcyrix20:33
slangasekok20:33
Q-FUNKbut nsc laso has them, though unused20:33
slangaseksee, "presumed" is why this is a problem, when it would have to be pushed on such short notice that there's no real opportunity for testing20:34
Lightkeycyrix 686, yay!20:34
Q-FUNKthe main issue is with debian's point and shoot way of generating PCI ID lists.  matching every PCI vendor with every PCI device found in the source code generates false positives.20:34
Q-FUNK  this is why -nsc needs to be fixed, tlo clear the room for cyrix and geode to claim their hardware.20:34
slangasekif you updated the nsc SRU to /just/ change the geode ID, I would be willing to accept that20:34
bryceslangasek: I believe that the behavior with multiple drivers claiming the same id is undefined20:35
slangasekbryce: well - should it use a random driver, or just fall flat on its face...?20:35
Q-FUNKI have access to nsc and geode (amd) hardware.  removing the conflicts fixes the behavior. I get X.  without removing those conflicts, I don't.20:36
ograi just heard in fedora it does the latter20:36
slangasekif the answer is "use a random driver", then we've got a fair amount of regression potential with this SRU20:36
slangasekif the answer is "fall flat on its face", we have a much more critical bug to weigh that against20:36
bryceslangasek: I would expect that it uses a random driver, but this isn't something I've experimented with so I don't know for certain20:36
slangasekQ-FUNK: yes, and I'm ok with getting that fixed, for the hardware where it's been tested20:36
slangasekit's the change in behavior for hardware that hasn't been tested that bothers me20:37
* bryce nods20:37
Q-FUNKslangasek: in that case, it mostly involves moving one claimed ID from the -nsc to the -geode driver.  versioned conflict needed in -geode against older -nsc packages.20:37
slangasekamong other things, consider the case of a user with a trimmed-down set of packages installed - they know they're using -nsc (even though their chip is Cyrix), so they only have -nsc installed, not -all.  Now they upgrade, and their chip is no loner supported.20:38
slangaseks/loner/longer/20:38
Q-FUNKI agree that lack of testing for cyrix hardware could be a gamble. however, most thin client hardware out there uses either nsc or geode(amd) Geodes.20:38
slangasekQ-FUNK: ok.  Can we try the -nsc NMU again, with only the change for the geode PCI ID?20:38
slangaseker, s/NMU/SRU/20:38
slangasekthe cyrix stuff, from what I'm hearing, can reasonably be postponed until after 8.04.1, when we can get proper regression testing20:39
Q-FUNKslangasek: do you also want us to revert debian's build script changes, on aspects where it doesn't involve shipping a fixed static nsc.ids list?20:39
slangasekQ-FUNK: that is definitely my /preference/20:39
slangaseksince it means less time that I have to spend trying to understand those changes20:40
Q-FUNKit could be done if needed, but I'm the wrong guy to do it, as I cannot make ends or tails of the XSF scripts. that's how I ended up choosing CDBS to package -geode, way back.20:40
Q-FUNKbryce: do you think you could look at my last debdiff and skim it into just shipping a different nsc.ids then?20:41
calcslangasek: do we have a meeting today at normal time20:41
calcslangasek: i didn't see an email about it this week20:41
brycecalc: afaik we do20:41
calcbryce: ok20:42
brycecalc: it may be a short one though20:42
calcok20:42
bryceQ-FUNK: ok I can do that for you - link me to the debdiff again plz?20:42
Q-FUNKslangasek: so, beyond the trimmed down delta for -nsc, are my latest debdiffs for -geode and -all suitable for SRU for 8.04.1 ?20:42
Q-FUNKbryce: starting at https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/219630  grab http://launchpadlibrarian.net/15556613/debdiff_2.8.3-2_to_2.8.3-2ubuntu1.txt20:43
ubottuLaunchpad bug 219630 in xserver-xorg-video-nsc "please add "geode" to driver list in hw/xfree86/common/xf86AutoConfig.c" [Undecided,In progress]20:43
slangasekQ-FUNK: I believe that the only debian/ changes that need to be kept are the ones to debian/control; everything else should be cosmetic with respect to this particular patch20:44
Q-FUNKslangasek: adding the Conflicts I had forgotten in -geode against -amd, that is.20:44
Q-FUNKslangasek: ok, fair enough.20:45
slangasekthe geode/all stuff looks good to me, but I'm still digesting parts of it20:45
Q-FUNKbryce: can I count on you and tjaalton sanity-chekcing all 3 debdiffs -just to be on the safe side?20:45
brycetjaalton is on vacation20:46
Q-FUNKslangasek: the -all part is just to make xserver-xorg-video-all Depends on xserver-xorg-video-geode instead of  xserver-xorg-video-amd.  this should have already been done in 8.04.0, but we forgot to do it on time.20:47
slangasekright.  -amd is currently a transitional package, correct?20:47
Q-FUNKit mostly exists to allow orphaners to drop the transitional package, including possible symbolic links included in older -amd transitional packages that were meant to provide backward-compatiblity for people wiht a static xorg-conf containing "amd" as the driver, but which don't work on debian derivative.s20:48
Q-FUNKyup20:48
slangasekI thinkk I'm also confused by the changelog for xserver-xorg-video-geode 2.9.0-1ubuntu2.120:48
Q-FUNK2.1 or 2.2 ?20:48
slangasek"Removed the GX model's PCI ID from geode.ids to fix LTSP usage case." - is that the same PCI ID that's now being dropped from nsc?20:49
slangasekor a different one?20:49
Q-FUNKsame20:49
slangasekso... it's being dropped in both places?20:49
Q-FUNKwe had to temporarily drop it, until -snc was fixed20:49
Q-FUNKit's back in 2.220:49
slangasekah20:49
slangasekthe 2.2 changelog doesn't mention this20:49
Q-FUNKhence the versioned conflicts in -geode20:49
Q-FUNKno?20:49
slangasek+xserver-xorg-video-geode (2.9.0-1ubuntu2.2) hardy-proposed; urgency=high20:50
slangasek+20:50
slangasek+  * Removed the transitional symbolic links for amd_drv.so (LP: #219630).20:50
slangasekthat's the whole changelog20:50
Q-FUNKargh20:50
Q-FUNKforgot to mention that20:50
Q-FUNKthe whole cherry-picking method involved in making an SRU has been a hard one on me20:50
Q-FUNKmy debian packages have the whole story, rather than one single line refering to an LP bug as used in SRU20:51
slangasekif you have time to prepare a 2.2 with a fixed changelog, that would definitely be appreciated too; changelogs are important so users know what's changed, not just so the SRU team does20:51
bryce(and do de-confusify fellow packagers)20:51
Q-FUNKslangasek: I initially had that.  pitti suggested that having a multiple-line changelog was unacceptable for an SRU.  he suggested that I should instead rewrite this into a sigle line that closes an LP bug.20:52
slangasekactually, that's not what pitti meant20:52
Q-FUNKno?20:52
slangasekI know that's what he seemed to say :)20:52
Q-FUNK:(20:52
Q-FUNKwell, ok. misunderstandings do happen20:53
slangasekwhat he meant was that the SRU should condense the changes into an entry for a single version20:53
Q-FUNKespecially when trying to make sense of changes in 3 packages, plus a new upstream, to fix one single issue, handled by a part-time maintianer.20:53
slangasekinstead of incorporating, verbatim, the changelog entries for other versions that aren't being uploaded in an SRU20:53
Q-FUNKah20:54
* Q-FUNK bangs head20:54
ograforcing a single line changelog would be insane :)20:54
Q-FUNKok, that's a bit more clear now.20:54
Q-FUNKheh :)20:54
ogramy ltsp SRU fixed ten bugs ... that would have been a looong line :)20:55
bryceogra, well if you omit spaces and vowels maybe?20:55
Q-FUNK:D20:55
ograheh20:55
Q-FUNKguys, I appreciate everyone's sense of humor, especially in moments like these20:55
Q-FUNKthis has been a though bug to tackle20:55
bryceyeah20:56
Q-FUNKit at least lightens the mood :)20:56
stgraberogra: "Fix LTSP (LP: xxx, LP: xxx, LP: xxx, ...). You see, it's not that hard :)20:56
stgraberok, not likely to be accepted :)20:56
ograyeah :)20:56
Q-FUNKslangasek: anyhow, if it's ok with you, starting with approving that -all change to drop the transitional package would be a good start.20:57
slangasekyes, that one is straightforward20:57
Q-FUNKslangasek: then, with bryce's help, we'll skim -nsc and re-submit.20:58
slangasekok20:58
slangasekwill you have time to redo the changelog for -geode?20:58
Q-FUNKas for -geode, was it ok as such (adding the forgotten Conflicts) ?20:58
Q-FUNKööö... i might get around it tonight.  it's already  23:00 here, mind you.20:59
slangasekthe changelog at present is definitely misleading, but if you won't have time to fix it then I'd rather accept it today as-is than wait another day on this20:59
Q-FUNKthankfully, it's only a one-line addition20:59
slangasekOTOH, I can afford to wait until you fall asleep to see if you get it done :)20:59
Q-FUNKok, then let's get it in. as long as both -nsc and -geode get in at the same time, we'll at least fix the PCI ID conflicts and send -amd into oblivion for good.  that would already be something good.21:00
slangasekhrm; the transitional symlink is dropped from -geode, but not added to -amd21:01
Q-FUNKslangasek: can I review the resulting packages from hardy-proposed tomorrow morning and let you know if I notice anythign fishy, before they get pushed into hardy-updates?21:01
slangasekthat means the package description is also wrong, because it says "If you are using a static xorg.conf, edit the Device section and change the Driver value from "amd" to "geode" before purging this package"21:02
slangasekapparently it should say, edit the Device section before /installing/ this package. ;)21:02
slangasekQ-FUNK: oh, yes, the packages certainly wouldn't be pushed to -updates that soon21:02
Q-FUNKslangasek: right. it initially migrated to -amd, but was dropped entirely,  because it creates a whole mess on debian derivatives.  I replaced that with a notice in -amd's Description, advising people to upgrade their static xorg.conf if they have any to use "geode".21:02
Q-FUNKsync :)21:03
slangasekQ-FUNK: then perhaps s/ before purging this package// ?21:03
slangaseksince it's not the purging that will break their static xorg.conf21:03
Q-FUNK"before" rather than "after" sounds good,21:03
slangasekok21:03
Q-FUNKindeed. it's the fact that calling "amd" will produce a dead screen, since there's no such driver anymore.21:04
* Q-FUNK writes himself a TODO21:04
slangasekit does seem to me that it would be better to include this symlink in the transitional package21:05
Q-FUNKI used to have it, but it disrupts operation in LTSP21:05
slangasekif 8.04.1 doesn't install the -amd package (by fixing -all), then it shouldn't disrupt anything21:06
slangasekwhereas the users who have it installed presumably would like things to actually be compatible...21:06
Q-FUNKif you look at -geode's changelog at debian, I initially moved the symbolic link from -geode to -amd, to make it purgeable. that wasn't enough.  in practice, for as long as two drivers (because of the symbolic link, I guess) claim the hardware, X barfs.21:06
slangasekah :/21:07
slangasekok21:07
=== donri is now known as bancus
Q-FUNKthat's how i ended up entirely removing the symbolic link.21:07
=== bancus is now known as nicte
Q-FUNKI don't think that there's any ideal way to get people upgrading from << hardy to get their static xorg.conf (if any is used) fixed automagically upon upgrade.21:08
=== nicte is now known as florolf
Q-FUNKor well... I supposed that some postinst sed script could do it, but I find this too scary to rely upon.21:09
Q-FUNKnot being a 'sed' guru, i didn't dare attempt it.21:10
slangasekyeah... I would dare21:10
slangasekhalf the sed evil in the xorg package is my handiwork21:10
slangasekbut it's a little late for that now21:10
bryceaha!!21:10
bryce;-)21:11
=== florolf is now known as mungojelly
bryceslangasek: I run into your name in the randomest places :-)21:11
slangasekyeah, funny that21:11
bryceonce I got sick of the silly default names in the game Pioneers, so I patched it to use the names from AUTHORS21:12
slangasekhahaha21:12
brycelo and behold, I fire it up and there I'm playing against you!21:12
Q-FUNKthis being said, patches are welcome.  besides, this would be double-useful as, later this autumn, -geode is supposed to merge back GX1 support and supersede -cyrix and -nsc.21:12
Q-FUNKit could be fun to parse xorg.conf for either one and upgrade it for the user.21:12
Q-FUNKhowever, this would break dexconf configuralibty, since it becomes a manually hacked xorg.conf too.21:12
Q-FUNKtypos r us21:13
brycehmm, next time I volunteer for an autoconf cleanup task, someone shoot me first ;-)21:13
Q-FUNKdoes a vintage soviet AK47 from a military surplus store suit you? :-P21:14
Q-FUNKok, I better head home here.21:14
brycethat'd be great21:14
ograQ-FUNK, well, by authmn this year we shouldnt have any xorg.conf anymore21:15
ogra*autumn21:15
Q-FUNKslangasek: thanks for the SRU run-trough.  hopefully, we'll have this fixed within the next few hours.21:15
Q-FUNKbryce: and thanks for helping out.  it's immensely appreciated.21:15
slangasekQ-FUNK: sure; thanks for persevering :)21:16
ion_ogra: Yay21:16
Q-FUNKit's been an... interesting ride.  I never got around doing any security release at debian for any of my packages, so this SRU is the closest thing I've ever seen to live fire.21:17
Q-FUNKand trying to keep track of changes in 3 packages was a nice peice of mental  gymnastics.21:17
Q-FUNKanyhow, 'night everyone :)21:17
brycecya21:18
bryceautoconf is one project I'd actually like to see slow *down*.  some of these changes are fairly gratuitous21:20
slangasekcalc: <popping the stack> yes, I believe we are to have a meeting today at the normal time :)21:22
slangasekmumble, previous unverified xorg SRU sitting in -proposed for a month21:24
bryceI think cjwatson's just been uber busy catching up on administrivia21:24
tjaaltonbryce, slangasek: howdy! IIRC the xserver will pick the first driver to support the ID in alphabetical order21:27
brycetjaalton: heya!  ok thanks, I wondered if that might be the case21:27
slangasektjaalton: hmm, then I wonder why nsc gives problems, g < n :)21:27
brycealthough it makes me wonder why nsc would mess things up, since amd and geode are alphabetically higher21:27
tjaaltonhum, right21:27
tjaaltonactually, by looking at the patch 03_auto_load_driver.diff, IIUI, the _last_ driver to support it would end up being used21:32
slangasekah, that makes sense then :)21:32
brycereverse alpha.  good to know21:32
brycecd /usr/share/xserver-xorg/pci/ ; cat *.ids >> voodoo.ids ; echo "Bwahahahaha"21:33
tjaaltonhehe21:34
tjaalton*boom*21:34
bryceslangasek: hum, this is weird, the -nsc package in hardy includes a patch that doesn't actually seem to apply21:39
slangasekawesomesauce21:40
slangasekit doesn't seem to /be/ applied, or it tries to apply it and fails...?21:40
bryceit tries to apply it, but it's already been applied to src21:40
slangasekwhee21:40
bryceer, something like that.21:41
bryceanyway, this makes the debdiff finally make sense, I'll get it fixed up.21:41
* ogra hugs bryce 21:41
ograths issue has gone on far to long for that little set of changes thats actually needed21:42
bryceogra, it's certainly been a learning experience all around21:45
* ogra hopes so 21:45
cjwatsonbryce: correct; if it's a short meeting tonight, I shall be happy :)22:07
bryceslangasek: am I correct in that since -nsc is 1:2.8.3-2 in hardy currently, this new upload should be versioned as 1:2.8.3-2ubuntu0.1 ?22:27
bryceslangasek: anyway I'm guessing yes.  I've finished the packaging22:33
bryceone last time doublechecking everythign and then I'll upload to hardy-proposed22:34
bryceslangasek: uploaded22:36
* ogra appluds22:36
ograor so22:36
bryceogra if you have means to test, it would be mucho appreciated22:37
ograi need to dig up the DBE60 thincan i got from martin and set that up for testing, not tonight anymore, but i can give it a go tomorrow22:38
brycethat'd be great22:38
ograshould we ping cr3 to trigger someone to test it on koolu ?22:39
liwdoes anything in Ubuntu care about Standards-Version in debian/control?22:39
bryceogra yeah good idea22:39
bryceliw not afaik22:39
slangasekbryce: xserver-xorg-video-nsc/1:2.8.3-2ubuntu1, yes please :)22:39
ograliw, the developer after you who has to merge mnually just for the standards change ...22:39
ograbut nothing apart from that :)22:40
ograoh, and lintian22:40
cr3ogra: what's up dude? xserver-xorg-video-nsc? what would you like me to test exactly?22:40
liwogra, well, I'm asking to decide whether to merge the Standards-Version from Debian or to keep the one in Ubuntu :)22:40
ogracr3, hardy-proposed22:40
ograliw, if its only for the sake of updating the standards i wouldnt ... if its one change among others i would22:41
ogragenerally if its standards only that should be done in debian and be synced imho22:42
liwogra, of course22:42
bryceslangasek: ok well you got 2ubuntu0.1 in there, I hope that's ok22:43
liwthis is part of a larger set of changes; I didn't want to bump the S-V in Ubuntu if Ubuntu follows an older version of policy22:43
ogracr3, bottom line is "shuld all work"22:43
brycecr3: I've just uploaded a fix to make hardy installable and functional on geode hardware22:43
brycecr3: so we would encourage re-running your tests on any geode hardware you have and verify that X now works on them.22:43
cr3ogra: should it be tested in both desktop and ltsp mode?22:46
ograindeed :)22:47
ogrado you have a thincan ?22:47
cr3ogra: yep22:48
ograah, well then there too22:48
ograi'll test it myself tomorrow on ltsp22:48
cr3I'll have to test it tomorrow as well22:49
cjwatsonliw: I'd second ogra, just sync S-V with Debian; I'd go so far as to say that S-V should never be changed in Ubuntu unless you are completely repackaging from scratch22:59
liwyep22:59
cjwatsonliw: the notion of following a version of policy has always been a bit sketchy in Debian anyway - it's really more for the maintainer to say "yup, I've checked up to here"23:00
cjwatsonso it's kind of a bizarre thing to bump :)23:00
liwyeah, that's what Debian uses it for; I find it useful for myself, to verify against the upgrading list23:00
slangasekbryce: 0.1 is probably more proper anyway; ubuntu1 was just what had been in the -proposed queue before23:01
bryceoh, I didn't spot that23:02
cjwatsonliw: *nod*23:03
slangasekbryce: um, ok; on this 0.1 you've uploaded for nsc, you're still disabling the cyrix PCI IDs, which I explicitly requested not be done in this round due to timing relative to the point release23:19
bryceslangasek: er, guess I didn't catch that.23:22
bryceI gathered Q-FUNK simply wanted all the autoconf junk straightened out23:23
bryceare there any other changes?23:23
slangasekbryce: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/219630/comments/5023:23
ubottuLaunchpad bug 219630 in xserver-xorg-video-geode "please add "geode" to driver list in hw/xfree86/common/xf86AutoConfig.c" [Undecided,In progress]23:23
slangasekstraightening the autoconf junk is appreciated, but it's the cyrix change that I consider the blocker due to our inability to regression-test here23:24
slangasekScottK: do you have any interest in taking care of the libselinux/libsepol merges, by change?23:24
slangaseks/change/chance/23:24
ScottKslangasek: No.  I thought tresys and manoj were going to work so sort stuff out.23:27
ScottKWithout help from them, I'd be tempted to sync and go from there.23:27
slangasekoh, is that not done yet? :/23:28
bryceslangasek: ok I see, Q-FUNK had said he was uncomfortable doing the cleanup of the XSF scripts and asked if I would "skim it just shipping a different nsc.ids then" which is what I did.  I assumed the debdiff he gave me was correct other than that.23:29
bryce*sigh* this is like the sru from hell.  one sec I'll fix it.23:30
ScottKslangasek: I've ping'ed them a couple of times on #ubuntu-hardened and gotten nods, but no action.23:31
ograbryce, well, its intresting to see how it melts down to a handfull of lines once *you* touched it23:31
slangasekScottK: well, I'm aware that Manoj has integrated at least some of their changes; maybe a sync wouldn't be the worst outcome23:32
ScottKIt would at least get us rebased from Debian and then we can adjust from there.23:33
bryceogra, yeah well it would help if I'd learn to read23:34
ograah, come on you fixed the probelm in 1h while th ebug goes back and forth since 3 months or so23:34
bryceslangasek: so should this be ubuntu0.2 or ubuntu2?23:34
ograwithout any proper outcome ...23:35
slangasekbryce: ubuntu0.123:37
slangasekbryce: you get to reuse the number because I'm not letting this other one into the light of day ;)23:37
bryceaw23:38
bryceok, so I just need to figure out what the cyrix pciid is.  hmm23:38
slangasekbryce: it's the line that's been commented out in Makefile.am in the patch23:39
slangasekthis patch disables registration for all devices with cyrix as the vendor ID23:39
bryceso is the change just uncommenting that line?23:40
slangasekI believe so23:40
bryceok that should be trivial23:40
brycehowever I notice they also reshuffled the ordering23:40
bryceI'll check if that's significant23:40
calcbryce: ping23:47
calcbryce: Benjamin Drung seems to have tested the various methods and it didn't work for him, so he sounds like a good candidate for the new debs23:48
calchttps://bugs.launchpad.net/~bdrung23:48
bryceok cool, would you like to ask him to test with that libx11 patch (since you've been the contact on that bug so far), or shall I?23:50
calcbryce: it would probably be better if you did so if he has questions it would be to the person who has a clue ;-)23:51
calci still don't have any idea why it seems that users that have this problem don't have the problem under a new user account, even removing .openoffice.org2 dir doesn't help them23:51
calcbut hopefully removing xcb will help out23:52
calcthey mention removing gtk/gnome ooo addon helps fix the problem so maybe there is a messed up file somewhere in gtk/gnome settings23:53
calcbut i have no idea where to even begin looking in there23:53
brycecalc, ok will do - hang on a bit though I'm multitasking on a few things23:54
calcok np23:54
bryceyeah the xcb issue seems to be one that gets exposed via race conditions with multiple things trying to get a lock23:55
brycethat sort of thing can exhibit itself and then go away under very oddball conditions23:55
brycelike cody found that just delaying when gnome-screensaver starts up suppressed the issue23:56
cody-somervillebryce, I think it was the two dbus-launch processes attempting to launch session buses at roughly the same time.23:58
cody-somervillegnome-screensaver uses dbus and would make a dbus call resulting in dbus-launch --autolaunch because we xfce4 (whom use xscreensaver by default) has dbus-launch --sh-syntax --exit-with-session after the launch of the screensaver (and ssh-agent)23:59

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