=== LD_ASHEESH_PATH is now known as geofft
micahgstokachu: not as much as I used to be, but if somethings needed, I can try to squeeze it in00:08
stokachumicahg: is there someone who took up that task?00:08
=== txwikinger2 is now known as txwikinger
micahgstokachu: I think the 3 of us who are "active" do it as we have time00:27
=== mbarnett` is now known as mbarnett
=== Ursinha is now known as Ursinha-afk
=== superm1_ is now known as superm1
stevengottliebi have a question regarding my software update for 12.1004:09
stokachucan i get https://launchpad.net/ubuntu/precise/+queue?queue_state=1&queue_text=gpoint approved?04:36
pitti_Good morning06:30
=== pitti_ is now known as pitti
zygagood morning06:34
=== thegodfather is now known as fabbione
mardykaleo: hi! I was asked to check if the SDK team had any opinion about this: https://lists.ubuntu.com/archives/ubuntu-devel/2013-March/036935.html06:48
apacheloggercjwatson: hey, if you get a chance today it would be cool if you could have a look at https://code.launchpad.net/~kubuntu-members/debian-cd/kubuntu-raring-artwork/+merge/15799806:54
tjaalton@pilot on07:06
udevbot(pilot (in|out)) -- Set yourself an in or out of patch pilot.07:06
tjaaltonpilot in07:07
tjaalton@pilot in07:07
=== udevbot changed the topic of #ubuntu-devel to: Ubuntu 12.10 released | Archive: Frozen for Final Release | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of hardy -> quantal | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: tjaalton, sconklin
=== tkamppeter_ is now known as tkamppeter
dholbachgood morning07:10
=== jussi01 is now known as jussi
=== jono is now known as Guest75135
cjwatsonapachelogger: you definitely want to switch to HIDDEN_TIMEOUT=2 (i.e. the same desktop image boot workflow that Ubuntu uses)?  I don't object, just wanted to double-check that08:19
cjwatsonapachelogger: that's also a UI-freeze-worthy change - are there any relevant docs?08:19
apacheloggercjwatson: yes on the hidden timeout, see bug 1164854 for freeze exception08:28
ubottubug 1164854 in kubuntu-settings (Ubuntu) "[UIFE] Kubuntu Boot Artwork Update" [Undecided,Fix released] https://launchpad.net/bugs/116485408:28
cjwatsongotcha, thanks08:30
=== ckpringle_ is now known as ckpringle
cjwatsonapachelogger: it'll probably take LP a while to notice, but it's merged and deployed now, thanks08:33
apacheloggercjwatson: thank you :)08:33
evbdmurray, pitti: have you heard many reports of reporting to Launchpad still being enabled post-release in 12.10?08:51
evtrying to find the right google terms for that :)08:51
pittiev: no, I didn't; that might happen for people who manually re-enable it?08:51
evvery doubtful in this case - a designer in the office has it enabled on 12.1008:51
evI'll see what else I can find08:52
seb128ev, maybe they played with the control center privacy settings (does that change apport's status?)?08:52
evseb128: that only toggles whoopsie running08:53
seb128apport is enabled in the /etc config ?08:53
evmaybe they've pulled in some 13.04 bits08:53
evin /etc/default/apport08:53
seb128ok, weird08:54
seb128dunno either then08:54
seb128ev, is it possible that they reported a bug, got asked for details and copied/pasted the command from the stock reply that tell them the command to enable apport?08:54
evseb128, pitti: she doesn't appear to have enabled it herself or taken instruction from anyone else to do so. She's also not running anything from raring as far as she's aware. It sounds like a fairly stock system.08:59
evI've asked to have a look at her computer again later today08:59
evI'll see what I can dig up then09:00
pittiev: the precise contents of /e/d/apport would be interesting; perhaps it was modified years ago already09:00
seb128look at when the /etc file got edited and the packages installed around this time in dpkg.log maybe09:00
evwill do to both :)09:00
=== sraue_ is now known as sraue
mptev, remarkable how that most common error in R is much more common in weekdays than weekends ... pre-release, I would have expected the opposite.09:37
evI'm always encouraged when it challenges our preconceptions09:37
lifelessmpt:, ev: o/09:38
maxbI've been using R for my office workstation for weeks, I just have a dual boot to Q on standby in case it all goes horribly wrong09:45
mptev, if we were tracking hangs by now, I get the feeling we'd be seeing a lot in update-manager09:52
seb128the computation to sort depends from an app under the app icon seems to be quite slow09:54
=== doko_ is now known as doko
dokoseb128, what about allowing the deprecated glib functions for the final release of 13.04 again? would save a lot of effort to fix the ftbfs now10:00
seb128Laney, pitti: ^ opinions?10:01
seb128doko, do you have specific deprecations you would like to comment/drop?10:02
seb128we can't just turn any deprecations off10:02
dokomeh :-/10:02
pittiFTBFS because of packages which disable deprecated symbols, but use them?10:02
seb128pitti, yes10:02
seb128in universe10:02
seb128doko, how many of those are left?10:03
seb128should be easy enough to drop the G_DISABLE_DEPRECATED flags, but I'm not sure how many sources we are talking about there10:03
pittiI don't like changing glib itself to not mark them as deprecated, because that would be a lie10:03
seb128same here10:03
dokoI didn't count, but it's every third or fourth package I'm touching10:03
dokoat least the g*'s10:03
seb128how many are left on the ftbfs list?10:03
=== ckpringle_ is now known as ckpringle
pittifor "dead" software we'll keep having this problem, so at some point we need to fix (or remove) those anyway10:04
seb128I would rather trying a bit harder to "clean" those and not change glib10:05
=== tvoss is now known as tvoss|test
pittiso maybe we can find some five people and a day to go through them and drop G_DISABLE_DEPRECATED10:05
=== tvoss|test is now known as tvoss
seb128I can help having a look through the list and fix some10:05
=== tvoss is now known as tvoss|sick
pittior remove the software if it's not even working any more, etc.10:05
Laneyright, I agree10:06
seb128doko, pitti: let me try to build a list of affected sources from the build logs10:06
seb128then we can try to call for help dealing with those10:06
Laneymaybe someone from +1 would help out10:06
Laneyalso mail the motu list10:06
seb128the 5 a days would work for me10:06
seb128ok, let's do that10:06
pittiI can help out there, too; it should be possible to get through some 20 FTBFSes on one day10:06
seb128doko, do you know why > q on that list only failed on armhf? most of those build issues don't seem armhf specific10:09
dokoseb128, see https://launchpad.net/builders10:09
seb128doko, ok, other arches didn't get to those yet10:10
dokoyes :-/10:10
pittidoko: http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20130329-raring.html is still the current one, right?10:25
seb128doko, Laney, pitti: ftbfs i386 due to glib deprecations: http://paste.ubuntu.com/5694973/10:29
seb128well those are the ones that match "grep "is deprecated " *.txt | grep glib"10:29
seb128in the 229 i386 ftbfses10:29
seb128doing the same for other arches10:29
pittiseb128: ah, I was looking at some 20 packages, and so far I didn't find a single one; many are due to missing -lm, or breakage which is specific to that pacakge10:29
seb128same here10:30
seb128pitti, I did some hackish, grep on the .html, wget of the logs and "grep "is deprecated " *.txt | grep glib" on the stack of lgos10:30
pittiseb128: I'll just take the first 20?10:30
seb128pitti, if you want, please10:31
pittiseb128: for NM tests I'm kind of blocked on reaching Dan Williams anyway, and I'm not feeling too awake today anyway10:31
pittiso this seems like the perfect job for a day with just half a brain :)10:31
* seb128 hugs pitti10:31
* seb128 runs the loop of wget on the ~400 armhf build issues10:32
ogra_`400 ?10:37
ogra_`where do you see these ?10:38
ogra_`the fstbfs list doesnt have as many10:38
seb128ogra_`, http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20130329-raring.html10:38
seb128ogra_`, universe is over 50010:39
ogra_`there werent as many last week !10:39
seb128ogra_`, build was not done, there is still 3 days of build backlog on i386/amd6410:39
ogra_`yeah, who cares for these obsolete arches10:40
=== Logan__ is now known as Logan_
seb128Laney, pitti, doko: that's the end of the list (using armhf): http://paste.ubuntu.com/5695016/10:41
seb128total is 59 glib related ftbfses10:41
pittiseb128: would you mind putting them into an etherpad?10:41
pittieasier for coordination10:42
ogra_`would be really nice if the ftbfs UI could filter builds that only fail on one arch10:42
seb128Laney, pitti: http://pad.ubuntu.com/glib-deprecated-ftbfs10:42
seb128that's the full list10:42
Laneyi'll take some this afternoon10:43
pittiseb128: ^5s10:44
seb128pitti, ^5s ;-)10:44
seb128$ grep "try adding it to the linker command line" *.txt | sed 's#buildlog_ubuntu-raring-armhf.##' | sed 's#_FAILEDTOBUILD.*##' | sort | uniq  | wc -l10:46
seb128 10:46
pittithat's mostly -lm?10:46
seb128so twice as many due to missing -l10:46
seb128pitti, 40 due to libm10:47
seb128pitti, I've added the "missing -lm" to the bottom of the pad10:48
seb128let's not mix stuff10:48
pittiseb128: you seem to have some false positives there; easyspice is due to -lm, not due to glib10:51
pittias we have them in your last paste, I'll just drop it from the pad10:52
seb128pitti, ups10:52
mptseb128, thanks for the hint, I reported bug 1167277 about it10:53
ubottubug 1167277 in update-manager (Ubuntu) "Unresponsive for a long time after checking for updates" [Undecided,New] https://launchpad.net/bugs/116727710:53
pittiseb128: and e. g. ecore also only has those as warnings, not failures10:54
pittiseb128: (it fails due to 'PRIO_PROCESS' undeclared, which I can't find anywhere)10:54
seb128pitti, Laney: ok, list down to 11 ...10:54
pittiah, nice10:54
seb128pitti, sorry, I matched warnings only before10:54
seb128those have "error: ... is deprecated ... glib..."10:55
pittiok, so for 11 FTBFSes we shouldn't change glib, but just fix them10:55
pittiI'm fine to do those this afternoon10:55
seb128pitti, thanks10:55
seb128doko, ^ doesn't help you much though :-(10:55
Laneyhow come doko thought there were loads due to that then?10:56
pittiseb128: is that the first block on the pad now?10:56
seb128Laney, he crossed a few while doing fixes10:56
Laneyjust seeing warnings due to glib which failed for some other reason10:56
mptev, end of an era -- the list of bugs in Errors no longer fits one on page of a default Launchpad listing10:56
seb128pitti, yes10:56
* mpt wonders if we can persuade wgrant to increase the default batch size from 75 to 10010:56
pittiseb128: did you see buzztard and cutter-testing-framework in your updated grep?10:56
pittiseb128: these were due to glib (I just uploaded fixes for those two)10:56
geserseb128: instead of greping the .html file, you can also grep the .csv file (but it only lists one log if a package fails on several archs) (http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20130329-raring.csv)10:57
seb128pitti, hum, no, the error is no "deprecated" but "unknow type" ... will add that to my grep, one min10:57
pittiseb128: I'll just take your first block then10:58
seb128 10:58
seb128pitti, those are the only 4 in that case10:59
pittiok, added those10:59
seb128pitti, danke10:59
seb128geser, thanks, I just used the file to have the list of logs to wget, that worked ... maybe next time ;-)11:00
dokopitti, language packs did arrive :-/11:00
pittiyeah, at some point we'll need an update; but they should build on i386 in about an hour, it's just updates11:01
=== MacSlow is now known as MacSlow|lunch
seb128doko, those 5 had dpkg errors, you might want to retry them11:02
Laneyhmm, that's a release version of regex-tdfa11:03
Laneythere's a newer version in proposed - did the rebuild not take that into account?11:03
Laney(not that I'm saying this version is fixed)11:03
=== juliank0 is now known as juliank
dokoLaney, no, rebuild is for the release pocket only. not interested in test rebuilds in things which we don't release. and not everything stays that long in -proposed like haskell ;p11:06
seb128Laney, could you look at the tomboy one? it seems something with the libappindicator sharp bindings, likely a libappindicator issue but you probably know better how the "find the dll" stuff works11:07
zygabarry: ping11:07
Laneyseb128: yes - can you update the pad?11:07
Laneydoko: well, we certainly intend to release everything in proposed ...11:08
seb128Laney, done11:08
* zyga found a python3 bug?11:08
evmpt: we can fix that :)11:08
zygaor python3/python2 bugs11:10
dokozyga, ?11:12
zygadoko: eh, sorry, nothing11:13
zygadoko: I thought I found a python3 metaclass inhertiance regression11:13
zygadoko: but it was my fault for using type(...) vs type.__new__(mcls, ...)11:13
zygadoko: just quickly tested that on precise/raring and it works11:14
evapw: I found the problem with getting kernel oops reports on https://errors.ubuntu.com. Fixing now.11:31
Laneyseb128: I think that the problem is that libappindicator0.1-cil-dev is an arch:all package but has pkgconfig files in a multiarch directory11:35
seb128Laney, oh11:35
apwev, nice thanks11:36
Laneyie packaging bug11:36
seb128Laney, thanks for investigating ;-)11:36
Laneyshould be easy to fix11:36
seb128Laney, let's make the binary arch any then?11:36
cjwatsonis it architecture-dependent in any other way?  if not, better to move the .pc file to /usr/share/pkgconfig/11:37
LaneyThat would be weird because the library is arch:all11:37
LaneyI'll move the pkgconfig file11:37
seb128that makes sense11:38
=== pete-woods is now known as pete-woods|afk
=== amitk is now known as amitk-afk
=== MacSlow|lunch is now known as MacSlow
=== ogra_` is now known as ogra_
=== cyphermox_ is now known as cyphermox
=== _salem is now known as salem_
=== hggdh_ is now known as hggdh
barryzyga: hi.  problem all sorted out?13:02
=== ckpringle_ is now known as ckpringle
zygabarry: yes, my bad: type(...) != type.__new__()13:04
zygabarry: subclass did not seem to inherit metaclass13:04
barryzyga: ah.  fun stuff. :)13:04
zygabarry: not pythonic :)13:05
zygabarry: well, I learn every day13:05
=== Ursinha-afk is now known as Ursinha
barryzyga: if you ain't learnin' you ain't livin'! :)13:08
zygabarry: is that because type.__new__() somehow super-calls __new__ again while type() does not?13:09
barryzyga: well, hard to know exactly what's going on without looking at your code, but suffice to say, these are tricky corners of the language13:14
zygabarry: I have a few line example13:15
barryzyga: pastebin!13:15
zygabarry: https://gist.github.com/zyga/535453113:16
zygabarry: basically, look at that, if you replace type.__new__() with type() - it fails13:17
barryzyga: py3 docs on __new__: http://docs.python.org/3/reference/datamodel.html?highlight=__new__#object.__new__13:31
barrybut this makes sense, because three-arg type() is a constructor13:31
* barry ->reboots13:31
=== Ursinha is now known as Ursinha-afk
seb128@pilot in14:04
=== udevbot changed the topic of #ubuntu-devel to: Ubuntu 12.10 released | Archive: Frozen for Final Release | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of hardy -> quantal | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: tjaalton, sconklin, seb128
=== Ursinha-afk is now known as Ursinha
pittiseb128: bah, I fixed two causes of FTBFS in thoggen, and now I see that it doesn't build against our current (i. e. already years old) hal, and against our current dbus14:09
pittilast build was in jaunty14:09
pittiat some point we must drop hal stuff anyway, so I'm really inclined to just remove that package; objections?14:10
seb128pitti, hal is on the ftbfs list btw ;-)14:10
seb128pitti, no objection from me14:10
pittiah, it got removed from testing, too14:11
xnoxpitti: do not remove hal !!!!14:11
pittiwe should have removed it about 3 years ago, but some ancient and dead software still depends on it14:11
mdeslaurpitti: flash needs it14:11
* xnox still wants Amazon Pay-to-view to work in US and Google Play Movies work in US/UK/other? and Adobe Flash DRM to work as well.14:11
pittixnox: but for now I only want to remove thoggen14:12
* mdeslaur misunderstood14:12
* pitti congratulates xnox as our new hal maintainer :)14:12
mdeslaurxnox: congrats! :)14:12
pittiseriously, this stuff uses hal!?14:13
pittidoes that even work still these days?14:13
xnoxpitti: i'm on vacation today, so don't take me too seriously =)))))14:13
mdeslaurpitti: i think it uses hal to get the hard disk serial number for drm14:13
xnoxpitti: yes, all of that $drm-crap works on top of flash which depends on hal.14:14
pittiflash certainly doesn't pull in hal14:14
mdeslaurpitti: it doesn't fail if hal isn't installed, but it disabled drm14:14
tjaaltonslangasek: so, fixing lightdm isn't that easy after all, since plymouth-splash could be stopped already before lightdm is about to start (able to hit that here)14:16
tjaaltonslangasek: and adding 'and (stopped plymouth or started plymouth-splash)' means the transition isn't as smooth anymore14:17
pittidoko: could you please retry gnome-pie on ARM? This error ("unknown type name 'GCancellab'14:20
pittidoko: ...) doesn't make any sense14:20
pittisun rays/RAM corruption/etc ?14:21
pittiit builds fine on amd64, and "GCancellab" doesn't appear any where in the code14:21
dokopitti, done14:21
pittidoko: that's it then, all the rest of glib-induced failures uploaded14:22
pitti(and got accepted)14:22
pittiseb128: ^ FYI14:22
seb128pitti, danke14:23
seb128doko, pitti, I've fixed some of the -lm issues, will try to do some every day14:23
dokoseb128, thanks!14:24
seb128yw ;-)14:24
dokotried to revert that one in binutils, but that seems to be tangled with other uploads, maybe glibc14:25
seb128doko, specifically libm or linking being pickier?14:25
dokoseb128, there are other libs too, but libm and libpthread are the ones which are seen many times. there were some libgmodule-2.0 (or such) too14:27
bdmurrayev: no, but I haven't looked14:29
* dholbach hugs seb12814:35
* seb128 hugs dholbach back14:35
slangasektjaalton: hmm, ok14:39
Quintasanwhy on earth I can't login into cups admin panel with my username and password when I am in the lpadmin group?14:42
ogra_doko, looking at the ants buioldlog it seems to think it hits an ICE, do you think it makes sense to give it back at least once ?14:54
dokoPlease submit a full bug report,14:55
dokowith preprocessed source if appropriate.14:55
dokoSee <file:///usr/share/doc/gcc-4.7/README.Bugs> for instructions.14:55
dokoThe bug is not reproducible, so it is likely a hardware or OS problem.14:55
dokoit even tells you =)14:55
ogra_i know that it tells me :P14:55
* ogra_ was there during that reading class back then :P14:56
ogra_doko, i'll do a local build later then to collect that14:56
dokoogra_, wait until the build finishes ...14:57
ogra_oh there is a build running ?14:58
ogra_i wish the ftbfs UI would reflect that14:58
ogra_bah, 2min old :P14:58
ogra_doko, bino looks like a rebuild candidate too (bus error while unpacking deps)15:02
ogra_doko, err, sorry that was brise15:02
ogra_(wrong row)15:03
dokogiven back15:03
dholbachcan somebody moderate my mail on u-d-a?15:35
cjwatsondholbach: done15:37
dholbachthanks cjwatson15:37
menaceare there dbg-packages for nautilus in ubuntu precise?15:52
menaceif yes: in which package? there is no nautilus-dbg15:53
Sarvattmenace: https://wiki.ubuntu.com/DebuggingProgramCrash debug symbol section on there, its nautilus-dbgsym15:55
seb128@pilot out15:57
=== udevbot changed the topic of #ubuntu-devel to: Ubuntu 12.10 released | Archive: Frozen for Final Release | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of hardy -> quantal | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: tjaalton, sconklin
seb128menace, nautilus-dbgsym like for any other binary, you just need to enable the ddeb source15:58
seb128or Sarvatt already replied15:58
menacesry, kvm-switch...16:15
Laneyapachelogger: are your kdiff3 and im-config patches forwarded?16:32
=== deryck is now known as deryck[lunch]
=== security is now known as megha
tjaalton@pilot out17:41
=== udevbot changed the topic of #ubuntu-devel to: Ubuntu 12.10 released | Archive: Frozen for Final Release | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of hardy -> quantal | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: sconklin
=== deryck[lunch] is now known as deryck
zygaI just got locked out of my laptop18:16
zygararing desktop, I updated / rebooted18:16
zygasecure boot blocked my system18:16
zygacjwatson: ^^ ?18:16
zygaI disabled secure boot, I'm now in 3.8.0-1718:17
zygaI've updated to
zygalet's see18:23
zygapitti: do you know who would be the best person to debug this?18:26
infinityslangasek: Can you remind me where the Debian bug for that WUR issue was?  I lost context somewhere in the last few days.18:37
slangasekinfinity: what's 'WUR'?18:45
infinityslangasek: warn-unused-result18:45
infinityslangasek: I thought it was a samba bug, but can't find it, and now I can't find context for our conversation either, leading me to wonder if I've gone (more) insane.18:47
infinityOh, hah.  But the last "git show" in my bash history is for 7e66ee5142deda977163d0a858c3d2883cae3f07 which happens to be the commit with the liberal application of __wur.18:48
slangasekinfinity: ah right - I think it was on cifs-utils?18:48
infinitySo, I don't have the bug tracker context, but I have the code.18:48
ubottuDebian bug 701422 in src:cifs-utils "cifs-utils: ftbfs with eglibc-2.17" [Important,Open]18:49
infinityslangasek: That's it, thanks.18:49
mlankhorstslangasek: runlevel is set to 2 from telinit, can plymouth-stop run because of stopped rc RUNLEVEL=2, before rc RUNLEVEL=2 is started?18:57
slangasekmlankhorst: I'm confused by the question. Are you asking whether a 'stopped rc RUNLEVEL=2' event would be seen before a 'started rc RUNLEVEL=2' event would be emitted?18:58
slangasekit cannot18:58
mlankhorstmeh something weird is happening though19:01
tjaaltonI can't get --verbose work with upstart on raring19:28
tjaaltoninitctl log-priority still shows info19:28
tjaaltonafter adding the option to cmdline19:29
stokachucould i get someone to approve nominations for bug 106957019:30
ubottubug 1069570 in MAAS "1 MAC Address, two IPs - DNS is "out of sync" with DHCP leases databases, I think..." [Critical,Triaged] https://launchpad.net/bugs/106957019:31
slangasektjaalton: the kernel commandline?19:40
slangasektjaalton: it definitely WFM19:40
tjaaltonslangasek: yeah, not here :)19:47
slangasektjaalton: ah, in fact 'initctl log-priority' shows the same for me, but I'm definitely /getting/ logging19:48
tjaaltonwhere does it log?19:49
tjaaltonupstart cookbook says 'grep init: /var/log/syslog' but nothing there19:50
slangasektjaalton: it logs to dmesg, effectively19:55
slangasektjaalton: and there's a bug in recent releases that I haven't pinned down which prevents this from finding its way into syslog19:56
slangasek(presumably a kernel or rsyslog bug)19:56
tjaaltonslangasek: ahh, yeah dmesg has them19:57
zyga_I need help figuring out why my raring system stopped booting in secure mode20:47
zyga_anyone interested?20:47
slangasekzyga_: "secure mode" meaning UEFI Secure Boot, or something else?20:48
zyga_slangasek: yes20:48
zyga_a bit hectic over here (real life problems piling up, almost contained now)20:48
slangasekzyga_: where does it break down?  Can you still boot older kernels?20:49
zyga_slangasek: I was on 3.8.0-5, rebooted to -17 failed to boot in secure boot mode20:49
zyga_slangasek: I tried they all seem to have failed20:49
zyga_I could not access grub easily though20:49
zyga_I can now reinstall -5 and other kernels (I have a local mirror with --no-cleanup)20:49
zyga_and retest anyway you like20:49
zyga_this is a lenovo g580 system20:50
zyga_it never had secure boot issues before20:50
zyga_it works since december last year20:50
slangasekhow do you mean, "could not access grub easily"?  there's the problem that holding shift doesn't work to display the grub menu, but you should still get the grub menu after any failed boot20:50
zyga_slangasek: I didn't get either20:50
zyga_slangasek: I managed to get into normal boot and edit /etc/default/grub enough to access the menu20:50
slangasekwell, there was an upload of grub2 just yesterday20:51
slangasekit's possible something regressed as a result of the rebuild :/20:51
zyga_slangasek: would it affect secure boot or are those unrelated?20:51
slangasekzyga_: well grub is the bootloader, so it's relevant to secure boot20:52
zyga_slangasek: ok, I can install -17 (current) and -16 only20:52
zyga_silly me20:52
zyga_I thought we used a shim20:53
slangasekthat's the first stage bootloader only20:53
slangasek(and hasn't been changed)20:53
zyga_isn't that what is actually signed?20:53
zyga_I'm not sure if my messages were from bios, shim or grub though20:53
zyga_what would you advise checking?20:53
slangasekcan you try downgrading to grub-efi-amd64-signed 1.11+2.00-12ubuntu1 and grub-efi-amd64 2.00-13ubuntu2 ?20:54
zyga_let's see if I have it already20:54
slangasekwhat messages?20:54
zyga_yes, I have that20:54
zyga_slangasek: failed secure boot messages20:54
slangasekwell, if you can quote me the message I can probably tell you where it's from ;)20:55
zyga_I'd have to reboot, I'll write it down the next time20:55
zyga_slangasek: ok, let me install those packages20:56
zyga_slangasek: can I just dpkg -i the relevant debs?20:57
slangasekzyga_: yes; if you do it that way, you'll need to include the matching grub-efi-amd64-bin and grub2-common packages20:57
zyga_can I do it via apt somehow?20:58
slangasekzyga_: IFF those versions are still in your cache20:59
slangasek(your apt cache, not the physical cache on disk)20:59
zyga_slangasek: I have that in my mirror20:59
zyga_but it's probably not in Packages20:59
zyga_let's do it manually20:59
slangasekanyway, it's probably not worth figuring out how to do it with apt, you might as well just dpkg -i the 4 packages20:59
zyga_there are also -bin packages20:59
zyga_should I get them/20:59
slangasekzyga_: grub-efi-amd64-bin, grub-efi-amd64, grub-efi-amd64-signed, grub2-common, grub-common - AFAICS that's what you need21:02
zyga_ok, let me try21:02
slangasek(I overlooked grub-common the first time, sorry)21:02
* zyga_ tries to munge that into shell21:02
zyga_$ sudo dpkg -i grub2/grub-common_2.00-13ubuntu2_amd64.deb grub2/grub2-common_2.00-13ubuntu2_amd64.deb grub2-signed/grub-ef21:04
zyga_i-amd64-signed_1.11+2.00-12ubuntu1_amd64.deb grub2/grub-efi-amd64_2.00-13ubuntu2_amd64.deb grub2/grub-efi-amd64-bin_2.00-13ubuntu2_amd64.deb21:04
zyga_ok, installed21:05
* zyga_ *had* to install mirror just to get this recovery option ;)21:05
zyga_slangasek: shall I reboot and re-enable secure boot now?21:05
slangasekzyga_: that's the thing to try21:05
zygaslangasek: it failed the same way, I took a photo21:10
zygaslangasek: let me share it21:10
zygaslangasek: https://plus.google.com/116315264177593873442/posts/9UUGFQ2cphM21:11
slangasekzyga: mmm.  Do you have the shim and shim-signed packages installed?21:12
slangasekzyga: (the answer is that these messages are from firmware)21:12
dokostgraber, python-cffi is the new way to write python bindings21:14
zygaI don't?21:14
zygaI have shim-signed21:14
zygaslangasek: I don't have shim21:14
slangasekzyga: ok, that should be sufficient21:14
zygaslangasek: http://paste.ubuntu.com/5696609/21:15
slangasekzyga: what's the output of 'sudo efibootmgr -v'?21:15
zygaslangasek: dpkg --get-selections21:15
slangasekzyga: md5sum /boot/efi/EFI/ubuntu/grubx64.efi ?21:16
zygabb8cea9bb89a83aa714bd175d61cf5bc  /boot/efi/EFI/ubuntu/grubx64.efi21:16
slangasekzyga: doesn't match the shim-signed binary21:17
slangasekzyga: so, we should figure out where it does come from21:18
zygaslangasek: how did you figure that out, from this line: ?21:18
zygaBoot0001* UbuntuHD(1,800,2f000,947c5c3f-fa10-495c-b18d-97a7c757148f)File(\EFI\ubuntu\grubx64.efi)RC21:18
slangasekzyga: well, I mostly figured it out because I helped implement it so know what's supposed to be where ;), but yes, that line shows the path that's being booted21:19
slangasek(I wanted the efibootmgr output to confirm that the boot options themselves were configured correctly)21:19
zygaright, I meant the actual checksum21:19
slangasekzyga: I checked the shim-signed package21:19
slangasekzyga: you could try reinstalling shim-signed21:19
slangasekzyga: but before you do, please make a copy of grubx64.efi21:20
zygatoo late :/21:20
slangasekohwell ;)21:20
slangasekzyga: order of operations fail on my part21:20
slangasekzyga: so what's the md5sum of that file on disk /now/?21:20
* slangasek scratches his head21:21
slangasekthat's not the md5sum I expect either ;)21:21
tjaaltonslangasek: turns out the upstart logs don't have any mention of plymouth-splash, so no wonder 'started plymouth-splash' didn't work21:21
zygacde67f528af411dd8d8f1b4bc643b484  /boot/efi/EFI/ubuntu/grubx64.efi21:21
zygaslangasek: is that the right file?21:22
tjaaltonproblem is I don't know what would work, so that the smooth transition is preserved21:22
tjaaltonsomething to play with tomorrow then21:22
slangasektjaalton: do you have plymouth in the initramfs?21:22
tjaaltonslangasek: probably, using cryptsetup21:22
zygaslangasek: I can probably find the older grubx64.efi from the mirror I use21:23
slangasektjaalton: right, that explains - no 'started' event because the service is started before upstart is21:23
zygaslangasek: and if it has the right md5sum I've pasted here, give it to you21:23
slangasekzyga: actually, sorry, I was directing you to the wrong place21:23
tjaaltonslangasek: ha, ok21:23
tonyyarussoHey everybody, I've been doing some mucking about with a script shipped with update-notifier-common (/usr/lib/update-notifier/apt_check.py).  I discovered that while it appeared to be intended to be usable as a module, it was never tweaked to actually be so.  So, I made some changes and was wondering if anyone could take a glance to see if they seem sane.  Here's the original: http://pastebin.com/102RGrjK , the new version: ...21:24
tonyyarusso... http://pastebin.com/j7ZNVdMg , the diff of the two: http://pastebin.com/4Rmy1Hjc , and an example script using it as a module: http://pastebin.com/p808Hp9T .21:24
slangasekzyga: because apparently the system I was referencing here is also not configured for SB currently :P  How about 'sudo grub-install --uefi-secure-boot', then check if the efibootmgr output shows a different boot path?21:24
zygaslangasek: it _removed_ ubuntu?21:25
zygaslangasek: http://paste.ubuntu.com/5696643/21:25
zygaslangasek: as you can see21:25
slangasekthat's... special21:25
zygatonyyarusso: hi, I think this is best addressed on the ubuntu-devel@ mailing list21:26
zygatonyyarusso: alternatively as a merge request (to trigger discussion) to the relevant project on launchpad.net21:26
zygaslangasek: am I being hacked or is this 20*13* showing its teeth21:26
zygaslangasek: and we got a borked upload with some interesting bug21:26
slangasekzyga: man, I don't know - none of these pieces have been uploaded recently, except for grub and the change there is irrelevant!21:27
tonyyarussozyga: All righty - care to point me to a primer on how to do a merge request?  I've opened bugs before, but haven't had a solution to offer.  :)21:27
slangasekzyga: so, ah... if you run grub-install again, does the missing boot entry come /back/?21:27
zygatonyyarusso: sure, there's a full help page on launchpad about that21:27
zygaslangasek: checking21:27
stgraberdoko: is that the actual upstream recommended way of doing bindings nowadays? my understanding was that ffi was indeed quite cool to generate minimal on the fly bindings as something a bit cleaner than ctypes, but it didn't look like something that should be used for a full upstream binding21:28
lifelessstgraber: upstream for what value of upstream21:28
zygaslangasek: do I get it right that I should _not_ reboot now ;)21:28
slangasektonyyarusso: http://developer.ubuntu.com/packaging/html/udd-intro.html + http://developer.ubuntu.com/packaging/html/fixing-a-bug.html21:28
slangasekzyga: yes, probably don't do that ;)21:28
lifelessstgraber: upstream has never recommended ctypes for bindings21:28
zygaright ;)21:28
* zyga has been in such a situation once before ;)21:28
slangasekzyga: in theory you could still browse manually in the firmware and ask it to boot the Ubuntu botloader by name, but that doesn't sound fun21:29
zygaslangasek: ah21:29
zygaslangasek: so uefi shell is always around?21:29
zygaslangasek: I thought that's only in the reference impl21:29
stgraberlifeless: doko was essentially saying I should be using cffi for the LXC binding instead of my current native C extension21:29
zygaslangasek: been there, done that, should be okay if I have to21:29
slangasekzyga: not shell; it's incompatible with Win8 cert reqs to ship the shell21:29
slangasekzyga: but your firmware menu *probably* has an option to boot a specific EFI executable by path21:30
slangasek(this only works under Secure Boot if the binary is signed)21:30
zygahmm, I don't recall such a menu21:30
stgraberlifeless: I know ctypes haven't been recommended by upstream and for very good reason, that's why to me cffi looked like something a bit cleaner than ctypes but not something that upstream python would recommend for a real-world binding21:30
lifelessstgraber: cffi should be equivalent, because it still invokes the compiler21:30
zygawhat shall we try next?21:30
slangasekzyga: I'm reading grub-install code right now to figure that out21:31
zygaslangasek: if the next UDS wasn't virtual I'd get you a beer for helping me :)21:31
slangasekzyga: what the heck... how about sending me the output of 'sh -x /usr/sbin/grub-install --uefi-secure-boot'?21:32
zygaslangasek: I'll set LANG= so that you can read it21:33
slangasekif you wish ;)21:33
tjaaltonslangasek: a horrible hack I guess but works: 'and (started cryptdisks-enable or started plymouth-splash)' :)21:33
slangasektjaalton: truly horrible; I think we should fix upstart instead to synthesize 'started' events for jobs started from initramfs21:34
zygaslangasek: http://pastebin.ubuntu.com/5696669/21:34
slangasektjaalton: (there's no guarantee that plymouth in the initramfs is caused by use of cryptsetup, for one thing)21:34
tjaaltonslangasek: heh, yeah. I was wondering if there was some more generic event to abuse here21:34
slangasektjaalton: not really, we need to create one - either by fixing it in upstart, or by adding a secondary job that's 'start on startup or started plymouth-splash', checks for plymouth-splash running already, and emits an appropriate common event21:36
tjaaltonslangasek: right, that could work21:36
tjaaltonas an interim solution21:37
slangasektjaalton: and by 'checks for plymouth splash running', I mean checking the output of 'status plymouth-splash'21:37
dokobah, after every reboot after a unity update my system comes up in low graphics mode21:38
tjaaltondoko: most likely not related to unity, but the lovely plymouth-splash/lightdm race we have21:40
tjaaltonwhich is finally understood, just needs some head-scratching to fix it properly :)21:40
dokobut unity sees updates more often =)21:40
slangasekzyga: 'fs_module=ext2' (line 1453) - /boot/efi is a VFAT partition, right?21:41
tjaaltondoko: pastebin Xorg.0.log from the failing boot21:41
slangasekzyga: hmm, ok21:41
slangasekzyga: so what if you run this command by hand?: efibootmgr -c -d /dev/sda -p 1 -w -L ubuntu -l \EFI\ubuntu\shimx64.efi21:44
slangasek(with appropriate quoting)21:44
zygaappropriate quoting?21:44
zyga\ ?21:44
zygaEFI uses windows style path separators?21:44
zygaslangasek: nothing21:45
dokotjaalton, hmm, $ ls -l /var/log/Xorg.*21:45
doko-rw-r--r-- 1 root root 31919 Apr 10 23:37 /var/log/Xorg.0.log21:45
doko-rw-r--r-- 1 root root 31151 Apr 10 23:36 /var/log/Xorg.0.log.old21:45
doko-rw-r--r-- 1 root root 34547 Apr 10 23:35 /var/log/Xorg.failsafe.log21:45
doko-rw-r--r-- 1 root root 34547 Apr  7 22:36 /var/log/Xorg.failsafe.log.old21:45
slangasekzyga: successful exit?21:45
zygaslangasek: as in, efibootmgr -v does not list anything new21:45
zygaslangasek: 121:45
slangasekzyga:  -v it21:46
zygaslangasek: it dind't print anything either way21:46
slangasekwhat's up with that21:46
tjaaltondoko: hmm, .old is probably not useful, guess you logged out soon?21:46
slangasekzyga: are you sure /bin/efibootmgr isn't corrupt/trojaned/21:46
dokotjaalton, yes21:47
zygaslangasek: if it was, that'd be interesting21:47
barryslangasek: just to verify, the patch to bug 1078697 needs to be backported to lucid-updates, right?  i ask because the patch in raring/precise does not apply cleanly, and i want to make sure i need to adapt it before i spend too much time on backporting (a lot has changed in the code since lucid ;)21:47
ubottubug 1078697 in apt (Ubuntu) "Ubuntu archive is missing SHA-1/SHA-256 hashes for some packages" [High,In progress] https://launchpad.net/bugs/107869721:47
dokotjaalton, will keep it the next time21:47
zygaslangasek: since I'm not in secure mode I'd have to boot from a CD to check for sure21:47
zygaslangasek: I can give you the md5sum I currently see21:47
tjaaltondoko: check /var/log/Xorg.0.log next time it happens, it's probably kinda short and shows something like 'no screens'21:47
zygaea865d9082f8aa250fc9f749e6391dbb  /bin/efibootmgr21:47
dokook, will do21:47
tjaaltondoko: in which case it's bug 98288921:48
zygaslangasek: maybe we can strace it?21:48
ubottubug 982889 in OEM Priority Project precise "X trying to start before plymouth has finished using the drm driver" [Critical,In progress] https://launchpad.net/bugs/98288921:48
slangasekzyga: checksum is correct.  strace it is!21:48
zygawrite(3, "B\0o\0o\0t\0000\0000\0000\0001\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 2084) = -1 ENOSPC (No space left on device)21:49
slangasekbarry: I'm confused, why would we need this for lucid-updates?21:49
zygathat's _not_ good21:49
slangasekzyga: have you had any recent kernel panics?21:49
zygaslangasek: did I bork my EFI flash stuff21:49
barryslangasek: that's my question.  when this came up last, cjwatson said it did.  i didn't have a chance to ask him why last time ;)21:49
zygaslangasek: not that I recall but I had a few problems earlier with my wifi (bcm) module21:50
slangasekzyga: are you using the raring kernel?21:50
zygaslangasek: yes21:50
zygaLinux g580 3.8.0-17-generic #27-Ubuntu SMP Sun Apr 7 19:39:35 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux21:50
slangasekzyga: hmmmm, not sure how to address this then; for some context, see http://mjg59.dreamwidth.org/23554.html21:50
zygaslangasek: can I purge that space somehow?21:51
slangasekzyga: you may be able to clean it manually from the efivars filesystem, *but*, the firmware may not recognize you've done this until after you've rebooted21:51
slangasek(maybe rebooted /twice/ according to that page)21:51
zygaslangasek: is that safe?21:52
zygaslangasek: and how do I erase it, just files?21:52
slangasekand of course the thing you're trying to write to firmware right now is your bootloader entry, so :P21:52
zygaI have a ton of things in /sys/firmware/efi/vars21:52
slangasekzyga: none of this is safe, here there be dragons, but if you can find the right variable it should be safe to remove it since that's basically the same thing efibootmgr itself does21:53
zygacan I remove dump- variables?21:53
=== Ursinha is now known as Ursinha-afk
zygaman, I want the old bios back21:54
zygaor uboot ;)21:54
slangasekzyga: I would /guess/ those are the kernel pstore variables, yes21:54
zygaslangasek: rm -rvf dump-*21:55
slangasekzyga: not sure21:55
slangasekzyga: note that there's a 'del_var' interface there21:55
slangasekyou might need to use that21:55
zygaI need to get a charger21:55
slangasekor you can use /sys/firmware/efi/efivars instead21:55
zygathis day is _interesting_21:55
slangasekwhich is more filesystem-like21:55
slangasekrm /sys/firmware/efi/efivars/dump* ?21:56
zygaone has files, other directories21:56
zygawell, efivars has files21:56
slangasek/sys/firmware/efi/efivars is the new hotness21:56
zygaeach dump- is full of backtraces21:56
zygaI wonder if that's safe21:56
zygaI mean21:56
zygait's flash21:56
zygait's going to die21:56
zygaand people get tons of that (wifi, nfs, etc)21:56
slangasekzyga: that's a question for the kernel team after we get you booting again :)21:57
slangasekzyga: in the meantime, rm the dump*, and reboot to either recovery media or (preferably) to /efi/ubuntu/shimx64.efi directly, then recover your bootloader entry with efibootmgr21:58
slangasekwell, you can try efibootmgr one last time /before/ rebooting, but no guarantee that'll work21:58
zygaslangasek: ok, I need to prep some stuff21:58
zygaslangasek: yeah21:58
slangasekzyga: the good news is, the variable names encode a unix timestamp and you've been accumulating these since at least December... so unlike some other implementations, yours seems to include a proper amount of variable space... :P22:00
zygaslangasek: ok, power up22:00
zygathanks lenovo22:00
zygaslangasek: let me burn raring image on a CD before we continue22:00
slangasekzyga: but be aware that filling the efi nvram is known to brick laptops in some cases (Samsung's implementation most notably), so even if we get those vars removed there's still some risk that this is going to go south on reboot22:01
zygaslangasek: well, I was about to get my refresh anyway ;)22:02
zyga(thought this laptop is brand new)22:02
zygaI wonder if that's under warranty22:02
* zyga wgets current raring image22:03
zygaI guess it sucks to have the full mirror and yet wget all the iso's22:03
slangasekzyga: did the 'rm' work?22:03
zygaI didn't try22:03
zygaI want to burn raring DVD before I continue22:03
slangasekthat part's safe enough to try, but ok22:03
zygaI can burn the older DVD I still have in my archive22:04
zygaand then rm22:04
xnoxslangasek: barry: yes, we need it for lucid _or_ for lucid in cat-ppa to deploy it where the checksums are generated.22:04
chilukslangasek, I was just trying to verify pad.lv/1057358 , and the fix is still not showing up in the final deb.  It looks like you still have the patch too far down 00list22:06
chilukI haven't figured out what processes 00list, and why it's so touchy... but I know it to be true.22:07
slangasekchiluk: I didn't upload it; looks like that was stgraber's upload?22:08
chilukI don't know.22:08
chilukslangasek, I assume you have a script that goes through and auto marks packages for needing verification.22:11
chilukthat's why I got excited.22:11
slangasekchiluk: the script is run manually by the SRU team when the package is accepted into -proposed; in this case that got missed somehow and stokachu prodded me :)22:12
slangasekbut anyway, if the fix isn't working, you'll want to take that up with stgraber22:12
chilukyeah we'd really like to get this "simple" bug off our queue.22:12
slangasekchiluk: or simply following up to the bug with that info and marking it 'verification-failed' to nudge things along22:13
chilukalready marked verification-failed22:13
stokachuchiluk: what did you break22:14
chilukwasn't me this time.22:14
chilukalthough I feared it was me.22:14
zygaslangasek: burning22:15
stokachuchiluk: are you using edit-patch to make sure the previous patches are applied before doing your work?22:15
zygaslangasek: I'll remove the dump-* variables after that22:15
slangasekzyga: ok22:15
zygaslangasek: I think it's really bad that we keep no bounds on the number of those22:15
zygaslangasek: I mean, keepin one or 5 is okay22:15
zygaslangasek: keeping them till we can is crazy22:15
chilukstokachu... it's a gotcha with isc-dhcp... where it requires certain patches to be in a certain order or it will revert them halfway through the build.22:15
chilukbasically I fixed my deb-diff..22:15
stokachuchiluk: i did a build recently and didnt see that problem22:15
chilukbut my fix didn't get pulled in.22:15
chilukstokachu, then you were doing it wrong!22:16
chilukmy debdiff works.22:16
stokachuapparently not if the verification-faild22:16
chilukwhat's in the repo has the dhcpd-ldap-apparmor.dpatch  at the end of the file where it gets reverted22:16
chilukmy debdiff is not what has been applied.22:16
slangasekzyga: that's one of the problems here, yes.  another is using precious nvram for non-fatal kernel oopses22:17
slangasekzyga: once this is all over, do you mind filing a bug on the kernel package about this?22:17
zygaslangasek: absolutely22:17
chilukman I was really excited to get this bug out of my queues ..22:17
zygaslangasek: better yet, on ubuntu-devel@ we have a million bugs anyway22:18
stokachuchiluk: https://launchpadlibrarian.net/136643012/isc-dhcp_4.1.ESV-R4-0ubuntu5.8.precise.debdiff22:18
stokachuit add the patch at the end of 00list22:18
zygaslangasek: bot not many of them may brick machines22:18
stokachuchiluk: if you used edit-patch within the source directory it would handle all this for you22:18
chilukI did use edit-patch... that's what screwed up in the first place.22:18
zygaslangasek: I'll copy all the dumps from that nvram to my good old hdd22:19
chilukstokachu, from 00list  #these get reverted during the build, so put non-ldap22:20
chiluk #patches earlier22:20
stokachuchiluk: then i dont know b/c like i said i did the process for each distro using both dpatch and quilt22:20
chilukstokachu, you should really verify your debdiff to make sure that your patch does not get reverted.22:20
zyga_slangasek: ehh22:23
stokachuchiluk: edit-patch applys all patches and the work i did on top of that would've already had whatever ldap gets reverted22:23
zyga_slangasek: I cannot understand anything22:23
zyga_slangasek: my kernel just crashed22:23
zyga_slangasek: I tried to rsync my efi vars just in case there's something I need to restore later22:23
slangasekstokachu: the build log shows what's up, with the patch being applied at build time for the 'patched-ldap' build, followed by it being unapplied for a different build. https://launchpadlibrarian.net/132443806/buildlog_ubuntu-precise-amd64.isc-dhcp_4.1.ESV-R4-0ubuntu5.7_UPLOADING.txt.gz22:23
zyga_slangasek: then it didn't fully crash, it was just one big overlay on the framebuffer22:23
zyga_slangasek: then I rebooted it thinking that's it, the CD didn't finish burning22:23
zyga_slangasek: then it _booted_ from disk22:23
slangasekzyga_: omgwhat22:24
zyga_slangasek: but now efibootmgr -v shows Ubuntu22:24
zyga_slangasek: I have the backtrace as a photo, coming up22:24
zyga_slangasek: if this makes any sense22:24
zyga_slangasek: maybe the firmware adds the stuff from disk somehow if there are no entries at all?22:25
slangasekstokachu, chiluk: however, this behavior seems consistent with chiluk's own debdiff on the bug, so...22:25
zyga_that's my current efi22:25
slangasekzyga_: that would be an insane thing for the firmware to do22:25
chilukyeah as I said the current version of code didn't use my debdiff22:25
zyga_slangasek: insane + firmware == daily? right22:25
chilukthe patch I wanted is still in the wron place for 00list22:25
slangasekzyga_: do you have nvram space *now* to update with efibootmgr?22:25
zyga_let's see22:26
zyga_slangasek: nope22:26
zyga_same strace result there22:26
zyga_I didn't remove anything though22:26
zyga_this is insane22:26
slangasek*can* you remove anything?22:26
slangasekor does it all just crash?22:27
zyga_let's try22:27
lifelessis there UEFI support for 32-bit builds ?22:27
zyga_I just did22:27
slangaseklifeless: no22:27
lifelessslangasek: what would be involved, in principle ?22:27
zyga_http://pastebin.ubuntu.com/5696808/ that's what I removed (usunięty == removed)22:28
zyga_slangasek: reboot twice now?22:28
slangasekzyga_: yep22:28
zyga_cross your fingers22:28
slangaseklifeless: grub-efi-ia32 exists, so in theory you just need boot media22:29
slangaseklifeless: as this cannot sanely done on our existing i386 boot image without compromising bootability on *other* systems, this is not something I expect to see in Ubuntu; but you can try to persuade cjwatson otherwise22:30
stokachuslangasek: is it me or is isc-dhcp using bad patching practices22:30
slangaseklifeless: (oh, there's probably installer bits that need doing as well)22:30
lifelessslangasek: I have a tablet here for experimentation, its an atom w/64 bit extensions, but a 32-bit UEFI environment22:30
slangasekstokachu: ... possibly?22:30
lifelessslangasek: and no non-UEFI boot facility [it ships w/windows 8]22:30
stokachuits just weird having to put patches above other because other patches revert code22:31
slangaseklifeless: make someone give you a 64-bit UEFI upgrade for it? :)22:31
lifelessslangasek: so I'm pondering getting enough of Ubuntu onto it to poke at touchscreen and video support.22:31
slangasekstokachu: they don't revert code; the structure of the patch file is magic and used to represent different sets of patches that are applied for different builds22:31
lifelessslangasek: if only it was that easy. I will dig up the right contacts and email them22:31
tuxskarhello, I'm using ubuntu 12.10 and I have this problem using libpcre3-dev22:32
tuxskar~/apertium/apertium-en-es ⮀ apt-cache policy libpcre3-dev22:32
tuxskar  Installed: 1:8.30-5ubuntu122:32
tuxskar  Candidate: 1:8.30-5ubuntu122:32
tuxskar  Version table:22:32
tuxskar *** 1:8.30-5ubuntu1 022:32
tuxskar        500 http://es.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages22:32
tuxskar        100 /var/lib/dpkg/status22:32
zygaslangasek: hmm22:32
tuxskarError: pcre_compile missing )22:32
zygaslangasek: not good22:32
zygaslangasek: keyboard / mouse does not work22:32
zygaslangasek: I've plugged external usb22:32
zygaslangasek: I had this just before the issues began22:33
slangaseklifeless: so if it's for a tablet and what you really need is a preinstalled image on removable media... that's fairly doable by just creating a disk image with a properly configured vfat partition and the magic binary bits in the right directory (/efi/boot/bootia32.efi, IIRC)22:33
tuxskarany idea?22:33
zygaslangasek: also bladernr_ is experiencing that22:33
zygabladernr_: canyou type?22:33
slangasekzyga: !22:33
slangasekzyga: at what point is it failing?22:33
zygaslangasek: it does not respond in any way22:33
bladernr_zyga: i'm fine, mine is an old issue and probably not even closely related to yours22:33
zygabladernr_: no, it started the _same_ way22:33
bladernr_and it's very transient and re-occuring22:33
zygabladernr_: then I rebooted and it all went nuts22:34
zygabladernr_: are you using efi22:34
xnoxlifeless: you can use rEFIt builds of 32bit EFI, it works well enough on UEFI devices despite targetting Apple's EFI from that you can at least boot/chain boot into grub-32bit. The "install" process will be very manual though.22:34
slangasekzyga: so you get what, a firmware screen and no input?22:34
lifelessxnox: thanks22:34
lifelessslangasek: thanks22:34
zygaslangasek: no, I booted to ubuntu :)22:34
xnoxlifeless: this is the most "current" way to bootstrap/boot into 32bit only UEFI.22:34
zygaslangasek: but keyboard / mouse is not operational22:34
lifelessI shall put some time aside in a couple weeks to give it a spin22:34
bladernr_zyga: nope... my system is too old for that22:34
slangasekzyga: ok, I claim no responsibility for this ;)22:34
zygaslangasek: heh22:35
zygaslangasek: ok, so I don't see any efi vars22:35
zygaslangasek: shall I reboot again?22:35
slangasekif deleting efi variables broke your keyboard... then that's a whole new world of crazy22:35
slangasekzyga: you don't see *any* vars, at all?22:35
slangasekdid the efivarfs fail to mount?22:35
zygaslangasek: no, I do see a few, just none of the dump-*22:35
slangasekzyga: I'd try running efibootmgr again22:36
zygaslangasek: they are mounted ok22:36
zygaas in -v or to add the record?22:36
zygathat -s22:36
slangasekzyga: add the record22:36
zygaI booted with partially burned raring disk22:36
zygaslangasek: I think that worked22:37
slangasektwo Ubuntus?22:38
zygashim + grubx22:39
zygais that expected?22:39
slangasekyeah, efibootmgr writes a new boot entry instead of overwriting the existing22:39
slangasekgrub-install has code to handle this22:39
slangasekjust wanted to see which one is which to make sure the ordering was correct - and it looks fine22:39
slangasekso I think you can reboot to SB mode now22:39
zygaand hopefully keyboard will work ;)22:40
zygaslangasek: yay, everything works22:42
slangasekzyga: so the real question is how you ended up with a wrong, non-SB boot entry in the first place22:42
zygaslangasek: so let's file a few bugs22:42
slangasekzyga: upgrade logs may or may not provide illumination on this22:42
zygaslangasek: that's interesting but unless there's a log that knows this I don't know how to find out22:42
* zyga will write a $10 app that "checks if your laptop is about to brick" ;)22:42
slangasekzyga: /var/log/apt/term.log would be a start22:43
zygait should not be translated, meh22:43
zygahttp://paste.ubuntu.com/5696840/ http://paste.ubuntu.com/5696841/ and http://paste.ubuntu.com/5696842/22:44
zygaslangasek: from the second log:22:45
zygaslangasek: Rozpakowywanie pakietu systemd-shim (z .../systemd-shim_1-0ubuntu1_amd64.deb) ...22:45
zygaslangasek: should that be installed?22:45
slangasekyes, it's unrelated to the shim bootloader22:46
zygais that a "shim systemd"?22:46
stokachuslangasek: since isc-dhcp is already in proposed with the reverted patch issue, maybe we can use https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1069570/comments/4122:46
slangasekapparently grub-install isn't verbose enough about its EFI handling22:46
ubottuLaunchpad bug 1069570 in MAAS "1 MAC Address, two IPs - DNS is "out of sync" with DHCP leases databases, I think..." [Critical,Triaged]22:46
stokachuslangasek: to push on top of it22:46
zygaPrzygotowywanie do zastąpienia pakietu shim-signed 1.1+0~20120906.bcd0a4e8-0ubuntu4 (wykorzystując .../shim-signed_1.2+0~20120906.bcd0a4e8-0ubuntu4_amd64.deb) ...22:46
zygathat's all I can see shim-related22:46
stokachuslangasek: it contains changes from previous changelog along with mine and the proper ordering of the patches22:47
slangasekzyga: oh, was shim-signed uninstalled at some point?  (since that's a new install, not an upgrade?)22:47
zygaslangasek: checking22:48
zygaslangasek: I dind't remove it myself if that's what you're asking22:49
slangasekstokachu: er, don't patch debian/ from within debian/patches22:49
zygaslangasek: what makes you think that shim-signed was uninstalled?22:49
zygaas in ever uninstalled22:50
stokachuslangasek: sorry not following what you mean22:50
zygaslangasek: I have history.log files they have timestamps and other info22:50
slangasekstokachu: the debian/patches/add-option-ignore-client-uids.dpatch there is definitely wrong, it shouldn't be patching other patches22:51
slangasekstokachu: debian/patches/add-option-ignore-client-uids.dpatch *contains* debian/patches/dhcpd-ldap-apparmor.dpatch... and patches to 00list and debian/changelog as well22:51
slangasekzyga: oh, sorry, this was a simple reinstall of the package, I was reading wrong22:51
slangasekzyga: so yeah, looks like we have nothing to explain the wrong boot entry22:51
zygaslangasek: yes, that appears to be the case22:52
zygaslangasek: so what about the entry was wrong?22:52
zygaslangasek: the checksum?22:52
slangasekzyga: it pointed to grubx64.efi instead of shimx64.efi22:52
zygaI see22:52
slangasekand only shimx64.efi is signed with Microsoft's key22:52
=== Ursinha-afk is now known as Ursinha
chilukso slangasek word round town is that stgraber is awwl (with leave) who would be the next best person to talk to about getting this issue and  https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1069570 committed?22:53
ubottuLaunchpad bug 1069570 in MAAS "1 MAC Address, two IPs - DNS is "out of sync" with DHCP leases databases, I think..." [Critical,Triaged]22:53
stokachuslangasek: hah, how the..22:53
slangasekchiluk: it seems that stokachu is preparing the SRU patch22:53
zygaslangasek: so I see a few bugs: mysterious grubx64.efi installed, kernel oopses logged to precious efi nvram, no cap / rotation on debug data in nvram22:53
slangasekzyga: the grubx64.efi isn't mysterious; it's expected and required, it's the second-stage bootloader22:54
zygaslangasek: + maybe the keyboard bug but I have no way to explain that (maybe apart from efi fastboot not starting USB for some reason but without any evidence)22:54
zygaslangasek: mysterious as in in that efi config space22:54
zyga(I probably phrase that incorrectly)22:54
slangasekah - yes, the efi boot entry was mysterious22:54
zygaslangasek: I'll write a short email to ubuntu-devel@, I'll follow up with bugs tomorrow22:55
zygaslangasek: I wonder if anyone else got affected by that22:55
zygaslangasek: and if the nvram depletion a factor22:55
stokachuchiluk: that apparmor patch why not just edit debian/apparmor-dhcpd directly?22:58
chilukbecause I was still new when I wrote it at first, and I was curious about the patching system.23:01
chilukcuriousity killed the cat.'23:02
YokoZarcjwatson: I subscribed you to https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1166124  because I remember our conversation ~ the printed text on the CD sleeves being grossly unrealistic a year or two ago23:03
ubottuLaunchpad bug 1166124 in unity (Ubuntu) "Ubuntu minimum system requirements needs to be updated" [Undecided,Confirmed]23:03
YokoZarcjwatson: I'm not sure if Canonical is printing CDs for 13.04 but if so please make sure they don't say 256 megs required :D23:04
zygaslangasek: I wonder if it's safe to upgrade grub2 now23:04
stokachuslangasek: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1069570/comments/4223:04
ubottuLaunchpad bug 1069570 in MAAS "1 MAC Address, two IPs - DNS is "out of sync" with DHCP leases databases, I think..." [Critical,Triaged]23:04
stokachuslangasek: mind taking a peek now, i think ive addressed everything23:05
stokachuslangasek: that should cover the broken -proposed and squash another bug23:06
zygaslangasek: did we get two ubuntu entries after my crash/reboot?23:08
=== Ursinha is now known as Ursinha-afk
zygaslangasek: email sent23:13
=== salem_ is now known as _salem
=== Ursinha-afk is now known as Ursinha
=== Ursinha is now known as Ursinha-afk
=== slangase` is now known as slangasek
=== Ursinha-afk is now known as Ursinha

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