/srv/irclogs.ubuntu.com/2011/04/11/#ubuntu-devel.txt

psusicjwatson, will that partman-auto fix automatically make its way into ubiquity, or does more work need done?  ( or did you already do it? )00:09
* stgraber really hates race condition ... it's been 10 boot that pub doesn't get any event00:14
stgrabercjwatson: updated bug 752393 with some more examples and thoughts. I'll change the package from lsb to plymouth as it seems to be a plymouth issue.00:31
ubottuLaunchpad bug 752393 in lsb (Ubuntu) "lsb init scripts show line buffering problems on bootup" [Medium,Confirmed] https://launchpad.net/bugs/75239300:32
cjwatsonok00:32
cjwatsonI'm going to bed shortly, will look tomorrow00:32
=== dendrobates is now known as dendro-afk
=== dendro-afk is now known as dendrobates
=== asac_ is now known as asac
cjwatsonThe archive mirrors aren't updating right now.  IS are aware02:34
=== cjwatson changed the topic of #ubuntu-devel to: Mirror updates stopped (hw problems) | Archive: Feature/UI freeze | Development of Ubuntu (not support, not app development) | #ubuntu for support and general discussion for dapper -> maverick | #ubuntu-app-devel for application development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu.com/HelpingWithBugs | Patch Pilots:
=== _LibertyZero is now known as LibertyZero
pittiGood morning07:18
cdbsGood morning pitti07:22
cdbspitti: How was your weekend?07:22
pittihey cdbs; was nice, thanks! how are you?07:26
cdbspitti: Completely fine :)07:27
abhinav-pitti: good morning. What do you think about the screenshot problem in https://bugs.launchpad.net/ubuntu/+source/apport/+bug/35784707:35
ubottuUbuntu bug 357847 in apport (Ubuntu) "ubuntu-bug wish: allow to just point at the window of a buggy application" [Wishlist,Fix released]07:35
micahg_pitti: good morning, I'm finishing up a pidgin merge, would you be able to sponsor before the freeze07:36
pittiabhinav-: sorry, what's the problem?07:37
pittimicahg_: yes, no problem07:37
pittiabhinav-: what does this have to do with screenshots? the main task there is to find out the process ID of the faulty app through the window ID?07:37
abhinav-pitti: yes, but in the comments, there was a suggestion to take screenshot as well of the window having problem07:38
pittiabhinav-: ah, so that's something different then07:39
pittiabhinav-: well, both GNOME (gnome-screenshot) and KDE have builtin screenshot capabilities07:39
abhinav-pitti: gnome-screenshot doesnt let take screenshot by pointing at a window ?07:39
pittiabhinav-: apparently not via CLI07:41
abhinav-pitti: but I suppose the solution has to be generic enough, so that it works on both KDE and GNOME ?07:43
pittiabhinav-: not necessarily; there can be a method in AbstractUI, and the Gtk/KDE/CLI implementations can then differ07:44
abhinav-pitti: right. I will look more into gnome-screenshot then. Although there is another screenshot application shutter, which provides the feature to point at a window and take screenshot. But it uses0 libgnome2-wnck-perl07:48
broderBefore I start trying to argue with people on the internet, does anybody else want to look at http://lifehacker.com/#!5790311 and confirm that e4rat shouldn't make more than a ~100ms max difference over a correctly functioning ureadahead?07:50
TheMusoOk this is weird, for some reason dput is erroring out for me saying that my public key isn't valid... but its the same key I've been using to upload packages for ages, and I've changed nothing locally or in lp.07:52
TheMusoCan anybody else confirm?07:52
StevenKTheMuso: Yes, ScottK mentioned it in #launchpad.07:52
TheMusoah ok07:53
StevenKI'm not sure what is going on yet.07:53
TheMusonp I'll jump over there to follow.07:53
TheMusothanks07:54
pittiabhinav-: shutter and its dependencies are an additional 19 MB compressed packages, which is prohibitively expensive07:54
pittiTheMuso: confrimed07:55
pittiTheMuso: it still uploads, though07:55
TheMusopitti: oh does it?07:55
pittiI pulled my hair out on that one for an hour yesterday when uploading langpacks07:55
pittiuntil I noticed that they actually work07:55
pittiTheMuso: well, it did for me. YMMV07:55
TheMusoRight, we'll see what happens.07:55
TheMusoI uploaded twice thinking something was transient. :)07:56
* TheMuso checks natty-changes.07:56
RAOFabhinav-: You can get a one-window screenshot out of gnome-screenshot, too, I'm sure.  GNOME Do appears to, at least :)07:56
pittiRAOF: you can, but it takes the currently focused window, there's no picker07:56
RAOFEh.  That's a SMOP.07:57
abhinav-pitti: the author of shutter gave me a perl script (~100 lines) which does this, but it requires libgnome2-wnck-perl :)07:57
pittiabhinav-: then you can probably do the equivalent in python with gir1.2-wnck-1.007:58
abhinav-pitti: yes, perhaps. I can try. thanks. :)08:02
pittiabhinav-: great; good luck!08:02
TheMusopitti: yeah my upload went through too.08:03
dholbachgood morning08:04
micahg_if I have a PKG_CHECK_MODULES check in configure, should the Cflags automatically get added or do I need to do something else?08:11
slangasekPKG_CHECK_MODULES() will automatically add cflags to a variable for you08:12
slangasekas long as that variable is then referenced in Makefile.in, you should be good08:12
micahg_ah, that's what I need to do, thanks :)08:12
pittimicahg_: no, they won't; you have to do something like myprogram_CFLAGS = $(MYLIB_CFLAGS)08:12
brodermicahg_: you give it a name (e.g. PKG_CHECK_MODULES([GLIB], [glib-2.0]) ) and then it defines, e.g., GLIB_CFLAGS and GLIB_LDFLAGS (or is it GLIB_LIBS? i don't remember)08:12
slangasek_LIBS iirc08:13
pitti_LIBS, yes08:13
pittiand confusingly myprogram_LDADD = $(MYLIB_LIBS)08:13
micahg_I was trying to add a proper check for launchpad integration for pidgin since the check it was under before was dropped08:13
damnohello08:16
damnoI need a bit of help08:16
damnoanyone here?08:16
pitti!ask | damno08:16
ubottudamno: Please don't ask to ask a question, simply ask the question (all on ONE line and in the channel, so that others can read and follow it easily). If anyone knows the answer they will most likely reply. :-)08:16
damnoi just compiled abiword08:17
damnosuccessfully08:17
damnobut coolab isnt orking08:17
damnosorry, collab08:17
ScottKpitti: I've uploaded KDE 4.5.5 for Maverick and filed Bug #757065 to track it.  I was hoping we could use the free buildd time once the Beta 2 freeze solidifies a bit to get it out the door.08:17
ubottuLaunchpad bug 757065 in oxygen-icons (Ubuntu) "Tracking bug for SRU update of KDE to 4.5.5 in Maverick" [Undecided,New] https://launchpad.net/bugs/75706508:18
pittiScottK: that sounds like a good opportunity indeed; I would like to wait a bit still, as the buildds are still quite busy, and I expect some more last-minute uploads08:18
ScottKpitti: Certainly.  I was guessing likely tomorrow.08:18
damnothe install process created a archive named 'backup-041120111230-pre-abiword.tgz'. is it essencial to keep it?08:19
ScottKThe core packages are all there.  I don't have the translation updates yet.08:19
ScottKNo need to particularly wait on those though.08:19
pittimeh, Launchpad's "I hate your key" messages are really confusing08:20
StevenKpitti: Currently being investigated.08:20
StevenKBut yes, it's exposing internals in an ugly way.08:21
TheMusoYes, and prevents dput uploading multiple packages simultaneously.08:21
TheMusoSince an error is being thrown.08:21
ScottKYes.  Yes it does.08:21
TheMusoScottK: Oh yeah, that would have been painful.08:22
pittiScottK: ok if I upload a new kubuntu-restricted-addons to drop the NBS kopete-gcall?08:22
damnoyou guys are too busy to help a new guy ,  I think08:22
damnobuy08:22
ScottKpitti: Certainly.08:22
=== smb` is now known as smb
micahg_pitti: in the interest of getting this done, would it be ok to attach the launchpad integration check onto something else (like glib), I can't seem to get this to work08:41
micahg_it was previously attached to startup notification08:41
pittimicahg_: so perhaps just leave it where it was before, on startup-notification?08:41
micahg_pitti: would have loved to do that, but that check was removed in 2.7.11 :)08:42
micahg_hi seb128, since you've done most of the pidgin merges, do you have an opinion about the above?  (4 lines)08:48
=== hunger_ is now known as hunger
seb128just put it on whatever is used to build that part of the code08:49
micahg_ok08:49
\shhmm...did anyone see this error lately on natty while uploading? http://paste.ubuntu.com/592510/08:53
lifelessyes08:54
lifelessits being fixed08:54
lifelessgpg.conf file got reaped by tmpreaper08:54
\shlifeless: means?08:54
\shlifeless: error on user side or on server side?08:55
lifelessserver side08:55
lifelessworkaround is in place if you want to try again08:55
\shlifeless: ok...so I don't care, actually the package was accepted08:56
TheMusohrm, alsa-lib on amd64 failed for some weird reason. I386 built fine. http://paste.ubuntu.com/592512/08:57
TheMusoThis is on the buildds.08:57
diwicTheMuso, yeah, saw that as well. "gcc: not found" seems to be the error08:57
* micahg_ thinks slangasek was talking about that earlier08:58
TheMusoOk thanks.08:58
apwthere is an incantation (possibly as tasksel one) including a ^ which says 'install everything i would expect to have installed'09:00
apwcan anyone remind me what it is?09:00
pittiapw: that's called installing a task09:00
pittiapw: apt-get install ubuntu-desktop^ should do that09:00
apwpitti, ahh that looks like it ... thanks :)09:01
pittihey apw09:01
apwpitti, hiya09:01
micahg_seb128: for the new symbols, do you just copy them from Debian and add an epoch?09:04
slangasekTheMuso, micahg_: no, I was talking about a change that's in a linux-libc-dev version that isn't published yet09:07
TheMusohrm ok thanks.09:07
seb128micahg_, yes09:11
slangasekTheMuso, micahg_: oh oops, I read the output wrong - yes, linux-libc-dev is published on amd64, so that explains perfectly the failure09:13
TheMusoslangasek: ok thanks.09:15
micahg_seb128: do we care about sort order?09:15
seb128no09:15
micahg_seb128: thanks09:15
micahg_pitti: bug 757146 if you have time to sponsor09:29
ubottuLaunchpad bug 757146 in pidgin (Ubuntu) "Please merge pidgin 2.7.11-1 (main) from Debian unstable (main)" [Wishlist,Confirmed] https://launchpad.net/bugs/75714609:29
slangasekTheMuso: verified that gcc-multilib 4:4.5.2-1ubuntu2 will fix this; as soon as that publishes we can retry alsa-lib09:30
TheMusoslangasek: Thanks.09:30
pittimicahg_: on it09:33
micahg_pitti: thanks09:33
JamesMRHi, I'm looking for some help/advice with an error I'm getting when trying to use apt, this is the error - "dpkg: syntax error in file triggers file `/var/lib/dpkg/triggers//File'" I'm on 10.10, it started appearing after trying to update to 11.04 beta via update-manager -d and my system froze partway through. 11 hours later I decded to rebooot my computer, the error has been bugging me since09:46
poolieJamesMR, try in #ubuntu09:48
poolieor rather, #ubuntu+109:48
micahg_pitti: did you upload pidgin yet? (if not, hold off)09:48
pittimicahg_: too late09:48
poolieclint's in a us timezone, right?09:49
pooliei wanted to push along https://bugs.launchpad.net/ubuntu/+source/bzr/+bug/70707509:49
ubottuUbuntu bug 707075 in bzr (Ubuntu Lucid) "[sru] lp-propose fails with a 404 error" [Undecided,New]09:49
micahg_ugh, I built this thing multiple times, and the last time it tells me symbols are missing09:49
TheMusoheh09:50
* micahg_ wonders if -j17 had anything to do with it09:56
micahg_pitti: I think I'll have a fixed pidgin in a few minutes, it seems if a symbol is listed twice it fails now10:09
* micahg_ is confused, not all the duplicates failed10:12
micahg_ok, so there's something I don't understand, can the same symbol appear multiple times in a file?10:26
slangasekmicahg_: the same symbol /name/ can, but only if it has a different symbol version AFAIK10:26
micahg_slangasek: ok, so these are all the same version10:28
micahg_can I safely remove one?10:28
slangaseksorry, maybe I'm confused - are you talking about removing it from a symbols file or from a library?10:29
micahg_symbols file10:29
slangasekah, I thought you were talking about an object file.  Sorry, I'm not sure I know the answer then10:29
sorenmicahg_: Which package?10:31
micahg_soren: pidgin10:32
sorenI probably don't know the answer, I'm just curious :)10:32
micahg_heh10:33
micahg_I'm rebuilding without the duplicate symbols which I expect to succeed locally, I just would like to know if it's safe for the archive10:33
soren"bzr branch lp:ubuntu/pidgin" takes a while...10:34
micahg_soren: try pull-lp-source pidgin :)10:34
sorennot a bad idea10:35
sorenlibpurple0.symbols?10:35
micahg_soren: yep10:35
micahg_so Debian removed the symbols, I'm just not sure why, it also wasn't noted in their changelog, but they're duplicates, so idk if that means anything was removed or not10:37
micahg_pitti: so, the build succeeded w/out the duplicate symbols, but idk if that's the right thing to do or not10:44
pittimicahg_: duplicate *.symbol entries don't really make sense, so this sounds like the right solution10:44
sorenWell, this particular symbols file has information for two separate libraries.10:45
sorenlibpurple.so.0 and libpurple-client.so.010:45
micahg_ah10:45
sorenThey could both export the same symbol.10:45
sorenWhether they actually *do*... I don't know.10:45
sorenI can imagine situations where it makes sense, but I have no idea if that applies here.10:46
=== doko_ is now known as doko
sorenSay, if the same binary package ships two flavours of the same library, both exporting (mostly) the same symbols.10:46
sorenNow that I've added to the confusion, I'll wander off. Toodles :)10:47
micahg_pitti: so, they're not duplicates, it's as soren suggested, they are gone from libpurple-client and now solely in libpurple10:48
sorenWithout a soname bump?10:49
soren*sob*10:49
sorenOh, right I wandered off.10:49
* micahg_ doesn't think the pidgin devs know what the so version is for, it seems to be tied to their dev version instead of soname changes10:51
micahg_or it could just be coincidence10:52
micahg_pitti: so, options are, upload an ubuntu2 that follows what Debian did (remove symbols w/out soname bump) or upload a 2.7.9-2 version and try to get this fixed properly11:03
pittimicahg_: I think just removing the duplicates from libpurple-client will do11:04
pittiat most it'll affect library dependency versions, but they should already be alright with the other symbols11:04
micahg_pitti: ok, I'll attach the debdiff11:04
TheMuso...i thought freeze was at 9:00UTC.11:07
pittiTheMuso: yes, freezing right now; the higher priority for the admins was to get the archive mirrors back working :)11:08
=== cjwatson changed the topic of #ubuntu-devel to: Archive: Feature/UI freeze | Development of Ubuntu (not support, not app development) | #ubuntu for support and general discussion for dapper -> maverick | #ubuntu-app-devel for application development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu.com/HelpingWithBugs | Patch Pilots:
TheMusoright11:08
cjwatson(mirrors should return shortly)11:08
micahg_pitti: bug 757311, thanks11:10
ubottuLaunchpad bug 757311 in pidgin (Ubuntu) "pidgin fails to build due to missing symbols" [High,In progress] https://launchpad.net/bugs/75731111:10
pittimicahg_: cheers, uploaded11:11
micahg_pitti: thanks, sorry for all the trouble :)11:12
pittimicahg_: no worries, thanks to you for sorting it out!11:12
=== pitti changed the topic of #ubuntu-devel to: Archive: Beta-2/Feature/UI freeze | Development of Ubuntu (not support, not app development) | #ubuntu for support and general discussion for dapper -> maverick | #ubuntu-app-devel for application development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu.com/HelpingWithBugs | Patch Pilots:
pittiarchive now frozen for beta-211:14
* ogra_ curses this insane freeze time 11:17
pitti?11:17
ogra_we shouldnt do freezes on monday mornings11:17
ogra_that kind of forces people into weekend work11:17
ogra_either have them in the evening or on the friday before11:18
pittithe main difference is that the release team cross-checks the uploads; little difference for developers11:18
ogra_i know :)11:18
pittiogra_: how would a freeze on Friday help in any way?11:18
cjwatsonwell, I sympathise with the weekend work bit, but how would moving it help?  if you haven't got the work done yet, you haven't got it done, and moving the freeze would make little difference11:18
pittiif you don't work on the weekend, fri/mon morning freeze is no different11:18
ogra_if you have work to do that requires less than a day you dont have to work on the weekends to make it into the archive before freeze11:19
ogra_if the freeze is in the evening or afternoon UTC11:19
cjwatsonmoving it later, sure; however that does have other consequences for the release team11:19
pittiogra_: you can still do that; freeze -> controlled what's going in, not "doors firmly closed"11:20
pittiwe already have negotiated an exception for unity11:20
cjwatsonthe later it is, the higher the chances of Tuesday's daily builds not being usable and us having to scramble11:20
pittibut we really need to coordinate uploads, to not collide with image builds, QA smoke testing, etc.11:20
ogra_i know, i also have discussed the possible alsa and pulse changes with kate11:20
cjwatsonin private or in channel/bug?11:20
ogra_but i still would like to give the community more time before we freeze11:20
ogra_cjwatson, during fridays meeting11:21
cjwatsonok11:21
mdzpitti, is the amd64 retracer possibly down or backlogged? bug 757219 has been pending for 3 hours so far11:36
ubottuError: Launchpad bug 757219 could not be found11:36
pittimdz: it was, but the log was empty; I restarted it for now11:36
seb128pitti, I've restarted it 2 times already today11:40
pittiseb128: and it doesn't produce any log?11:40
seb128it does "consolidating the duplicates" and seem to crash11:40
pittiah, log_dupcheck11:40
seb128or never went over that11:40
seb128pitti, well there is nothing in the logs, I guess I should try to run it manually11:41
pittisladen: your ubuntu-mono upload dropped --with-scour, but doesn't document why?11:45
sladenpitti: oh bollocks, could swear I did  bzr revert debian/rules  first11:46
pittisladen: want me to reject and you reupload?11:46
pitti(same version number is fine)11:46
sladenpitti: yes11:46
sladenpitti: I just do that to save 20 minutes on the local build time11:47
pittiquite a large set of new icons as well, I hope they got some testing?11:47
sladenpitti: urm?  Should only be 1.  But a lot of symlinks/alternate names11:48
pittisladen: ah, then debdiff just got confused :011:48
sladenpitti: it's overriding one icon (and all of its aliases) from Humanity, as Humanity maintainers/upstream don't want the icon that Mark wants, but Humanity upstream (vish) is being kind enough to ensure it correctly goes into ubuntu-mono as a mutal solution :)11:49
sladenpitti: weird.  debian/rules  has --with-scour,  and bzr status shows nothing11:51
pittisladen: maybe you had an older source package around?11:51
dokopitti: do you intend to address all the other v4l issues too?11:51
pittidoko: so far I am aware of gambas (which built locally, but not on the buildds, sorry), and hal, but both are fixed now11:52
pittidoko: what else?11:52
pittiI'm mainly fixing NBS right now, but can look into other issues if required11:52
dokopitti: https://launchpad.net/ubuntu/+bugs?field.tag=ftbfs+natty+v4l&field.tags_combinator=ALL11:56
=== MacSlow is now known as MacSlow|lunch
* pitti sighs on timeout11:57
pittidoko: if you happen to have the page open, perhaps you can toss me a bug list on IRC?11:58
pittitried 5 times now11:58
dokopitti: http://paste.ubuntu.com/592569/11:59
chrisccoulsonnobody noticed any new firefox issues since i turned on -pie in the builds again last night?12:00
pittichrisccoulson: hardly, as the mirrors are still not updated :)12:01
chrisccoulsonah12:01
chrisccoulsonthat's not good ;)12:01
pittidoko: any priorities there? I can do two or three, but not 2512:01
dokoenoclue, I just filed these with the tag, because it's obvious from the build logs12:02
lamontScottK: "fond" isn't exactly the word I would use12:07
pittidoko: I'll grab linphone, vdr, and kino then, they seem to be the most popular12:08
pittidoko: ah, linphone already fixed12:08
dokoyeah, sorry, I may have filed issues for superseded versions12:09
pittiah, no, LP output is just confusing12:09
pittiit went to universe, that's why it shows published on Apr 812:09
pittiso yeah, will have a look at these three12:09
=== yofel_ is now known as yfoel
=== yfoel is now known as yofel
janimowhat is the procedure for freeze exception uploads?12:55
arandI wonder if there is a...12:55
arand!ffe12:55
ubottuFeature Freeze Exception. See https://wiki.ubuntu.com/FreezeExceptionProcess for the freeze exception process.12:55
janimoarand, thanks12:59
ogra_janimo, adding features ?12:59
=== claudinux is now known as Claudinux
janimoogra_, nope, hopefully fixing the gconftool crash13:02
janimoworking around actually by building with -O0 :(13:03
ogra_well, just have a bug for it and mention the bug number in the changelog will suffice13:03
ogra_bugfixes that dont add new features dont need an FFE13:03
ogra_just upload and be in #ubuntu-release if the reviewer has questions13:03
ogra_(all uploads get reviewed anyway from now on)13:04
janimoogra_, ok, just joined that channel13:04
ogra_makes sense prior to milestones and during freezes13:04
ScottKlamont: Speaking of stuff you're fond of ...  What are the chances of fpc on armel bootstrapping this cycle?13:09
lamontwell, I did say I'd see about throwing it against the wall again to see if this time is any different than the last 3 times13:09
ScottKOK.13:10
lamontof course, if it does bootstrap, it'll just fail to run on most of the buildds, I'm guessing13:11
=== MacSlow|lunch is now known as MacSlow
=== chuck_ is now known as zul
=== Quintasan_ is now known as Quintasan
mdzseb128, any luck with the retracer?14:04
seb128mdz, the amd64 is running14:04
mdzseb128, great, I guess it will catch up soon then14:05
seb128mdz, but there is quite some backlog from the weekend so it might take another hour before getting yours14:05
mdzack14:05
seb128pitti, I disabled the job which consolidates the db for now to get the retracing going btw14:05
seb128pitti, I will try to restart it manually once we clear the backlog14:06
pittiseb128: ah, thanks14:06
=== bregma_ is now known as bregma
bdrunggeser: DMB meeting?14:27
pittidoko: FYI, I uploaded linphone and kino fixes, and will do a vdr sync after the buildd backlog settled down; then these three are fixed14:31
=== dendrobates is now known as dendro-afk
=== diwic is now known as diwic_afk
GunnarHjdoko: Hi Matthias, there is a rumor that you're patch pilot today. ;-)14:49
=== sconklin-gone is now known as sconklin
=== kentb_ is now known as kentb_dell
=== kentb_dell is now known as kentb
=== kentb is now known as ubuntu-touch
=== ubuntu-touch is now known as kentb
=== Claudinux_ is now known as Claudinux
=== jjohansen is now known as jj-afk
=== hggdh_ is now known as hggdh
kirkland@pilot in15:17
=== udevbot changed the topic of #ubuntu-devel to: Archive: Beta-2/Feature/UI freeze | Development of Ubuntu (not support, not app development) | #ubuntu for support and general discussion for dapper -> maverick | #ubuntu-app-devel for application development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu.com/HelpingWithBugs | Patch Pilots: kirkland
kirklandGunnarHj: hi, i'm on pilot duty, too, fwiw15:18
GunnarHjkirkland: Hi Dustin, it's worth a lot. :)15:21
GunnarHjkirkland: There are two things I'd appreciate your help with. First I'm wondering if it's possible to commit only one of the revisions (322) from https://code.launchpad.net/~gunnarhj/gdm/profile/+merge/56426, or should I create a separate MP for it? (Rev. 323 is pending furter discussion.)15:21
kirklandGunnarHj: reading ...15:21
kirklandGunnarHj: hmm, I echo seb128's question ... you should easily be able to: . $HOME/.profile || true15:25
kirklandGunnarHj: and . $HOME/.xprofile || true15:25
apwcjwatson, about?  seeing any reports of loss of graphical boot?  my first test box i updated seems to go from purple to black with a cursor ?15:27
GunnarHjkirkland: Think I have to test it again, to recall why I made another conclusion...15:27
kirklandGunnarHj: so if you just do:15:27
kirklandGuest24406: . $HOME/.profile || true15:28
kirklandGunnarHj: the || true will catch the error that you're testing for with -f (file existence)15:28
kirklandGunnarHj: and it will also catch any syntax errors in the sourcing of that file15:28
GunnarHjkirkland: Will get back to you about that.15:29
GunnarHjkirkland: Then there is https://code.launchpad.net/~gunnarhj/language-selector/help/+merge/57109. Is a pure docs change affected by BetaFreeze?15:30
apwcjwatson, a quick poke seems to imply that linux_gfx_mode is not keep, ie changing the set to keep gets it back15:30
kirklandGunnarHj: https://wiki.ubuntu.com/DocumentationStringFreeze15:31
cjwatsonapw: first I've heard of it15:32
apwcjwatson, i don't see to have a gfxblacklist.cfg15:32
apwcjwatson, i don't see to have a gfxblacklist.txt even15:32
cjwatsonapw: do you have /boot/grub/gfxblacklist.txt?15:32
GunnarHjkirkland: I know, but that document is not subject to translation yet (won't be until after the Natty release).15:32
cjwatsonhm, maybe it falls over if that file's missing15:32
apwcjwatson, nope no such file15:33
kirklandGunnarHj: ah15:33
apwand dpkg can't find one either15:33
kirklandGunnarHj: okay, then i'm willing to sponsor that one, if you open a bug for it15:33
apwcjwatson, isn't that file from its own  package ?15:33
apwcjwatson, this machine just has had an apt-get install ubuntu-desktop^ run on it too, so its in theory complete15:34
cjwatsonno, it's from grub-gfxpayload-lists, which I forgot to MIR (doing now)15:34
cjwatsonbut grub should tolerate its absence anyway15:34
cjwatsonbug me15:35
apwcjwatson, welll in theory it might be the right behavour in the absense of the file ...15:35
cjwatsonI think on balance I'd rather default on15:36
apwcjwatson, ok touching that in seems to fix the issue15:37
apwcjwatson, i assume you want a bug against grub2 ?15:37
cjwatsonyes15:37
apwcjwatson, also  ... i have a feeling that something other than drm is switching off the display, contributing to the length of the 'black with no backlight' phase15:37
apwdoes that ring a bell at all ?15:37
apwplymouthd when it starts or something?15:38
kirklandGunnarHj: can you get me a bug number for the language-selector fix?15:39
cjwatsonapw: no bells ringing there15:40
GunnarHjkirkland: Sure, just give me two minutes.15:40
apwcjwatson, bug #757603, want it assigned ?15:41
ubottuLaunchpad bug 757603 in grub2 (Ubuntu) "graphical boot is disabled when the gfxblacklist.txt is missing" [Undecided,New] https://launchpad.net/bugs/75760315:41
cjwatsonI'll grab it15:41
apwack15:42
GunnarHjkirkland: Done. Used an ongoing bug on i18n documentation.15:43
=== jono_ is now known as jono
pittidoko, mterry, didrocks: we have two urgent MIRs for beta-2, bug 754661 and bug 757600; does any of you have some time to review them?15:52
ubottuLaunchpad bug 754661 in python-psutil (Ubuntu Natty) "[FFe] [MIR] python-psutil" [High,Confirmed] https://launchpad.net/bugs/75466115:52
ubottuLaunchpad bug 757600 in grub-gfxpayload-lists (Ubuntu) "[MIR] grub-gfxpayload-lists" [Undecided,New] https://launchpad.net/bugs/75760015:52
mterrypitti, sure15:52
* mterry takes first, will take second if no one else does15:52
pittimterry: cheers15:52
* didrocks still triages unitish things15:58
didrockskees: answered on bug #755146, can you please have a look once you have time for it?15:59
ubottuLaunchpad bug 755146 in compiz (Ubuntu) "compiz crashed with SIGSEGV in g_source_unref() (dup-of: 740897)" [Undecided,New] https://launchpad.net/bugs/75514615:59
ubottuLaunchpad bug 740897 in compiz (Ubuntu) "compiz crashed with SIGSEGV in g_source_unref()" [Medium,Confirmed] https://launchpad.net/bugs/74089715:59
seb128didrocks, njpatel suggested that's a duplicate of the ccsm crash earlier16:01
didrocksseb128: ok, let's hope so :) weird that we still have a missing unref in sources, I checked everything apart from the dash, will have another look16:03
seb128kees, did you get your compiz crashes when using ccsm?16:03
kirklandGunnarHj: #?16:04
stgraberSpamapS: ping16:05
GunnarHjkirkland: Sorry, bug 74285716:05
ubottuLaunchpad bug 742857 in language-selector (Ubuntu) "i18n matters ought to be properly documented" [Undecided,In progress] https://launchpad.net/bugs/74285716:05
didrocksseb128: from the ubuntu-devel mailing list: " crashed when clicking launcher for Terminator while Terminators were running"16:07
kirklandGunnarHj: cool, pushed, uploaded16:08
kirklandGunnarHj: let me know about the gdm one16:08
seb128didrocks, ok so maybe njpatel was wrong ;-)16:09
didrocksseb128: that's why I'm pinging kees :-)16:09
didrocksseb128: well, the issue will also result in ccsm being uncheck16:09
GunnarHjkirkland: Thanks. I will (in a few minutes).16:10
GunnarHjkirkland: Please see my latest comment on https://code.launchpad.net/~gunnarhj/gdm/profile/+merge/5642616:25
mterrycjwatson, about grub-gfxpayload-lists, I don't see any existing blacklisted IDs and it doesn't seem to install a dpkg trigger, so is this package currently a no-op?16:31
cjwatsonmterry: tseliot was thinking of adding entries to fglrx/nvidia packages, although I'm not sure whether he actually has yet16:33
cjwatsonmterry: rightly or wrongly (perhaps wrongly) the current design is that packages that install blacklist files should call update-grub-gfxpayload16:33
cjwatson(I wouldn't mind a bug to triggerise that, although I don't think it's necessary for natty)16:34
mterrycjwatson, sure, OK.16:34
tseliotcjwatson, mterry: both fglrx and nvidia-current install such blacklist file (currently empty though)16:34
cjwatsonright - I want to have the facility in place though16:34
mterrypitti, both approved16:40
pittimterry: thanks16:41
dholbachhttps://wiki.ubuntu.com/UbuntuAppDeveloperWeek starting in 15 minutes in #ubuntu-classroom16:46
abhinav-dholbach: will the IRC logs be available ?16:49
sladenabhinav-: irclogs.ubuntu.com16:49
james_wcjwatson, Can't exec "unxz": No such file or directory at /usr/share/perl5/Dpkg/IPC.pm line 261. <- That's from the xz work I assume? It implies that the updated dpkg is installed, but an xz package is missing?16:50
dholbachabhinav-, yes, they'll be also put on https://wiki.ubuntu.com/UbuntuAppDeveloperWeek afterwards16:50
abhinav-dholbach: cool. Thanks :)16:50
seb128mdz, your bug got retracers, it's an overlay scrollbar issue16:53
mdzseb128, thanks. when apport filed it, it was tagged ayatana-scrollbar (before even being retraced), but was still filed on rhythmbox for some reason16:54
mdzis that how it's supposed to work?16:54
seb128mdz, the tag just means that the scrollbar binary is installed16:54
mdzoh16:54
seb128it doesn't mean the bug is due to those16:54
cjwatsonjames_w: is that on a DC machine?16:55
mdzI thought it might have been because of ?? () from /usr/lib/liboverlay-scrollbar-0.1.so.016:55
james_wcjwatson, yeah, jubany16:55
mdzbut that makes more sense16:55
cjwatsonjames_w: current versions of dpkg pre-depend on xz-utils16:55
mdzseb128, isn't the scrollbar binary package installed by default though?16:55
seb128mdz, right, I need to talk to ken about that16:55
cjwatsonjames_w: one of the versions floating around the -cat archives might be suitable for jubany; I'd suggest asking IS16:55
seb128mdz, we should add something to reassign to overlay-scrollbar if liboverlay-scrollbar is in the stacktrace16:56
james_wcjwatson, ok, thanks16:56
mdzseb128, yeah, similar to the nautilus->ubuntuone rule16:56
seb128mdz, well in fact I just checked I was wrong, it does add the tag if the scrollbars are in the ProcMaps, but it just tell you that the application which crashed had those loaded16:57
seb128not that it crashed in there16:57
mdzah16:57
=== deryck is now known as deryck[lunch]
keesdidrocks, seb128: I have no idea where the 755146 crash came from, honestly. the other one (755167) was totally a crash while in ccsm.17:11
didrockskees: ok, so "known and prioritized issue"17:11
keesdidrocks: cool, thanks!17:12
keesdidrocks: after turning off focus-follows-mouse, I have had 0 more problems.17:12
=== herton is now known as herton_lunch
keesI don't like not using FFM, but it does keep me from having unity crash :)17:12
didrockskees: yeah, ffm is not supported from the start :/17:12
keesdidrocks: if that's the case, unity should refuse to run if FFM is on. ;)17:13
didrockskees: there were a discussion about this 2 monthes ago, but some people argued it was working, so we didn't touch it17:13
keesdidrocks: does the unity (or compiz) apport hook report the state of FFM?17:15
didrockskees: no, and yes, nice suggestion :)17:18
didrockskees: I'll add that17:18
didrocksthanks :)17:19
keesdidrocks: cool; that should really help weed out stuff17:19
didrocksright17:20
=== JasonO_ is now known as JasonO
kirklandGunnarHj: okay, another message, back at you ;-)17:22
SpamapSstgraber: pong, I read your analysis of the console issue. Makes sense to me.17:28
stgraberSpamapS: can you post the boot.log file after you switch to that lsb-base-logging.sh ? assuming you still have the VM around17:35
SpamapSstgraber: I do (I have 2 like it actually). Booting them now. :)17:37
stgraberSpamapS: cool, thanks17:38
=== beuno is now known as beuno-lunch
GunnarHjkirkland: That's indeed more elegant than my function. :)17:42
GunnarHjkirkland: Just a detail: Can't we drop the "|| true" part then? To me it appears to be superfluous. Or what am I missing?17:42
kirklandGunnarHj: no, that part is essential to catch the (. ~/.profile) failure17:42
=== jj-afk is now known as jjohansen
=== herton_lunch is now known as herton
kirklandGunnarHj: wanna update that merge?17:52
GunnarHjkirkland: Yes, I'll do that. But let's first finish the "|| true" talk. Just submitted a new comment on https://code.launchpad.net/~gunnarhj/gdm/profile/+merge/5642617:55
GunnarHjkirkland: To me it appears as if the parentheses protect the main process from stopping irrespective of what you put inside them.17:57
=== sforshee is now known as sforshee-lunch
kirklandGunnarHj: interesting, it does seem that way to me18:01
SpamapSstgraber: boot.log uattached18:01
kirklandGunnarHj: my tests agree with that18:02
=== dendro-afk is now known as dendrobates
stgraberSpamapS: thanks. I'm currently working on fixing the apparmor part of it, it's calling a function I didn't make plymouth aware yet. Fixing this one should give a slightly better output.18:06
stgraberSpamapS: for memcached that's probably as good as it's going to be until someone changes its init script18:07
GunnarHjkirkland: Ok, then I'll update the merge and get back to you.18:09
kirklandGunnarHj: perfect18:10
kirklandsmoser: looking at https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/72657218:11
ubottuUbuntu bug 726572 in cloud-initramfs-tools (Ubuntu Natty) "[MIR] cloud-initramfs-tools" [Undecided,In progress]18:11
kirklandsmoser: looks like kees gave you your +1 for MIR18:11
kirklandsmoser: nice ;-)18:11
kirklandsmoser: i'll move it over18:12
smoseryeah, can you commit it to seed ?18:12
smoserseed "uec"18:12
smoserand, kirkland, thank you for doing work for me :)18:12
kirklandsmoser: sure18:13
kirklandsmoser: you do work for me all the time;  it's the least I can do :-)18:13
=== JasonO_ is now known as JasonO
SpamapSstgraber: are the lsb log messages completely suppressed?18:17
SpamapSstgraber: I don't see any calls to plymouth update18:18
=== deryck[lunch] is now known as deryck
stgraberSpamapS: nope, they still go through the console as usual, it's just that instead of showing the first half of the message, then wait and show the "[ OK ]" part, I wait until I know if it worked or failed to show the whole line18:19
stgraberthe problem with apparmor is that it's calling log_action_msg which does a simple "echo" so it gets printed immediately and so appears before the line saying that apparmor is starting :)18:20
stgraberwhich makes sense because that line is technically printed before the call to log_end_msg, it just looks weird ...18:21
kirklandsmoser: done18:21
stgraberSpamapS: plymouth is basically grabbing everything that gets displayed on the console and writes that in boot.log. So you just need to be careful to always echo full lines to the console.18:25
ScottKkirkland: If you're still patch piloting, I'd appreciate it if you would look at Bug #757540.18:30
ubottuLaunchpad bug 757540 in ttf-kacst-one (Ubuntu) "Missing many Glyphs to support Uyghur (Uighur) Language" [Undecided,In progress] https://launchpad.net/bugs/75754018:30
kirklandsconklin: sure18:30
kirklandScottK: ^18:30
ScottKThanks.18:30
kirklandScottK: i'm tackling a likewise-open double merge at the moment, will look at yours next18:31
ScottKkirkland: Thanks.18:31
=== dpm_ is now known as dpm
superm1janimo, i wasn't even aware that you had uploaded deltas to mythtv until ScottK pointed it out.  could you try to remember to submit a merge request for the VCS next time so it's not missed?18:35
janimosuperm1, I thought maintainers are notified on upload18:36
janimosuperm1, I almost never notify debian or upstream vcs explicitley unless it is a bugreport18:36
superm1i didn't see anything come through my mail about it, hm wonder why18:36
superm1the maintainer is a mailing list, is that maybe why?18:37
janimofor are there are changes to amany7 packagesa and explicitly doing that for each is a lot less efficient than relying on the fact that LP mails out notifications18:37
janimosuperm1, not sure why, maybe not all maintainers are notified by LP. Failing that I thought package updates even syncs from Debian do not go over ubuntuX changes without at least some notification that there is an ubuntu delta18:39
janimos/for are/for ARM/18:39
=== beuno-lunch is now known as beuno
superm1for this particular package it's not in debian18:40
micahg_janimo: I don't think maintainers are notified on upload18:40
=== hallyn is now known as hallyn-afk
micahg_at least in Ubuntu :)18:40
janimomicahg_, that is a misfeature of LP I'd say18:40
janimoI know I get mails for packages I happened to have uploaded first to ubuntu18:40
janimoand my name sis still in mainatiner field18:40
superm1i think if it's an explicit person listed as a name in the maintainer field they're notified18:41
janimosuperm1, mythtv has a 'maintainer'/owner in Ubuntu18:41
superm1mailing lists/teams probably aren't because of the potentially sending out so much upload spam18:41
superm1think about all the stuff with ubuntu-motu on it18:41
janimofor packages which I know this is the case I am relying on the fact they follow the package closely - KDE is another example18:42
janimoinstead of filing bugs/debdiffs I make uploads but I am happy to post debdiffs in the future18:42
janimoif that lessens the chances of miscommunication18:42
superm1whatever is convenient for you, bug debdiff, email, vcs merge request, ping in irc, just somehow someone in ~mythbuntu getting notified would be good18:43
janimosuperm1, ok18:50
kirklandScottK: uploaded;  was a little bit of a pain as AnAnt had only included a tarball of his debian directory, rather than a merge proposal, or a debdiff;  also, i had to repack the upstream tarball19:10
ScottKkirkland: Thanks.19:10
kirkland@pilot out19:20
=== udevbot changed the topic of #ubuntu-devel to: Archive: Beta-2/Feature/UI freeze | Development of Ubuntu (not support, not app development) | #ubuntu for support and general discussion for dapper -> maverick | #ubuntu-app-devel for application development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu.com/HelpingWithBugs | Patch Pilots:
kirklandjdstrand: slangasek: kees tells me you've had your thinkpad overheat and shut down recently?19:21
kirklandjdstrand: slangasek: I've had it twice in 2 days19:21
ScottKkirkland: Thanks to that upload, people who speak Uyghur will be able to read Ubuntu in their native script.19:21
kirklandScottK: cool19:21
jdstrandkirkland: bug #75168919:21
ubottuLaunchpad bug 751689 in linux (Ubuntu) "Thinkpad x201* overheats due to slow fans when on 'auto'" [Undecided,Confirmed] https://launchpad.net/bugs/75168919:21
kirklandjdstrand: thanks19:22
ScottKdpm: Is there some reference on ubuntu.com about it being an Ubuntu project goal/value that everyone be able to use Ubuntu in their own language?  I thought I remembered that, but I can't find it.19:25
dpmScottK, on a session right now, let me come back to you later19:29
ScottKThanks19:32
GunnarHjkirkland: https://code.launchpad.net/~gunnarhj/gdm/profile/+merge/57218 ready for you. Added a comment on the MP.20:00
dpmScottK, is this what you were looking for? -> http://www.ubuntu.com/project/about-ubuntu/our-philosophy20:03
slangasekkirkland: yes, filed a bug against the kernel for this: bug #74692420:08
ubottuLaunchpad bug 746924 in linux (Ubuntu) "kernel default cpufreq governor fails to take action when system is overheating" [Undecided,Confirmed] https://launchpad.net/bugs/74692420:08
ScottKdpm: It was.  I missed the language bit when I read it.  Thanks.20:20
psusislangasek: that's the job of the ACPI bios20:26
slangasekpsusi: the bios didn't change, the kernel did20:26
slangasekand the bios doesn't control cpu frequency in Linux, the kernel does20:26
dpmScottK, you're welcome :)20:27
psusislangasek: the bios specifies acpi tabeles that are supposed to monitor thermal zones and do things like start fans and limit the cpu speed in response to heat.  the kernel cpufreq govenor has never responded to heat afaik20:28
psusiunfortunately, most bios vendors don't bother actually complying with the acpi spec in this area20:28
psusithe cpufreq govenor has no way of knowing which hwmon temperature to respond to, and how it should respond, even if you have an mwmon temperature sensor, which is why acpi bios is supposed to provide the correct tables establishing the linkages20:31
slangasekpsusi: ok, so why has this regressed between maverick and natty?20:32
psusiwhy do you think it has?20:32
=== htorque_ is now known as htorque
slangasekpsusi: because I can tell the difference between my machine overheating and shutting down and it not overheating and not shutting down20:36
psusithat doesn't mean that it used to lower the frequency when it got hot, it could just be that you weren't getting hot before20:36
slangasekyes, it may not have been lowering the frequency, I'll grant you20:37
slangasekbut the behavior has regressed since maverick20:37
psusisomething could have changed to generate more heat, but I'm fairly certain that cpufreq has not and can not respond to high temp by lowering the frequency.  Have you tried booting back into the older kernel to make sure it isn't something changing in userspace, or maybe a clogged vent or something?20:38
stgraberpsusi: it doesn't seem very likely that slangasek, kirkland, jdstrand and I all happened to have clogged vent issue starting with natty ;)20:40
kirkland:-D20:41
jjohansenin general the natty kernel seems to run a little hotter20:41
kirklandstgraber: yeah, on both of my thinkpads, too20:41
slangasekno, I do need to reboot to the maverick kernel to check it out; that's on my todo list for this week20:41
kirklandit could just be global warming at work, too20:41
* jjohansen is unsure if that is because of less lock contention == work work being piped throguh or something else20:41
* jjohansen needs to dig but we had a bug in maverick where things ran hot too20:42
jdstrandpsusi: my vent is not clogged20:43
jdstrandpsusi: I disassembled the laptop and applied new thermal grease and blew out the fan and vent in an effort to fix this20:43
jdstrandthe natty kernel does run hotter20:44
jdstrandmy guess is the lack of big kernel lock, but I have no idea20:44
jdstrandmaverick's fans run just as slow though, and is the kernel is only about 8C cooler when CPUs/threads are fully utilized20:45
jdstrands/and is/and/20:45
psusihow close is that to the critical trip?20:46
psusii.e. is that 8C difference the difference between shutdown and not?20:46
jdstrandpsusi: critical is 100C here20:47
jdstrandpsusi: I hit that pretty frequently in natty, less so in maverick20:47
jdstrandpsusi: I am now using an updated thinkfan that will actually kick the fans up to speeds that will keep it cool enough-- I have not gone higher than 86C since and that is with a lot of taxing20:48
chrisccoulsonjdstrand, my laptop runs much hotter in natty too20:48
chrisccoulsonand the battery life is absolutely horrendous20:48
chrisccoulsonit's less than 1 hour in natty. my battery has never been great, but it's dropped through the floor now ;)20:48
jdstrandpsusi: so imho there are too issues-- 1) on at least the x201 the kernel is not spinning the fans up high enough and 2) natty in general seems to run hotter20:49
jdstrand(all in the bug)20:49
jdstrandpsusi: I don't see the bug in backscroll, it is bug #75168920:50
ubottuLaunchpad bug 751689 in linux (Ubuntu Natty) "Thinkpad x201* overheats due to slow fans when on 'auto'" [Critical,Confirmed] https://launchpad.net/bugs/75168920:50
slangasekjdstrand: do you think I should mark 746924 a dupe of that one?20:51
slangasekkirkland: "real-life physical damage" - er, it shouldn't unless the acpi tables are wrong?20:51
slangasekI'm not sure the cause is slow fans in my case though20:52
kirklandslangasek: let's just say I quit using my laptop on my lap20:52
kirklandd-:20:52
slangasekI guess I should check that out, though I can't use /proc/acpi/ibm/fan in natty anymore to do so...20:52
psusiyea, the fan spinning faster when temp goes up is also what the acpi bios is supposed to do, but from what I have seen, vendors don't bother implementing20:53
slangasekkirkland: oh right, because if it were better at dissipating heat, it'll be just fine to blow all the exhaust on you ;)20:53
jdstrandI looked up the i7 in intel docs and it tends to run hotter than other systems, and don't think 100C will hurt the cpu (ie, when the kernel shuts down), but that won't be good for the thermal grease or other components20:53
kirklandslangasek: i'd rather it blow 50C exhaust than 98C exhaust20:53
* slangasek prepares to argue the point with equations and diagrams20:54
jdstrandslangasek: I don't know if it is the same issue or not...20:54
kirklandiwconfig is reporting Bit Rate=144.4 Mb/s at this coffee shop ... that's um, impressive ...20:55
jdstrandslangasek: why can't you use /proc/acpi/ibm/fan anymore?20:55
psusihrm... thinkfan eh?  I'll have to look more clusely at this.. looks like it may be a better replacement for fancontrol20:55
jdstrandoptions thinkpad_acpi fan_control=120:55
kirklandslangasek: yeah, /proc/acpi/ibm/fan looks fine for me20:55
jdstrandslangasek: drop that into /etc/modprobe.d, works fine here20:55
slangasekjdstrand: oh, I thought /proc/acpi/ibm had gone away, hmm20:55
kirklandkirkland@x201:~$ cat /proc/acpi/ibm/fan20:55
kirklandstatus:         enabled20:55
kirklandspeed:          327420:55
kirklandlevel:          auto20:55
jdstrandkirkland, slangasek: to manipulate it though, you need to load with fan_control=120:56
slangasekack20:56
kirklandjdstrand: right20:56
jdstrandI have a thinkfan patch btw20:56
jdstrandhttp://people.canonical.com/~jamie/thinkfan_0.7.1-2ubuntu1~jdstrand1.debdiff20:57
jdstrandkirkland, slangasek: thinkfan if you don't know is a daemon that will adjust fan speed based on temperature using /proc/acpi/ibm/fan20:58
* slangasek nods20:58
jdstrand'127' is valid on my x201s20:58
jdstrandand puts the fan in disengaged mode, which keeps it from overheating (86C is the highest I've seen since using it)20:59
kirklandjdstrand: interesting20:59
jdstrandand that debdiff adjust thinkfan to not barf on '127'20:59
kirklandjdstrand: i'd be willing to test that, if it would help get it into natty20:59
jdstrandkirkland: thinkfan is universe. I consider this just a workaround. the kernel should be fixed21:00
kirklandjdstrand: totally agree;  but i'm willing to use a workaround, at this point21:00
jdstrandkirkland: oh yeah, by all means, use it yourself. you have a x201s?21:01
kirklandjdstrand: just a plan old lower resolution x20121:01
kirklandjdstrand: but i do have the i7 proc21:01
kirklandjdstrand: i have a much older x61 running Maverick that I've seen it on more and more lately21:02
jdstrandkirkland: be sure to read the docs, etc, but you could use this as a starting point for /etc/thinkfan.conf: http://paste.ubuntu.com/592803/21:02
kirklandjdstrand: that x61 is a server for me, so it really sucks when it goes down;  i don't notice it immediately, until i need something off of it21:02
stgraberjdstrand: x201s with i7 L640 ?21:02
* jdstrand nods21:02
jdstrandstgraber: yep21:03
=== warp10 is now known as warp8
jdstrandmodel name: Intel(R) Core(TM) i7 CPU       L 640  @ 2.13GHz21:03
stgraberjdstrand: cool, I can use your config as-is then :)21:03
jdstrandhehe21:03
jdstrandalso, you can adjust the bios to disable cores and/or threads which (unsurprisingly) helps quite a bit too21:04
psusislangasek: can you compare powertop readings between maverick and natty?  I wonder if you can see the higher power usage, and maybe identify what is using it21:06
slangasekpsusi: it only happens when I'm running the system at full throttle, there's nothing to look at in powertop that would be meaningful AFAICT21:07
psusislangasek: the overheating only happens at full throttle, but it seems likely that it is just generally hotter all the time21:08
psusiand even under load, there might be too much noise to identify the cause, but confirming the higher power drain would still be informative21:08
=== warp8 is now known as warp100
psusiit would rule out say, the fan spinning more slowly21:09
slangaseksure, I'll look into it21:10
=== JasonO_ is now known as JasonO
=== warp100 is now known as warp10
psusislangasek: I also wonder if you are seeing this printk in your logs when overheating: CPU%d: %s temperature above threshold, cpu clock throttled (t\21:32
psusiotal events = %lu)\n"21:32
slangasekpsusi: I have such log entries from 3 days ago, yes21:33
stgraberpsusi: here I'm only getting this: http://paste.ubuntu.com/592821/ can't find any reference to "cpu clock throttled" in my log21:35
psusihrm... well I found that in arch/x86/kernel/cpu/mcheck/therm_throt.c, which looks like it is checking intel MSRs to notice overheating... but aside from printing the message to the log, it doesn't look like it does a damn thing about it21:38
slangasekhah, good show21:40
* psusi grubles about lack of acpi standard compliance21:40
psusithis whole file looks like an attempt to workaround broken acpi bios by using the processor specific registers directly21:41
slangasekpsusi: so if I'm seeing those messages, does that imply ACPI is being bypassed and not allowed to do its thing?21:44
psusislangasek: I don't think so... I think that like most other systems I have looked at, your acpi bios does not bother properly handling thermal events in accordance with the standard...21:45
psusiI think that basically nobody does, and this code was written to allow the kernel to do something about it despite acpi not working right... but I can't work out just how this is supposed to work21:46
psusislangasek: see under acpi, the bios is supposed to define a thermal_zone that represents the temperature in a given area, such as that of the cpu... most venders I have looked at do this, so you can read the acpi temp21:50
psusibut they are also supposed to define a fan object that allows for monitoring and control of any fans, as well as a relationship between the fan(s) and thermal_zones, including when they should be ramped up..21:51
psusialso a relationship between the cpu and the tz so that it can be throttled... but from what I have seen, nodboy botheres with all of this21:52
psusifrom what I can see, they just stop at the tz and have it signal critical temp, time to shut down... no fan and no throttling21:52
=== dendrobates is now known as dendro-afk
slangasekpsusi: so my ACPI implementation definitely has exposed under /sys information about four cooling devices and associated temperature trip points; unfortunately they all seem to have a trip point set higher than the critical temp at which emergency shutdown occurs (127.5°C vs. 100°C)21:57
slangasekI also, under the current kernel, can't find where the emergency shutdown limit is set21:58
psusihrm.. interesting.... I think it was set by the thermal_zone21:59
slangasekunder the last kernel I had booted, these limits were *different822:00
slangasekthe last natty kernel22:00
psusiyou have a 4 core cpu?22:00
slangasekit was 100 and 92-ish22:01
slangasekyes22:01
psusihrm... yea, I would expect a well behaved bios to have the tz crit at 100 for shutdown, and each cpu core counts as a cooling_device which should be linked to the tz to engage throttling at say, 9222:02
slangasekok, here we go22:02
slangasek$ cat /sys/class/thermal/thermal_zone0/trip_point_*22:02
slangasek10000022:02
slangasekcritical22:02
slangasek12750022:02
slangasekpassive22:02
slangasekso the cooling devices all trigger on the latter trip point, which is higher than the critical point22:02
slangaseksay what22:02
psusiyea, that looks borked22:03
psusibbiab, need to head home22:04
LLStarkshi, i'm wondering whether it's too late to draft up proposals for uds-o. i'd like to present a grub2-gfxmenu implementation to cjwatson and other interested parties.22:22
jdongkees: random question: I don't suppose SSP can be disabled on a per-function basis, can it?22:24
keesjdong: no, and if you've got that level of knowledge, why not fix the function? :P22:26
jdongkees: haha sadly the brokenness is the stack canary actually affects performance in the codepath.22:26
jdongkees: and I already had to eat my hat for claiming it wouldn't!22:26
keesjdong: ugh. what code? it's usually very minor. anything that has strings on the stack usually doesn't have a measurable difference when adding SSP22:27
jdongkees: it's an interrupt service routine on ARM; only discovered the performance discrepancy after porting it to an environment where -fstack-protector is default22:28
jdongI mean of course I can just change the buffer type to be one that -fstack-protector doesn't care about :)22:29
keesjdong: in the kernel?22:31
slangasekmvo: I was pleasantly surprised to see all the multiarch fixes going into the package management infrastructure the past couple of weeks... I really expected multiarch to be enable-on-your-desktop-at-your-peril for this cycle, and was surprised when update-manager started working for me again :)22:36
mvoslangasek: yeah, its pretty cool, the full stack has support now, even in synaptic we have basic support (and aptdaemon too) and you can click on foo:i386 and watch the resolver churn and try to come up with a solution. its quite cool22:38
slangasekindeed :)22:38
* mvo sends hugs to donkult and juliank for their great work on this22:39
lifeless\o/22:39
mvobedtime for me now, see you all tomorrow22:40
* mvo waves22:40
=== dendro-afk is now known as dendrobates
micahg_pitti: so, I discovered what happened to the pidgin symbols, it seems they were intentionally dropped upstream due to portability concerns, I also found that this seems to cause a problem for dockmanager which is a new package in natty, so no inherent regression22:43
pittimicahg_: ah, that explains it at least22:44
micahg_pitti: and that probably should've had an FFe, sorry about that22:47
=== Claudinux_ is now known as Claudinux
psusislangasek, so you said your thermal zone has only critical and passive trip points?  no active?  and the passive is higher than critical?22:51
slangasekpsusi: yes22:52
psusislangasek, that shouldn't change with kernel version, but have to checked if it is like that in maverick?22:53
psusibecause that does look like broken acpi bios22:53
slangasekno, I haven't checked22:53
slangasekregardless, broken acpi is the world we live in - Ubuntu still needs to behave appropriately in the face of it22:54
psusithen you need to come up with specific workarounds for every piece of broken hardware22:55
syn-ackI hate it when a former employer makes it impossible to verify that you worked there because they're that much of a jerk22:55
jcastrokees: I need you to add some people to ~ubuntu-drivers when you get a chance, only TB folks can do so23:03
keesjcastro: oh? for UDS planning? I thought all that got sorted out already.23:05
jcastrokees: we're missing jdstrand and jasonwarner23:06
jcastrokees: and probably iain-farrell too for the Design track23:06
keesjcastro: shouldn't they be part of uds organizers?23:08
* jcastro looks23:08
jcastrook weird, what's the difference between a track lead and a driver? ok, yeah, uds-organizers makes sense23:08
jcastrokees: whatever lets people schedule but not also allow them to like upload glibc or something. :p23:10
azeemit's like rhythm and lead guitar23:10
keesjcastro: I've added jdstrand jasoncwarner and iain-farrell to uds-organizers now23:11
jcastrolooks good!23:12
jdstranddoes that mean I can't upload glibc anymore? :P23:12
* jdstrand doesn't actually ever touch glibc ;)23:12
psusislangasek, heh, I can't even get my netbook to its 85c passive trip point.. seems to top out at 5023:12
keesjdstrand: that would be funny. have uds-organizers block membership in core-dev ;)23:13
jdstrand:)23:13
slangasekpsusi: you need a more powerful processor then! :)23:15
psusislangasek, indeed... it's only a 1.3 ghz 10 watt celleron ;)23:16
jdstrandslangasek, kirkland: for giggles, I updated my bios. when I went into my bios after to check on things, I noticed something called Advanced Thermal Management. Thinking that sounded promising, I moved when on AC from 'Maximum Performance' to 'Balanced'. I don't know if it will fix anything or not yet, I just did it23:18
slangasekjdstrand: do you have similar-looking trip points under /sys/class/thermal/thermal_zone*/ ?23:19
jdstrandit seems like as soon as the temp gets around 83, it does something because it drops down 5-10 degrees or more every now and again, but I don't know if that is just the state of my builds or what23:19
jdstrand$ cat ./trip_point_*23:20
jdstrand10000023:20
jdstrandcritical23:20
jdstrand9150023:20
jdstrandpassive23:20
slangasekright, that's what I had last time I looked23:20
slangaseknow my passive is higher than my critical which is screwy23:20
=== Claudinux_ is now known as Claudinux
jdstrandinteresting-- when compiling 3 kde4libs at the same time, it never goes above 83, and as soon as it gets there, it drops to 75 or so (this is with thinkfan mind you-- but before it would go up to and stay at 86C)23:28
jdstrandbalanved may be worthwhile23:28
jdstrand(anecdotal)23:28
psusijdstrand, what's the fan doing during this time?23:28
psusijdstrand, also it would be helpful to run stress for an even full load instead of something unpredictable like a compile23:29
jdstrandpsusi: well, I am using thinkfan atm, and its above my threshold so it is disengaged23:29
jdstrandre stres> yes, hence the 'anecdotal' :)23:29
psusijdstrand, can you read the actual fan speed?  maybe with lm-sensors?23:29
jdstrandit is 642523:29
jdstrandits disengaged-- I setup thinkfan to monitor the temp and go full-speed about 7523:30
psusijdstrand, so when the temp drops does the fan speed go up?  or is the cpu being throttled?23:30
jdstrands/about/at/23:30
jdstrandpsusi: right, I think the cpu is being throttled with this new 'balanced' thermal management setting in the bios23:31
psusijdstrand, did the trip_point values change as a result?23:31
jdstrandpsusi: I didn't look before, so I don't know23:31
psusijdstrand, well if the trip point is 91.5 then it shouldn't be throttling until you hit that23:32
psusiso my guess is that the fan speed is going up23:32
jdstrandthe fan speed is not going up23:33
jdstrandis is at ~640023:33
jdstrandI am monitoring both temp and fan at the same time23:33
jdstrand6400 is max fan speed23:33
psusijdstrand, both before it hits 83 and while it is dropping to 75?23:33
jdstrandpsusi: yes. thinkfan is setup up to be 'disengaged' at 75 and higher23:34
psusijdstrand, then the big question is whether this happens with stress -c instead23:34
jdstrandfan speed is steady-- cpu meter is pegged to the top, temp is fluctuating between 75 and 8323:34
jdstrandwell, what I need to do is that and disable thinkfan and see what is happening23:35
psusijdstrand, also, how about the frequency?  do you keep an eye on that?23:35
jdstrandnot currently23:35
jdstrandI was trying to see where that is23:35
jdstrandoh23:35
jdstrand/proc/cpuinfo23:36
jdstrandyeah, it just went from 2134.000 to 1199.00023:36
psusijdstrand, add the cpu frequency scaling applet to panel23:36
jdstrandthis advanced thermal management thing is a bios deal23:36
jdstrandI don't have a panel, I am using unity :)23:37
jdstrandbut, I can't stay longer23:37
* jdstrand has an appt23:37
jdstrandthis likely works fine: watch 'cat ./cpuinfo |grep MHz'23:38
jdstrandyep, got to 82 then dropped to 119923:38
jdstrandtemp went to 72 and cpu went up to 213423:38
jdstrandneat23:38
jdstrandok, gotta go23:39
psusihrm... weird...23:39
jdstrandI don't clean to know how 'advanced thermal management' works btw...23:39
* jdstrand -> really gone23:39
jdstrands/clean/claim/23:40
=== chuck_ is now known as zul

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