/srv/irclogs.ubuntu.com/2009/03/20/#ubuntu-devel.txt

asac"Pixel units are relative to the resolution of the viewing device, i.e., most often a computer display. If the pixel density of the output device is very different from that of a typical computer display, the user agent should rescale pixel values. It is recommended that the reference pixel be the visual angle of one pixel on a device with a pixel density of 96dpi and a distance from the reader of an arm's length. For a nominal arm's length of 28 i00:02
slangasekasac: URL?00:03
asachttp://www.w3.org/TR/CSS21/syndata.html00:03
asac4.3.2 Lengths00:03
asacslangasek: so scaling of pixel unit seems to be explicitly encouraged00:03
asacof course we dont know how far the user is away00:04
slangasekit says to scale it to account for viewing distances00:04
slangaseknot to screw with it based on DPI00:04
asacso we scale blindly by dpi00:04
YokoZarand while we're talking about pixel values the latest updates from today seem to have made the DPI for my display even more wrong (pidgin fonts are even bigger now)00:04
asacslangasek: its a combination of distance and density from what i understand00:04
slangasek# pt: points — the points used by CSS 2.1 are equal to 1/72nd of an inch.00:05
asacso in theory we would need three profiles or somthing like:00:05
asachandheld, laptop, desktop00:05
slangasekthe spec also says that, which is the correct definition of points00:05
slangasekpitti: is bug #27622 still 'in progress' somewhere?00:06
ubottuLaunchpad bug 27622 in langpack-locales "Paper Size is wrong for locale es_CO (A4 -> Letter)" [Medium,In progress] https://launchpad.net/bugs/2762200:06
=== jdong__ is now known as jdong
=== lifeless_ is now known as lifeless
slangasekasac: yes, and I say that tampering with the definition of a pixel based on DPI is worse than doing nothing at all, because DPI is not correlated with viewing angle00:07
asacslangasek: yeah i agree. and maybe pt really does that00:07
asacbut it looked like it doesnt ... could be relative of course00:07
asaci dont have a high dpi device here to compare the real size00:08
asacbut px does definitly things based on dpi too ... not sure if thats all a bug or not ;). probably needs some discussion with the right folks00:09
=== TheMuso_ is now known as TheMuso
=== pgraner-errands is now known as pgraner
PerryArmstrongikonia; you there??01:19
directhexit's past 1am, so probably not01:21
PerryArmstrongit depends on the country where they stay...here its 7 am01:21
directhexyes, it does indeed depend on that.01:22
PerryArmstrongi just came here seing this IRC name in GSoC01:22
directhexand it's past 1am where he is01:22
TheMusoConsidering the person in question has been idling at least 11 hours, I'd say they are not currently around at a guess.01:22
PerryArmstrongthank you directhex, TheMuso for the info01:23
PerryArmstrongany discussions on GSoc01:23
PerryArmstrongi am sarching for maria who is the mentor for ubuntu in GSoC01:26
=== ampelbein is now known as Ampelbein
t3rm1n4lhow do i build cheese on ubuntu 9.0401:50
t3rm1n4l?01:50
t3rm1n4llatest cheese sources require latest gnome01:51
t3rm1n4lwhich is latest than on 9.0401:51
=== nhandler_ is now known as nhandler
=== Snova_ is now known as Snova
TheMusoslangasek: new linux-ports uploaded, no ABI bump, based on the most recent jaunty kernel upload, with the only change being the config change mentioned which was done in jaunty mainline.03:29
=== Ampelbein is now known as ampelbein
jdongkees: out of curiousity, where would we fit in on http://www.awe.com/mark/blog/200801070918.html that chart?04:25
slangasekjames_w: hrm, is bzr-builddeb known to be broken in jaunty right now?05:03
slangasekpossibly only when the upstream tarball is missing05:04
slangasekhmm, nope, broken even if I grab it05:04
james_wslangasek: not known to me05:12
macoi used bzr builddeb today just fine05:13
macoslangasek: bug 345727 is problematic for people that use both gnome & kde.05:15
ubottuLaunchpad bug 345727 in seahorse-plugins "Seahorse-agent writes an empty ~/.gnupg/gpg.conf on first run, breaking email signing in KDE" [Medium,In progress] https://launchpad.net/bugs/34572705:15
macoScottK and i talked about it, and having seahorse-agent do what gpg-agent does and just put the skeleton file in place seemed like the right thing to do. there's a branch attached to fix it. is that something to bother you about for release?05:17
maco(that bug is why i used bzr builddeb :P)05:18
slangasekjames_w: mmk, bug will be coming then05:20
maco(read today as: 2 hours ago)05:21
james_wslangasek: thanks05:21
slangasekmaco: if by 'bother me about' you mean 'upload', sure? :)05:27
macoslangasek: email said release people need to give permission before uploads happen05:27
macoso i figured id ask you (release people) before bugging someone about uploading05:28
slangasekmaco: yeah, I suppose the email does say that :)05:29
slangasekmaco: permission granted05:29
macook thanks :)05:29
slangasekHobbsee: how does having libavcodec51 installed break libavcodec52/libavformat52?05:30
macooh i can answer that: "aptitude says so"05:31
slangasekheh05:31
macoaptitude full-upgrade says i have to remove libavcodec51 so libavformat52 can be installed and then brasero is not allowed to update once that occurs05:32
slangasekwell, libavformat52 is marked Breaks: libavcodec51, and I don't understand that one either; but adding a conflicts besides seems like the wrong solution05:32
slangasekand you're sure that's not just the brasero/nautilus-cd-burner issue?05:33
macooh if theyve got an issue of their own then that could explain those two05:33
macowhen this apt process finishes, ill get it to spit out the "omg libavformat52 is gonna break things!" message again05:34
james_wslangasek: are you blocked on the bzr-builddeb bug?05:34
slangasekjames_w: nah, I used debuild instead :-P05:35
james_wexcellent05:35
james_wI shall stop torturing myself on this free wireless connection and deal with it when I return home05:35
james_wtoodle pip05:35
* slangasek waves05:35
=== foxbuntu` is now known as foxbuntu
dholbachgood morning06:07
macolong update06:34
macoanyway...aptitude says "libavformat52: Breaks: libavcodec51 but 3:0.svn20080206-12ubuntu3 is installed.06:35
maco" and then offers to remove libavcodec5106:35
slangasekthat's the right thing for it to do06:35
maco(the updater killed my net connection, no idea why it keeps doing that)06:36
slangasekand in fact, the latest ffmpeg-debian upload only causes libavcodec51 to be removed sooner06:36
macomaybe its just bcause of the brasero/nautilus but it gives a "score 270"06:37
macopresenting it as "unmet dependencies" seems like an odd way to deal with that06:38
macoi assume update-manager/do-release-upgrade would gloss over that?06:38
slangasekjames_w: bug #345747 filed against the bzr-builddeb package06:39
ubottuLaunchpad bug 345747 in bzr-builddeb "backtrace when running bzr bd --source" [Undecided,New] https://launchpad.net/bugs/34574706:39
Hobbseeslangasek: if i've got it wrong, feel free to kill that upload and upload whatever *is* the fix, and point me at it06:39
macoHobbsee: i think he's saying its doing the right thing06:40
macowe just find it ugly06:40
slangasekmaco: yes, 'unmet dependencies' is a bit odd; yes, update-manager would do something less odd06:40
slangasekHobbsee: is what maco described above the issue that you were trying to fix?06:40
Hobbseemaco: oh, aptitude offers to remove it?  I don't recall you mentioning that earlier.06:41
Hobbseeslangasek: yes06:41
macopretty sure i said that. quassel's going nuts trying to do a /lastlog though06:42
macoHobbsee: ok your memory wins. i only saw & repeated the part of aptitude's spew that says it was going to not-update brasero06:49
Hobbseemaco: oh good.  So i'm not going *entirely* mad.06:49
slangasekI'll reject the upload then06:53
Hobbseeok, cool06:54
Hydranthey all... I want to install gcc 4.4 alongside everything else on my system.... how can I do that?06:58
J-_Just an idea: http://brainstorm.ubuntu.com/idea/18694/ </spam>07:16
HobbseeJ-_: no need to spam that here as well.  Besides, jaunty's in beta freeze by now.07:16
HobbseeJ-_: and looking at that, the answer will be "Mark says no", fwiw07:16
J-_Ah okay.07:16
macoyep07:17
macothough id love if we could alt+click or ctrl+click or something07:17
macothen it wouldnt interrupt using the window behind, which is the reason they're currently not clickable07:17
crdlbmaco: but you can't accept one type of mouse input without accepting them all07:23
macocrdlb: what if it glowed when you held down the necessary modifier key?07:24
macothat'd add discoverability!07:24
=== tkamppeter_ is now known as tkamppeter
tkamppeterpitti, hi09:03
mvoevand: I have a haning partman in front of me (bug #345785) - anything I can do to resurrect it or will I have to redo the partitioning and kill ubiquity (with todays daily)09:03
ubottuLaunchpad bug 345785 in ubiquity "hangs in advanced partitioner" [Undecided,New] https://launchpad.net/bugs/34578509:03
evandmvo: can you kill it, but also when you run the installer again, can you pass ubiquity the -d flag and then attach /var/log/installer/debug to that bug report?09:07
mvoevand: sure, I will do that. I'm not sure I will be able to reproduce it again, but I will try. I paritioned back and forth (I need a complicated layout to test my free space code :)09:08
evandah, fingers crossed then :)09:09
mvoevand: *pff* now it works (I tried exactly the same steps)09:17
evandvery odd09:28
evandmvo:  have you rebooted since?  If you haven't, is there a traceback anywhere in your /var/log/installer/debug?09:30
crazybyteevand, hi. may i take a few minutes of your time?09:31
evandcrazybyte: sure09:31
mvoevand: I have not rebooted yet, but killed / restarted ubiquity (to run it with -d)09:31
mvowill that overwrite the log ?09:31
mvoevand: no Traceback, sorry09:32
evandmvo: no worries09:32
crazybyteevand, after a short discussion with janimo (i'm not sure that you know him but he recomended you) and browsering around I want to poke around and try to implement a grub-restore and some gui for grub as posted on brainstrom and janimo told me that i can ask you a bit about ubiquity09:33
crazybytei want to familiarize myself with the code and also and i'm sure that i will came up with some questions for things that i don't really understand09:35
evandcrazybyte: sure, why don't you jump in #ubuntu-installer and we can take it from there09:36
crazybyteok09:36
crazybytethank09:36
crazybytei can't right now because i'm at work and trying to figure out the cause of some very ugly bug but if later i can i will gladly. is that possible?09:37
crazybyteevand, ^^^09:37
evandsure09:38
evandif email works better for you, mine is evand@ubuntu.com09:38
crazybyteok09:38
crazybytethank you09:39
evandanytime09:39
pittislangasek: 27522 (wrong paper size) still on my list, just not very high-prio; but I'll get it done for jaunty09:45
=== azeem_ is now known as azeem
pittiasac: do you agree to slangasek that bug 310999 should have the targetted tasks removed? or closed at all?10:12
ubottuLaunchpad bug 310999 in nss "comodo seen issuing certificates unwisely" [Unknown,Confirmed] https://launchpad.net/bugs/31099910:12
pittiRiddell: do you have someone to work on bug 308060?10:31
ubottuLaunchpad bug 308060 in libmsn "Include libmsn in main" [Medium,Confirmed] https://launchpad.net/bugs/30806010:31
asacpitti: yes. thought that was already done10:31
asacjust wont fix it10:31
pittiasac: okay10:31
pittiasac: the floating task as well? or just the release tasks?10:32
asacpitti: you can keep the floating "nss" open. personally we wont do anything in the distro on our own10:32
pittiokay10:32
asacso either open or close10:32
asaci dont mind10:32
pittiokay, closing then10:33
pittithanks!10:33
pittiRiddell: if not, and libmsn is too buggy/too unmaintained, is it possible to drop the dependency?10:34
Riddellpitti: it's not buggy or unmaintained, I'm working with upstream on a patch, he commented on that bug10:36
pittiRiddell: ah, thanks10:37
pittiRiddell: final harrassment from me from today, bug 339902 seems to be in discussion upstream, so we're just waiting for them?10:39
ubottuLaunchpad bug 339902 in notify-osd "notifications visible through the screensaver" [High,Invalid] https://launchpad.net/bugs/33990210:39
Riddellpitti: right, hopefully a fix will be in 4.2.2 out shortly after beta10:41
pittigreat10:41
* pitti is a bit concerned to see the desktop team's list of RC bugs grow instead of shrink10:41
pittibut that's just because less and less "critical" bugs are put into it, not because they don't get fixed (they do)10:42
pittiso, by and large, we're in good shape10:42
* pitti -> off again10:44
* cjwatson looks at his huge pile of build failure mails, sighs, and starts digging into ports uninstallability10:59
cjwatsonlibgnome given back on sparc ia64 hppa armel, which should clear up quite a bit of uninstallability11:05
cjwatsonand libgnomekbd on hppa ia6411:09
mdzpitti: is there any simple way to query for bugs  where apport-collect was used (i.e. which were not reported originally using apport)?11:15
mdzpitti: I'm interested in seeing how much it's being used11:15
cjwatsoninfinity: phonon is going to need manual bootstrapping on hppa, assuming that the weird segfault in http://launchpadlibrarian.net/23279114/buildlog_ubuntu-jaunty-hppa.phonon_4%3A4.3.1-0ubuntu1_FAILEDTOBUILD.txt.gz doesn't happen again11:18
cjwatsoninfinity: phonon Build-Depends: libqt4-dev Depends: libqt4-webkit which is uninstallable because phonon is too old11:18
BUGabundopitti: ping11:26
BUGabundoany know bug on jaunty's jokey and nvidia?11:26
infinitycjwatson: Fun.11:27
infinitycjwatson: Oh, if you're deeply interested in failures, you might want to get a jump on https://lists.ubuntu.com/archives/ubuntu-autotest/2009-March/thread.html before I start filing bugs today...11:29
cjwatsoninfinity: interested, but probably not interested enough to beat you to it11:33
infinitycjwatson: I'll note that doko's the only person actually subscribed to that list.11:37
infinitycjwatson: Might be nice to find some folks in your team who'd be keen on actually watching it?11:37
cjwatsoninfinity: hmm, yes - can you mail me+Robbie a reminder?11:38
infinitycjwatson: When I find myself a bit more awake, sure.11:39
dokoinfinity, cjwatson: I would assume that doing rebuild tests would include filing reports for the real failures?11:39
cjwatsondoko: that was what I understood from infinity's comments above ...11:39
infinitydoko: I try to get them all filed (or even fix the really trivial ones), but more eyes (and people beating me to it) wouldn't hurt, since it really is distro's domain.11:39
dokoahh, ok11:39
cjwatsoninfinity: do you tag the autotest bug reports somehow, BTW, or make them RC, or whatever?11:40
infinitycjwatson: I target them to the current release.11:40
* cjwatson nods11:40
cjwatsonthat should be fine11:40
infinitycjwatson: And make them RC if it's a fatal, all-arches sort of failure, rather than a "gee, this doesn't work on PPC" thing.11:40
dokoinfinity: I take python-docutils, lxml and clientcookie11:41
cjwatsonpychecker looks as if it just plain hasn't been updated for 2.611:42
cjwatsonryanakca: your revision 34 in kdebindings looks wrong, and has caused python-kde4-dev to be uninstallable11:48
cjwatson+Conflicts: python-kde4 (<= 4:4.2.1-0ubuntu4)11:48
cjwatsonryanakca: shouldn't moving a file from one package to another normally be expressed using Replaces not Conflicts, anyway?11:49
MacSlowpitti, will it make sense to work on a patch (on the weekend) to fix these libgksu-glitches (http://people.ubuntu.com/~mmueller/libgksu-clearlooks.png http://people.ubuntu.com/~mmueller/libgksu-murrine.png) so GtkEntry-widgets will look like http://people.ubuntu.com/~mmueller/custom-app-clearlooks.png http://people.ubuntu.com/~mmueller/custom-app-murrine.png (note: just GtkEntry not the brushed metal bg)11:56
MacSlowpitti, will that be able to still make it to the repo?11:56
MacSlowpitti, if not I will just not do it and waste my spare time on that ... just wondering11:56
mdzmy fonts just changed with the latest updates; is that expected?12:03
ogramdz, where exactly ? i had some issues with firefox antialiasing that were fixed by a recent upload from asac12:04
mdzogra: the application font (text in xchat, menus, etc.)12:04
geserinfinity: your rebuild sbuild has that bug that the provided modules from the perl package are counted for versioned build dependencies, see https://lists.ubuntu.com/archives/ubuntu-autotest/2009-March/020856.html12:05
ograhmmm, for me it turned out that there were some links from /etc/fonts/conf.avail/ to /etc/fonts/conf.d missing, but the latest upload should have fixed that, probably it causes other fallout12:05
geserdoko: if you have time to review and sponsor: bug 34586012:05
ubottuLaunchpad bug 345860 in nevow "FTBFS in jaunty" [Undecided,New] https://launchpad.net/bugs/34586012:05
infinitygeser: Yeah.  Ignore that, I'll fix it...  Forgot to port the fix to that sbuild fork. :/12:11
ogramdz, just finished an upgrade and my fonts stayed the same12:16
asacmdz: it depends on your dpi12:19
mdzit's a "thinner" looking font12:19
asacat least if you refer to font size12:19
asacmdz: ah ... yeah. thats a change in fontconfig ... before we shipped -medium while itshould have been -slight hinting12:20
mdzasac: should have been?12:20
asacmdz: yes. thats what we default for in gnome12:20
asacso now fontconfig and gnome agree12:21
=== mcasadevall is now known as NCommander
asacmdz: the other change is that we use 13.333px for /desktop/gnome/interface/font_name ... before we had "10"; but that only makes a real difference on screens != 96 dpi12:23
nightwishsorry, we have to perform emergency maintenance on this host so it will go down now. i hope we'll be back within the next 10 minutes12:24
asacmdz: you can try to set that to "Sans 10" ... which is the value we used before12:24
cjwatsonnightwish: wrong channel?12:36
Hobbseecjwatson: or an /ame, presumably12:38
Hobbseeer, or similar12:38
nightwishcjwatson: hum?12:43
cjwatson12:24 <nightwish> sorry, we have to perform emergency maintenance on this host so it will go down now. i hope we'll be back within the next 10 minutes12:43
cody-somervillecjwatson, I think nightwish means the IRC Server is going down12:43
cjwatsonthere is no one "this host" that everyone on this channel would be using12:44
cjwatsonand there are better places for notices of IRC server outages than mentioning them in individual channels12:44
nightwisharrrgh sorry seems my irc client is buggy. this msg shouldn't go to people on freenode :/12:46
ogracjwatson, pfft, thats just because you didnt pay attention to his index finger when he said "this host"12:46
superdumpi think this may not be the right place to ask, but i was wondering whether the ffmpeg packages (ffmpeg, libav*, libswscale...) with the svn20090303 version name were taken from the 0.5 branch that we made or from trunk13:26
ScottKsiretart: ^^^13:29
superdumpoh, ok13:29
superdumpif siretart did it, i already know :)13:29
superdumpi didn't realise he managed ubuntu packages as well as debian13:29
superdumpit's good to have him hanging out in our irc channel, then we know what's going on13:29
superdumpthanks13:29
ScottKAh.13:30
cjwatsonlool: do you want an installer change to install libc6-vfp on armel?13:39
cjwatsonlool: if so, can I have something suitable for around line 564 of http://bazaar.launchpad.net/~ubuntu-core-dev/hw-detect/ubuntu/annotate/head%3A/hw-detect.sh ?13:43
cjwatsonlool: alternatively, perhaps libc6-vfp should be seeded in minimal?13:44
=== ampelbein is now known as Ampelbein
loolcjwatson: I'm happy you noticed, I don't have to tell you about NEW-ing it and selecting it in the installer then   :-)13:48
loolcjwatson: It would be welcome to install it indeed; thanks for looking into that13:49
pittimdz: apport-collect> not right now, I'm afraid; I guess I can make it add an apport-collect tag if that helps?13:49
loolcjwatson: Ok, will cook you something13:50
cjwatsonlool: I think it's probably simplest to put it in minimal, so I'll just do that. After that the hw-detect change would only be necessary if Debian wanted to have the same thing13:50
pittiMacSlow: not sure what you are asking for?13:51
loolcjwatson: It will work if you pull it in minimal; perhaps we wont need that next cycle though if we build everything vfp, in which case we'll have to think of reverting it13:51
cjwatsonright, but trivial13:51
MacSlowpitti, you saw the screenshots, right?13:51
loolYes, just mentionning it for compleness13:51
cjwatsonlool: (NEWed as well)13:51
loolthanks13:51
pittiMacSlow: I did, but my bling-untrained eye can't see what you mean13:51
MacSlowpitti, the nasty rectangle frame behind a GtkEntry-widget13:52
pittiMacSlow: since those are very different dialog13:52
pittiss13:52
MacSlowpitti, just focus on the GtkEntry-widgets in each screenshot13:52
pittiMacSlow: oh, I see13:53
pittiMacSlow: that's such a minor detail, I personally consider that more like a bug fix13:53
MacSlowpitti, you should clearly see that the ones of libgksu have nasty "non-bg-cleared" frame13:53
MacSlowpitti, so it would be accepted?!13:53
pittiMacSlow: however, somehow you need to indicate which input field has the focus?13:53
MacSlowpitti, the focus-ring is not touched by this13:53
pittiMacSlow: looks fine to me13:55
pittiMacSlow: I mean, fixing this after beta13:55
MacSlowpitti, cool ok then13:55
mdzpitti: nah, I was just curious if we could infer from the existing data13:55
pittimdz: in theory yes, but not with a simple LP search13:56
pittimdz: such a bug would have a Dependencies.txt attachment added after several comments were already made13:56
pittimdz: i. e. it can be told by looking at the activity log13:56
pittimdz: I guess it's possible to craft a custom SQL query13:57
=== Ampelbein is now known as ampelbein
=== ampelbein is now known as goodkarma
* pitti hugs mvo14:05
=== goodkarma is now known as Ampelbein
Riddelljdstrand: there's a patch on bug 308060 now, can you check if that looks like it fixes the issue you had?14:13
ubottuLaunchpad bug 308060 in libmsn "Include libmsn in main" [Medium,Confirmed] https://launchpad.net/bugs/30806014:13
jdstrandRiddell: sure14:14
Bester_Penner_foplease help with your clicks: http://change.pennergame.de/change_please/8610636/14:28
Bester_Penner_fohttp://change.pennergame.de/change_please/8610636/14:28
Bester_Penner_foplease, it is important for me!!!!!!!!!!!!!!!14:29
Bester_Penner_fohttp://change.pennergame.de/change_please/8610636/14:29
superdump:)14:29
cjwatsonbeat me to it14:29
superdumphehe14:29
ion_:-)14:29
superdumpcould still give him a ban in case he comes back14:30
superdumpdepends on your policies14:30
liwmvo, should Synaptic show the priority of a package, especially as modified by /etc/apt/preferences and pinning?14:30
cjwatsonthey usually morph before coming back14:30
superdumptrue14:30
cjwatsonI'll wait and see14:30
mvoliw: it does not currently, but it would be nice to do it14:35
liwmvo, ack; #52158 was the context, but shouldn't require attention from you rightn ow14:36
ScottKcjwatson: I can confirm the powerpc gcc bug is fixed as another package that had the same ICE as qt4-x11 just built after I retried it.14:37
cjwatsonScottK: oh good, I didn't know there was another one. What was that?14:43
ScottKkde-style-skulpture14:44
ScottKI had it on my TODO to replicate you change for that package, but just retried it instead.14:44
PecisDarbsanyone ran into such bug in jaunty - put empty cd-rw in a drive and suddenly nautilus goes mad and trying to open itself for some 5 - 7 times, crashes, and tries again14:57
PecisDarbs[   92.577853] nautilus[3962]: segfault at a346008 ip b1da755d sp b65cffc0 error 4 in libbrasero-media.so.0.1.1[b1d97000+1e000]14:58
PecisDarbsuhhh ohhhh14:58
liwmvo, looking at #76740 - I can see in the glade file that several of the dialogs are indeed missing window titles; should I add them and send you a patch (or branch to merge, whichever is easier for you)? or is it too late to fix this in jaunty?15:02
jdstrandRiddell: assuming all the length calculations are correct, then yes it looks fine. Those calculations are a bit hairy to verify, but appear correct. I wonder if it would be easier/safer to error out if c2 is larger than c1?15:05
jdstrandRiddell: that said, if this is the patch upstream wants, I have no problems15:06
Riddelljdstrand: it's not by upstream, it's by one of us, hello agateau15:06
Riddell15:05 < jdstrand> Riddell: assuming all the length calculations are correct, then yes it looks fine. Those calculations are a bit hairy to verify, but appear correct. I wonder if it would be easier/safer to error out if c2 is larger than c1?15:06
agateauhi15:08
agateaujdstrand: what do you mean with "easier/safer to error out if c2 is larger than c1?"15:08
jdstrandXMLSTR _tcscpy(XMLSTR c1, XMLCSTR c2)15:09
agateauif c2 is larger, c1 will only contains the amount of char it can hold15:09
jdstrandagateau: assuming the length calculation is correct15:09
agateaujdstrand: true15:10
jdstrandagateau: I'm not saying it isn't, I'm saying this code is a bit swirly and hard to verify :)15:10
agateaujdstrand: i see what you mean :)15:10
jdstrandagateau: not your additions, mind, just how it processes the string15:10
agateauI would have been more confident if there was some unit test15:11
agateaubut I played a bit with msntest program15:11
agateauand I have been chatting with a friend (who was surprised to find me on msn again) for an hour now15:11
jdstrandagateau: so two things could be done-- you can simply write a '\0' at the end of the string, based on your length calculation or based on your calculation, error out15:12
agateauso at least it does not introduce immediate crash15:12
agateaujdstrand: my patch does write \0 at the end15:12
jdstrandagateau: yes, I mean before that (ie, not in _tcscpy())15:13
jdstrandthen you could use strlen in tcscpy15:13
mvoliw: too late for jaunty, because of the UI freeze15:13
jdstrandagateau: that seems a bit weird though15:13
agateaujdstrand: oh, you mean write '\0' at the end of the source string?15:14
jdstrandagateau: yes15:14
liwmvo, ack, then I won't work on the patch15:14
mvoliw: but if you fix it in bzr or assign to you and tag later that would be cool15:14
agateaujdstrand: that would be less invasive indeed15:14
liw(now)15:14
jdstrandagateau: it should already be there, so there shouldn't be a problem with normal strings15:14
* agateau looks at what it would imply15:15
agateaujdstrand: the thing is: it means one has to take care of every call to _tcscpy(), and missing one call won't cause a compile error15:17
jdstrandagateau: the other option is to not change _tcscpy at all and instead treat it like strcpy(), and error out if source is longer than dest, based on your calculations15:17
jdstrandagateau: well, you are doing that anyway, aren't you?15:18
jdstrandagateau: oh I see what you mean, bec you changed it, the compiler will blow up15:18
agateaujdstrand: yes15:18
agateauand I had to propagate the changes up to where i know the buffer size15:18
apwpitti on the apport thing, i guess my point was that it all depends if there is a 1:1 correspondance from the type to the dialog or from the type to the tags15:19
apwi was seeing the type as essentially the dialog to use, and would expect us to have more than one tag possible from that type15:19
pittiapw: to both actually (well, currently anyway, since I had no reason to do it in any other way)15:19
apwright its that way right now15:19
jdstrandagateau: if you are confident that the patch introduces no regressions, I feel ok with it. the length calculation doesn't seem like it should be grossly off (if at all) and a 1 char heap overflow with jaunty's gcc protections would be very hard to exploit15:20
apwbut i was envisioning makeing the tag changable was the easiest way to fix it15:20
pittiapw: if you are happy with the dialogs, and it's just a matter of tags, then it's easy to add a "Tags" field to the report object, that launchpad.py appends to the standard tags15:20
apwi think the dialog had become changable dependant on the kernel error type anyhow15:21
agateaujdstrand: in my (limited) testing it worked ok15:21
=== Ampelbein is now known as ampelbein
apwwe might want to say use Tags in preference to main tag or something15:21
apwthough i think we already have Tags adding tags as it were15:21
agateaujdstrand: I am quite new to Ubuntu development, so I will let Riddell handle the rest15:22
pittiapw: ah, indeed15:22
pittiapw: gosh, seems apport grew too big for me to remember every impleemted detail :/15:22
jdstrandagateau: perhaps think about what we talked about for a bit, then decide how to proceed. I'll leave the regression testing in the capable hands of Riddell, you and the kde team15:23
pittiapw: so, apportcheckresume already adds that; shouldn't that suffice?15:23
apwpitti, right now we have apport-oops and resume always on suspend or hibernate bugs15:23
apwso we can tell them appart, i thought that someone other than15:24
apwus had an issue with it being -oops or something15:24
agateaujdstrand: yes, sounds wise15:24
pittiapw: seems this was a misunderstanding then; mdz might have looked at older reports which didn't tag themselves with "suspend" yet?15:24
jdstrandagateau: regarding all calls to tcscpy()-- keep in mind that tcscpy is only used by xmlParser.cpp, and libmsn just imported this file wholesale, so I think as long as you get everything in there, you would be fine.15:25
jdstrandagateau: if that is the route you choose15:25
agateaujdstrand: true15:26
mdzpitti: it is possible to tell them apart,  but it's not always convenient15:30
tkamppeterpitti, you are aware that the Apport hooks for printing do not capture the most important part due to permission issues? On all printing-related bugs I get CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log', ex: bug 34586615:30
ubottuLaunchpad bug 345866 in foomatic-db "Insufficient quoting of filenames" [Undecided,New] https://launchpad.net/bugs/34586615:30
mdzpitti/apw: you can get all of the suspend/resume bugs by looking for apport-kerneloops+suspend, but you can't get all of the non-suspend kerneloops bugs15:30
mdz(of which there will be many once kerneloops is working)15:30
pittitkamppeter: right, that's a bug in cups; we need to make the log files readable for the adm gruop15:31
apwapport-kerneloops+resume15:31
tkamppeterpitti, will this get fixed for beta, as with the beta we will probably get many testers and bug reports.15:32
pittitkamppeter: I'm not currently working on it (it doesn't even have a bug); -EOVERLOADED :(15:33
pittitkamppeter: can you please file a LP bug for it, and assign it to me?15:33
tkamppeterpitti, which package15:34
pittitkamppeter: cups15:34
loolcjwatson: I pushed libc6-vfp installation in hw-detect to lp:~ubuntu-core-dev/hw-detect/ubuntu happy if you can review it15:36
mdzslangasek: I have a pretty bad feeling about 32803515:38
cjwatsonlool: thanks, looks fine aside from the "greq" typo :-) Fixed that15:38
mdzlike it will turn out to be the heisenbug which resurfaces post-RC15:38
cjwatsonlool: I don't think this needs to be uploaded pre-beta though15:38
mdzand be an obscure kernel race condition rather than an X driver bug15:38
loolPff I suck15:38
loolcjwatson: Fixed; no certainly not needed pre beta15:39
looloh no, you pushed15:39
loolerr bzr is really confused15:40
cjwatsonyou need to use bound branches :)15:40
loolIt's fixed in bzr though15:40
cjwatsonI definitely beat you to it, bound branches wouldn't lie to me. P)15:40
cjwatson:)15:40
tkamppeterpitti, bug 34595315:41
ubottuLaunchpad bug 345953 in cups "Apport hook for printing does not capture CUPS error_log: Permission Denied" [High,Triaged] https://launchpad.net/bugs/34595315:41
loolWhat'ss weird is that I don't see your revision in my local log after a merge15:41
cjwatsonyou probably want to uncommit and pull again ...15:41
loolBut I do stand corrected and that's a point in favor of bound branches for the future15:42
pittilool: you can also rebase15:44
loolpitti: Yes, I was surprized that this actually works fine15:45
loolalbeit I had this uncommit filed I added in a checkout once, but I'm not sure whether rebase or me broke it15:45
slangasekmdz: yes, plausible that it's a kernel race; but only varying the X driver version has so far made the crashes disappear for me15:45
slangasekpitti: acpi-fakekey: it will work in the specific case that the first keyboard device that acpi-fakekey tries to open is one that happens to have that hotkey in its keymap definition :-P15:46
slangasekpitti: so yes, that's roughly equivalent to "completely broken", but on the off chance that it's not equivalent in practice, I'd rather just leave the junk there until we have it replaced15:47
pittislangasek: agreed15:47
pittislangasek: I was just curious about the state15:47
pittislangasek: a lot of those are hopefully obsolete with current kernels, but I don't know a good way to check which15:48
slangasekbuying more laptops... :)15:49
ScottKSending them to community developers for testing ....15:57
MacSlowpitti, how do I get qa-team membership as fast as possible16:03
MacSlowpitti, not being able to change the importance of bugs on the ubuntu-package of notify-osd is really hampering my triaging work16:04
davmor2MacSlow: have a word with bdmurray maybe16:05
MacSlowdavmor2, yeah speaking with bdmurray  might be best16:06
MacSlowbdmurray, can I perhaps get change-permission to alter the importance of the ubuntu-package notify-osd?16:07
MacSlowbdmurray, I'm also the upstream lead and developer of this ... and having the ability to change importance-levels for this would speed up my bug-triaging work16:08
MacSlowbdmurray, seb128 always (rightfully) complains I'm not fast enough with commenting/triaging bugs filed on notify-osd (in ubuntu)16:09
bdmurrayMacSlow: Are you familiar with apport crash reports and the private information that might be contained with in?  https://wiki.ubuntu.com/Apport16:09
MacSlowbdmurray, nope16:09
bdmurrayMacSlow: As a member of Ubuntu Bug Control you'd be able to see private bug reports that are from apport crashes and may contain sensitive data16:10
bdmurrayMacSlow: here's a better link https://wiki.ubuntu.com/Bugs/HowToTriage#Apport%20crash%20reports16:11
bdmurrayMacSlow: so once you've familiarized yourself with that since you are an upstream developer I'd be happy to add you to the team16:14
MacSlowbdmurray, ok after the call I'll read that16:16
calcwho should i contact to get my ppa quota bumped quickly? i hit the limit on my last OOo upload and it got rejected16:16
cjwatsoncalc: #launchpad16:16
calccjwatson: ok16:17
=== Pici is now known as newnick
=== newnick is now known as Pici
shayavlc seems very messed up on jaunty16:19
shayanone of the text in menus or dialogs displays correctly16:20
shayaqt issue?16:20
directhexshaya, when in doubt, blame qt/gtk bridge stuff16:43
cjwatsonlool: armel uninstallables just dropped from 201 to 62 thanks to libgnome16:58
cjwatsonI'll poke through a few other things I know about shortly16:58
clarchi16:59
clarcwould it be possible to put a new vlc version in hardy backports?16:59
=== fader is now known as fader|lunch
Lurewould just like to point to kernel panic with today update (something to look into before beta): bug 33942317:08
ubottuLaunchpad bug 339423 in update-manager "Borked installation of latest updates in jaunty, now kernel panic on boot" [Undecided,Confirmed] https://launchpad.net/bugs/33942317:08
loolcjwatson: wee!17:09
thiebaudedoes anyone know when bug 304871 will be fixed?17:10
ubottuLaunchpad bug 304871 in xserver-xorg-video-intel "[i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)" [Unknown,Confirmed] https://launchpad.net/bugs/30487117:10
mvoLure: could you please attach /var/log/apt/term.log (if you haven't alrady)?17:10
Luremvo: done that, but I did not have any apt-get issue, so I suspect problem is elsewhere17:11
* Lure thinks is it initramfs-tools or kubuntu-default-settings17:12
\shbah.../me runs into bug #32940317:13
ubottuLaunchpad bug 329403 in linux "Dont Boot After Installation on HP DL380GS" [Undecided,New] https://launchpad.net/bugs/32940317:13
macohow long does apt-listchanges --apt $package usually take to run? i'm trying to figure out if this is "normal" or if i should go report a bug17:14
cjwatsonthiebaude: it came up in the release meeting, but there's no known fix at present and upstream are not responsive17:14
cjwatsonthiebaude: so it's being tracked at the highest level, but there's no ETA yet17:14
thiebaudeok, cjwatson thanks17:14
DnaXmpt: see this https://bugs.launchpad.net/emesene/+bug/34566017:14
ubottuUbuntu bug 345660 in emesene "Emesene Libnotify plugin don't check for actions" [Wishlist,Triaged]17:14
DnaXupdate notify osd wiki page ;)17:15
mptDnaX, thanks, I saw that this morning but I didn't link to it from the spec because our preferred solution would be for emesene to integrate with the messaging menu instead17:15
\shcjwatson: looks like d-i + grub have some problems with /dev/cciss/ devices (intrepid wise)17:16
mptDnaX, we don't have docs on how to do that yet, but tedg and/or dbarth in #ayatana may be able to help you out when they're there17:16
cjwatson\sh: file a bug17:17
DnaXmpt: can you explain better "messaging menu"?17:17
\shcjwatson: someone did already bug #329403 I attached some more info files from /var/log/installer/17:17
ubottuLaunchpad bug 329403 in linux "Dont Boot After Installation on HP DL380GS" [Undecided,New] https://launchpad.net/bugs/32940317:17
cjwatson\sh: there are some known things that are fixed in jaunty, but I won't be able to tell whether your problem is one of them without checking17:17
cjwatson\sh: please do NOT attach additional information to existing installer bugs; instead, file a new bug17:18
cjwatson\sh: it is more work to untangle multiple issues from one bug than it is to mark duplicates17:18
\shok...I'll file a new one :)17:18
mptDnaX, the menu that shows up in Jaunty when you're running Evolution and/or Pidgin, and has items for each person who's messaged you recently17:18
mptDnaX, huh, from the screenshot on <http://dnax.netsons.org/rendere-emesene-compatibile-con-notify-osd> I see that the old notifications didn't let you reply etc anyway.17:20
mptoh, I see17:20
mptclicking anywhere on the bubble let you reply17:20
mptso just removing that function would be a bit of a regression17:20
johanbrDnaX: http://bugzilla.gnome.org/show_bug.cgi?id=574744 has some information17:21
ubottuGnome bug 574744 in General "Empathy could take advantage of the Messaging Indicator" [Minor,Unconfirmed]17:21
DnaXmpt: you say? uhm...17:21
DnaXi don't know how integrate emesene with fast-user-switch indicator...17:22
\shcjwatson: bug #346001 ... error is already seen in grub-.log17:24
ubottuLaunchpad bug 346001 in debian-installer "[Intrepid] HP DL36xx + Smartarray , no boot after installation " [Undecided,New] https://launchpad.net/bugs/34600117:24
cjwatsonthe error in grub.log isn't interesting, didn't need that :-)17:27
cjwatsonit's just a symptom17:27
DnaXmpt, johanbr: there is a python binding of libindicator?17:28
cjwatson\sh: oh, this is your system that thinks it's dmraid when it isn't17:30
mptDnaX, I'm sorry I don't know the technical details, you'd need to chat with tedg or davidbarth when they're back on Monday (or post to the ubuntu-desktop@ mailing list)17:31
johanbrDnaX: kind of... https://bugs.launchpad.net/indicator-applet/+bug/34383717:31
ubottuUbuntu bug 343837 in indicator-applet "libindicate needs python bindings" [Undecided,New]17:31
mptah :-/17:31
\shcjwatson: yes...but I got rid of it...now it's only the grub...and it fails also from cd17:32
DnaXjohanbr: good...17:32
cjwatson\sh: you did, but grub-installer doesn't realise you did17:32
\shcjwatson: oh...cool17:32
cjwatsonI hate dmraid17:33
DnaXmpt: so... my patch can't be accepted?17:33
\shcjwatson: any quick fix that I can try out?17:33
cjwatson\sh: wait17:33
\shcjwatson: well, it's funny..because actually it's a raid but hardware raid ;)17:33
cjwatson\sh: yeah, but it has metadata on it that dmraid thinks belongs to it17:34
cjwatsonapparently17:34
cjwatson\sh: this is a bug, of course17:34
cjwatson\sh: if you haven't already, please do file a bug on dmraid about the misdetection17:35
\shcjwatson: I can move the bug I filed to partman-dmraid or dmraid?17:35
mptDnaX, well it's a bit better than the status quo. :-) Not in Ubuntu for another week, unfortunately, because we're in beta freeze. But you could submit it upstream.17:35
cjwatson\sh: no, I already moved it to the proper place, which is grub-installer17:36
DnaXmpt: i've just submitted to upstrem ;)17:36
cjwatson\sh: the misdetection is a separate bug, which should be filed on dmraid and investigated17:36
\shcjwatson: ok..I'll file another bug :)17:36
DnaXtoo later for jaunty? :(17:37
cjwatson\sh: do you need automatic installation support here?17:37
\shcjwatson: yepp :)17:37
cjwatson\sh: netboot or CD or both?17:37
\shcjwatson: netboot17:37
cjwatsonbah, it'd have to be the hard one17:38
mptDnaX, I don't know sorry. You could try proposing it for Jaunty and see what happens.17:38
cjwatson\sh: just 8.10?17:38
\shcjwatson: jepp...or actually I could use jaunty too...17:38
\shcjwatson: I just used 8.10 because of latest stable release...we need it for tomcat crap..and intrepid is the first one with a good tomcat6 packaging17:39
cjwatson\sh: well, I'll get it fixed in jaunty, but this should do it for intrepid, I think:17:40
cjwatsond-i partman/early_command string sed -i '/^if.*dmraid/s/; then/ \&\& false; then/' /usr/bin/grub-installer17:40
cjwatson\sh: actually it'd be nice to have confirmation of that before I shove this into jaunty :-)17:40
cjwatson(I'll use a slightly more sophisticated fix in jaunty that doesn't break dmraid, of course)17:40
\shcjwatson: give me a couple of mins I'll put this in my preseed and come back to you17:41
cjwatsoncool, thanks17:42
=== fader|lunch is now known as fader
\shcjwatson: ok..installing :)17:48
\shcjwatson: btw...how can I disable apt-setup-udeb apt-setup/services-select multiselect security, which is set by default, and slows the preseed installation down, when there is no real internet connection...I tried to set it with an empty string, but it just waits there for security.ubuntu.com17:49
eeejayhey DnaX, need python bindiings for libindicate?17:51
cjwatson\sh: it must be something else that's waiting, then; setting that to empty does disable apt-setup's security generator17:51
eeejayDnaX: did you get hold of the bzr branch?17:51
cjwatson\sh: from your logs, it's a much earlier point17:52
DnaXeeejay: i'm not a python developer... but my knowledge is sufficient for a small patch :P17:53
eeejayDnaX: a small patch for what?17:53
cjwatson\sh: you could set apt-setup/security_host (and apt-setup/security_path if necessary) to a local mirror of -security, or at least to something that will fail quickly17:53
DnaXeeejay: Emesene17:54
eeejayDnaX: ah, cool.17:54
DnaXeeejay: bug #34566017:54
ubottuLaunchpad bug 345660 in emesene "Emesene Libnotify plugin don't check for actions" [Wishlist,Triaged] https://launchpad.net/bugs/34566017:54
DnaXeeejay: however I will try bzr branch17:54
\shcjwatson: it comes before the udeb loading...17:55
LordKowhey is it possible to get some pidgin 2.6.0 fixes backported to pidgin 2.5.5? it involves a memory leak.17:58
=== RainCT_ is now known as RainCT
cjwatson\sh: right, the apt-setup/security_{host,path} hacks should take care of it18:01
\shcjwatson: cool...ok..going into lab and checking installation18:01
LordKowbug 34577418:04
ubottuLaunchpad bug 345774 in pidgin "AIM buddy list unavailable window repetition" [Low,Confirmed] https://launchpad.net/bugs/34577418:04
LordKowfix available from upstream, requires a backport from their current devel branch (2.6.0).18:04
=== ampelbein is now known as Ampelbein
\shcjwatson: good news...that worked :)18:11
cjwatsongreat18:11
cjwatsonI'll get a proper fix into grub-installer18:12
\shcjwatson: cool :) and thanks for the quick fix :) now I can install some more machines in no time :)18:12
DnaXmpt: XD released https://bugs.launchpad.net/bugs/34566018:36
ubottuUbuntu bug 345660 in emesene "Emesene Libnotify plugin don't check for actions" [Wishlist,Fix released]18:36
\shcjwatson: btw...dmraid bug #346011 with reference to #34600118:36
ubottuLaunchpad bug 346011 in dmraid "dmraid recognizes raid signature on hp smartarray" [Undecided,New] https://launchpad.net/bugs/34601118:36
mptimpressive18:36
cjwatson\sh: ok, thanks18:37
\shcjwatson: anyways...thx a lot for the quick fix :) 10 new test servers installed in no time :)18:38
\shand now...weekend time :)18:38
cjwatsongood stuff18:39
cjwatsonlool: ok, I think I've now done something about almost all the armel uninstallables, and at any rate all of the ones I expect you to care about19:01
cjwatsonit'll take a few hours for all the builds to churn though19:01
ScottKcjwatson: Do you have any hints for easily figuring out why something is uninstallable on an arch one doesn't have access to?19:04
cjwatsonScottK: chdist19:04
ScottKcjwatson: Thanks.19:04
cjwatsonit's great, once you have it set up you do 'chdist apt-get jaunty-armel install <foo>'19:04
cjwatsonabsolute godsend19:04
ScottKThat sounds like what I've been looking for.19:05
cjwatsonor even build-dep rather than install19:05
ScottKFor build failures the logs are reasonably useful.  But for install failures, I hadn't found anything.19:06
cjwatsonyou still have to drill down in the usual way with apt-get, but it no longer takes an eternity of staring at the screen19:06
=== Ampelbein is now known as ampelbein
=== ampelbein is now known as Ampelbein
siretartsuperdump: in fact, the ubuntu ffmpeg packaging is even in the debian pkg-multimedia git, because that's easier fo rme19:17
=== mcasadevall is now known as NCommander
superdumpsiretart: :)19:27
slangasekpitti: interested in your opinion on bug #345531; do you think that's something we should try to get into powerdevil+gpm for jaunty, or should we restore the acpi-support bits that act on the ACPI events instead of the key events?20:00
ubottuLaunchpad bug 345531 in acpi-support "fn keys for backlight (brighness) not working : geforce 8 card on sony vaio" [Medium,Confirmed] https://launchpad.net/bugs/34553120:00
shayahas anyone tried to build vlc from source?20:04
shayait tries to run itself in the installation and fails due to running as root20:04
shayaheck, not even root as rebuilding it in fakeroot20:04
slangasekshaya: seems to be up-to-date in the archive across 8 architectures?20:07
shayathen I don't know how you build it20:07
shayafakeroot dpkg-buildpackage fails20:08
slangasekwell, not like that at least20:08
slangasek'dpkg-buildpackage' alone20:08
infinityshaya: dpkg-buildpackage -rfakeroot is what you want.20:08
shayahttp://pastebin.com/m6634164d20:08
slangasek-rfakeroot is now the default20:08
infinityshaya: "fakeroot dpkg-buildpackage" does the whole process as (fake) root.  "dpkg-buildpackage -rfakeroot" only does clean and binary-* as (fake) root.20:08
shayaok20:09
shayamakes sense I guess20:09
shayaI guess I need to get out of my old 90s methods :)20:09
shayatrying to figure out this20:11
shayathis is vlc for me20:11
shayahttp://yucs.org/~spotter/vlc.png20:11
slangasekmvo: in this update-manager change to no longer account for space for initrd .bak files, won't that potentially bite us if the kernel is upgraded before initramfs-tools on dist-upgrade, or do you already account for ordering elsewhere?20:16
slangasekmvo: (the kernel package deps don't enforce this, for sure)20:17
=== Ampelbein is now known as ampelbein
gnummhi20:44
gnummare ubuntu package maintainer here?20:44
dtchengenerally, yes, though you may find your question more succinctly addressed in #ubuntu-motu20:46
gnummok20:46
Turlhi21:01
Turlis the new splash screen final?21:01
Turlusplash, I mean21:02
slangasekto the best of my knowledge, it is21:04
Turl:S21:04
Turlit's completely unpretty21:04
=== radix` is now known as radix
slangaseksuperm1: do you know whether nvclock 0.8b4 would be appropriate to suck in from Debian for jaunty?  It appears there are some compatibility fixes there with newer hardware21:27
kklimondaanyone know what's going on with virtualenv ?21:40
kklimondai can't get it to work in jaunty with python 2.621:41
loolcjwatson: thanks a lot21:53
calcanyone know if bug 256058 is actually a bug?22:13
ubottuLaunchpad bug 256058 in freetype "Fonts not rendered correctly in OOo - Times New Roman looks bold above 13pt" [Medium,Confirmed] https://launchpad.net/bugs/25605822:13
calci can't tell if it is a hinting bug or an issue with stem width?22:13
thiebaudecalc: a couple of people were talking about extra large font like 13.322:14
calcthiebaude: this is a different issu22:15
calcthiebaude: http://launchpadlibrarian.net/21512305/bug256058.png22:15
thiebaudecalc: i see what you mean22:16
calchttp://launchpadlibrarian.net/16642799/openoffice_fonts.jpg is another example of it22:16
thiebaudeit's different bug then what i was saying22:16
calccompared between gutsy and hardy22:16
calci saw the 13.33 bug myself a few days ago22:16
thiebaudeok22:17
RainCTuhm.. isn't notify-osd supposed to pause the timer when the icon is above a bubble?22:17
RainCTah, there's a bug about it22:18
slangasekmdke: do you have moderator access on ubuntu-doc?  you might want to let through the latest notice regarding a UI freeze exception :)22:44
slangasekkees: need an MIR opinion on nvclock23:04
slangasek(an initial impression)23:04
keesslangasek: #?23:04
slangasekkees: we have smartdimmer in main, which is an old fork of some code from nvclock that's pulled in by acpi-support; it's stale and doesn't work on current nvidia-based laptops23:05
slangasekkees: no bug yet23:05
* kees fetches23:05
slangasekkees: so we can fix this bug by killing off the smartdimmer source package, merging the new upstream version of nvclock from Debian, building a new smartdimmer binary package, and yay23:06
slangaseknvclock is currently in universe, so y'all are the first stop :)23:06
keesright, reading through it now23:06
keesit has a pile of lintian warnings, but it is being maintained (updated Feb 20th).  Perhaps we could pull it before it goes into main?23:07
slangasek"pull it" --> "do the merge first"?23:08
keesyeah23:08
keesit'd be nice to clean up the lintian warnings too.23:09
ilowewhere can I read about the build process for the official livecds?23:09
slangasekcould do; requires two uploads instead of one then, since that implies not hijacking the smartdimmer binary initially23:09
slangasekbut if that's you're preference, I'll get started there23:09
iloweI found the Debian/Live project but I'm looking for the Ubuntu-specific stuff23:09
keesI think that would be a good way to go -- the more recent one closed several Debian-reported bugs.23:09
keesoh goody23:09
kees  * Update 01_fix_buffer_overflow dpatch.23:09
keesI was just going to say that the code looked a little scary23:10
slangasek:)23:10
keesin what context does this run?  as the user or as root?23:11
slangasekkees: rooty23:11
slangasektwiddling hardware, nom nom23:11
slangasekthere's no unsanitized user input to it, though23:12
slangasek(when running as root)23:12
keesyeah, was trying to make that determination23:12
slangasekit's not suid, currently nothing /at all/ invokes it by default; cf. bug #345531, asking for the smartdimmer integration to be readded to acpi-support for jaunty23:13
ubottuLaunchpad bug 345531 in acpi-support "fn keys for backlight (brighness) not working : geforce 8 card on sony vaio" [Medium,Confirmed] https://launchpad.net/bugs/34553123:13
slangasekyuck, why does that buffer_overflow patch take 122 lines to fix a single buffer overflow :P23:14
keesslangasek: yeah, I think if this got general packaging cleanups, I think it would be in a "supportable" shape.  I would +1 it after a merge, standards update, and misc fixes to get rid of the various lintian warnings.  they all look trivial, but annoying to have in main.23:14
slangasekok23:15
keesslangasek: trailing white-space updates.  ftl23:15
=== asac_ is now known as asac
slangasekkees: haha, the lintian warning about "menu-item-creates-new-section" refers to menu-policy 2.1, where nvclock-gtk is given as an example for one of the sections \o/23:26
* kees holds his face23:27
directhexhttp://farm3.static.flickr.com/2373/2048486298_2a6444b4c2.jpg ?23:32

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