cjwatsonstokachu: are you planning to get the fix for bug 1169740 into raring, as well as SRU?00:05
ubottubug 1169740 in rsyslog (Ubuntu Raring) "rsyslog hangs loading modules" [Undecided,Confirmed] https://launchpad.net/bugs/116974000:05
nemooh. one more thing for you guys. I think this UEFI nonsense is going to be a big stumbling block00:11
nemothere's no way around it anymore00:11
nemoso, some clearer guides, online and in installer, on what to do, would be nice00:11
cjwatsonwe've put a great deal of effort into UEFI already; it would be best if you could file bugs about specific things you feel are missing, rather than a general comment ...00:12
nemocjwatson: heh. was just typing something longer :)00:12
nemocjwatson: but. specifically, the installer was aware Windows 8 was there00:12
cjwatson(also, distinguish plain UEFI from UEFI Secure Boot, as the issues are quite different)00:13
nemobut did not warn me I was not in EFI mode00:13
cjwatsonhey, I'm not going to try to understand anything UEFI-related at 1am local00:13
nemoonly my own paranoia made me halt before blowing away existing setup00:13
cjwatsonthat's why I suggested filing bugs :)00:13
nemoalso. none of the docs explain how to get to EFI boot from Windows 8 - which was what I had to do. BIOS failed horribly in this regard00:13
cjwatson(I'll have forgotten this conversation by the morning ...)00:14
nemooh well00:14
cjwatsonthese are useful comments and I heartily encourage you to file them as bugs so they don't get lost00:14
nemoOh. Also, getting this information to someone who is in Windows 8 and just plugged in USB drive or CD. 'cause booting straight off it sure didn't work.00:18
nemorelative to where they are at that moment.  that's similar to (2) I guess00:18
nemoAnd. Man, is it hard to get into the BIOS screen on one of these fast-booting UEFI setups these days :(00:18
cjwatsonBooting to UEFI from USB is certainly meant to work, and has in the past00:18
nemocjwatson: well. Depends on BIOS setup possibly00:19
cjwatsonLots of room for intersection of our bugs and firmware bugs00:19
nemothise was a lenovo g78000:19
cjwatsonNo idea about the specifics of that00:19
nemowhen I finally got into BIOS screen there were options for boot order. I made sure USB was on top00:19
nemothere was also, under UEFI, windows boot loader and some USB boot loader00:19
nemoI put the USB one on top.  Unfortunately, that still sent me straight to windows.00:20
* cjwatson -> overdue sleep00:20
nemoWhen I went to bios, the boot sequence was right, but windows was back on top00:20
nemosetting boot to USB from the windows 8 options was the only way to get it to work00:20
nemowell. actually legacy mode worked too, but that's how I got to a point in the installer that would have completely screwed everything up00:20
nemooh well. g'nite00:21
stokachucjwatson: i have debdiffs ready for precise, quantal and raring00:37
stokachucjwatson: do you want me to attach raring, quantal? i was waiting on the OP to return with his testing00:37
stokachuand i see he updated00:37
stokachucjwatson: if you see this and im not here i went ahead and filled out most of the SRU, waiting on OP to send me his test case and ill submit it up00:54
stokachucjwatson: and to answer your original question (sorry its late) precise is my main concern as raring can be after release00:56
=== security is now known as megha
=== udienz_ is now known as udienz
pittiGood morning03:53
tjaaltondoko_: pong04:33
=== tkamppeter_ is now known as tkamppeter
dholbachgood morning06:42
=== smb` is now known as smb
evapw: interestingly, we've only ever received 23 KernelOops reports with an OopsText field in them.07:41
evIt doesn't include 12.04, which doesn't have the version of whoopsie that sends the OopsText field, but I wonder if we're failing to correctly process these crashes at an earlier stage.07:41
evapw: http://paste.ubuntu.com/5718063/ - you can look those up individually by going to https://errors.ubuntu.com/oops/$the_oops_id08:06
=== mvo__ is now known as mvo
apwev, indeed they mostly look reasonable, a couple seem truncated to the left ... and 23, i have had more than 23 this cycle i would think08:15
evapw: truncated to the left?08:15
apw('d4ae7486-568d-11e2-a835-2c768aafd08c', OrderedDict([(u'OopsText', u'ence at 00000004\nIP08:15
evand yeah, I have no doubt that we're missing a lot, but I'm not sure why. The daisy.ubuntu.com frontend is very liberal in the reports it'll insert into the database.08:16
evoh interesting08:16
apwi don't know of any bugs or oopses which start that way08:16
apwin fact i think they probabally all start bug or oops08:16
=== doko_ is now known as doko
evso I'm wondering if this is some corner case in apport / whoopsie. (why we have so few)08:16
apwyou should be able to trigger them i think, isn't there a sysrq for that08:17
apwno it always forces a complete reboot.  we could so with a mechanism in our kernel to allow you to trigger them for testing me thinks08:20
StevenKapw: I think there is a magic sysrq for it, but I can't remember what it is either.08:20
apwStevenK, sadly it sets panic_on_oops before it oopses, which is a hard fatal reboot jobbie08:21
apwi cannot sensibly find one to trigger them quietly08:21
StevenKThat isn't playing fair08:21
dokotjaalton, any reason not to merge the JITEmitter.patch in llvm-3.2?08:29
tjaaltondoko: is it from debian?08:32
dokotjaalton, yes08:32
tjaaltondoko: hmm can't find it on 3.2-4?08:35
dokotjaalton, because it's in -5?08:36
tjaaltonpackages.d.o is lagging behind..08:37
dokotjaalton, or #1160587. note that Sylvestre mostly complains about stuff not being in Debian, but he's not caring much for the other way around :-/08:37
tjaaltonI guess it's fine08:39
tjaaltondoko: are you merging it with -5?08:39
tjaaltongetting the r600 updates would be nice too08:39
tjaaltonalthough we didn't get radeonsi support included in raring, glamor-egl isn't uploaded yet and I doubt it would make it in main on such short notice :/08:40
tjaaltonthen a couple of commits to x-x-v-radeon to use these08:40
dokotjaalton, well, I can apply the jitemitter patch08:45
tjaaltontkamppeter: did you pull the whole touch-grab branch from whot, or just that one commit?09:08
tjaaltontkamppeter: I can still crash it easily by changing between the dash icon and indicator menus09:09
tkamppetertjaalton, I only picked that one commit.09:17
tkamppetertjaalton, what sequence of finger clicks I have to do exactly? I clicked the dash icon (Ubuntu symbol at the upper left) and after that one of the indicator icons (Network Manager) and again the dash icon and nothing crashed for me (on the Lenovo Thinkpad Twist).09:19
tjaaltontkamppeter: doing that a few times crashes it here with the branch09:19
tjaaltoni'll try without09:19
dokotjaalton, llvm-3.2 waiting in the queue09:36
didrocksdiwic: I'm seeing quite some people complaining about pulseaudio taking 99% of their CPU since last update. I wonder if inotify doesn't go crazy if /run isn't there or something is tweaked. Heard about it?09:36
diwicdidrocks, no, not yet09:37
tkamppetertjaalton, I cannot reproduce the crash, I tried on both the Nexus 7 and the Thinkpad Twist.09:37
diwicdidrocks, do you have a bug or person affected that I can work with?09:37
seb128diwic, seems like ricotz has it09:38
seb128ricotz, ^09:38
didrocksdiwic: do you speak french? ;) (a lot of people on the unstable part of the french forum are complaining, so not just one isolated case)09:38
didrocksdiwic: I can get them opening a bug report, is there anything I should add in addition to what ubuntu-bug will bring to them?09:38
didrocksif ricotz can do live debugging, that's even better09:39
didrocksricotz: diwic: FYI, people report that if they kill pulseaudio in their session, then it works fine09:39
tjaaltontkamppeter: i'm building with your patch now09:39
didrocksI wonder if it's a race before /run is set for the user or anothing…09:39
diwicdidrocks, I guess attaching to the process and seeing where it's stuck would be the first thing09:39
didrocksdiwic: yeah, they are not *that* technical :p09:40
ricotzdidrocks, diwic, i killed pulseaudio several times and it constantly uses 100% of one cpu again09:40
didrocksricotz: ah, at least, it's more reliable for you, mind helping diwic? ^09:40
diwicricotz, can you attach to it with gdb?09:41
ricotzdidrocks, already downgraded :\, to be able to use my laptop09:41
tkamppetertjaalton, you do not need to build. For Intel I have packages on my PPA and for Nexus 7 there is the tarball attached to the bug. To try without patch, go back to the official packages.09:41
ricotzdiwic, i will give it a try in a moment09:41
tjaaltontkamppeter: building already09:42
diwicricotz, or run sysprof on it could work too, if that easier09:42
ricotzdiwic, although i am running an older kernel here09:42
darkxstI am not seeing the cpu issue, but why would pulseaudio be using 3GB of ram ....09:44
ricotzdiwic, http://paste.debian.net/plain/25023509:50
diwicricotz, all threads appear sleeping in that post09:51
ricotzdiwic, seems like attaching to it released the "loop"09:53
diwicricotz, oh.09:53
diwicricotz, maybe you can try sysprof instead? Have you used it?09:53
tjaaltontkamppeter: it's trivial to get the grab hang with it09:53
tjaaltontkamppeter: just hit the indicators with two fingers a few times09:54
ricotzdiwic, not yet09:54
tkamppetertjaalton, you mean, clicking two indicators at the same time?09:57
ogra_stgraber, i forwarded your mail to the ubuntu phone list10:01
ricotzdiwic, http://people.ubuntu.com/~ricotz/pulseaudio/10:04
ricotzdiwic, not sure how to interpret it10:05
stgraberogra_: thanks. I guess I probably should subscribe to some of those lists...10:05
diwicricotz, hmm, what does the screenshot look like?10:09
ricotzdidrocks, http://people.ubuntu.com/~ricotz/pulseaudio/sysprof.png10:12
didrocksI think this is for diwic ^10:13
ricotzah sorry10:13
diwicricotz, hmm, I loaded your log in my sysprof. It seems to point at e1000e_poll_eerd_eewr_done, but isn't that some kind of network related thing?10:16
ricotzdiwic, actually yes, does pulseaudio probe those for something10:16
ricotzlike discovering bluetooth adapters10:17
tjaaltontkamppeter: no, but rapidly change between two or more indicators by tapping on them with two fingers10:17
diwicricotz, you haven't mounted /run/user on a network drive or something?10:17
ricotzdiwic, no10:17
ricotzdiwic, maybe you missed some prerequisite for the cherry-picked patch10:20
diwicricotz, I wrote the inotify patch yesterday myself10:21
ricotzdiwic, ah i see, alright10:21
ricotz+-        valid_pid_file = TRUE;10:22
ricotz++        valid_pid_file = true;10:22
diwicricotz, yeah, I changed pa_bool_t to bool too10:23
diwicricotz, argh, I don't get it. Why would adding an inotify watch cause the e1000 driver to eat cpu?10:26
tkamppetertjaalton, https://blueprints.launchpad.net/ubuntu/+spec/client-1305-convertibles-and-touch-desktop10:28
tkamppetermlankhorst, bryc: ^^10:31
=== ara_ is now known as ara
diwicricotz, if you do "sudo fuser -v /run/user/ricotz/pulse/pid" a few times, does anything show up?10:31
tkamppeterbryce, ^^10:31
diwicricotz, (assuming your logged in user is "ricotz")10:31
ricotzdiwic, nothing shows up10:34
ricotzdiwic, /run/user/*/pulse/pid contains the correct pid10:35
mlankhorsttkamppeter: we're aware of the touch problem, if it was easy to fix, or even not that hard to fix by the upstream maintainer it would already have been fixed10:35
diwicricotz, hah! I reproduced it here: If I edit the pid file manually (with gedit), PulseAudio starts taking up 100% CPU10:37
diwicricotz, probably there is some software on your machine that accesses it in some way10:39
mlankhorstAnyway I have a fix for bug 1170074, it seems nobody tests on x86 these days but it would be unsurprising if x86 was completely broken for nouveau/radeon because of it. :s10:39
ubottubug 1170074 in mesa (Ubuntu) "mesa 9.1 regressed Tibia on nouveau" [High,Fix committed] https://launchpad.net/bugs/117007410:39
diwicricotz, and that triggers the loop10:39
ricotzdiwic, hmm, i see, running gdm/gnome-shell here10:39
diwicricotz, anyway, if I can reproduce it here, I can hopefully come up with a fix too with some analysis10:41
diwicricotz, thanks so far!10:41
ricotzdiwic, yeah, touching the file triggers it too while running in gdb10:42
ricotzdiwic, ok, yq10:42
rbasakjodh: seen the LWN article on upstart?11:03
rbasak(just FYI, in case you're interested)11:03
jodhrbasak: not yet :)11:03
zygais there a way to select apt-proxy via ubiquity somehow?11:32
xnoxzyga: i'm considering to seed squid-deb-proxy-client package to desktop CDs....11:33
=== hrww is now known as hrw
diwicdidrocks, ricotz, ok, I believe I have fixed it now. Since this is last minute, what precautions do you suggest I take before pressing the "upload" button?11:53
ricotzdiwic, i guess you can put it in a ppa and let someone test it11:54
diwicricotz, are you volunteering? :-)11:54
diwicricotz, I don't know exactly when Final Freeze is, but some time today I believe11:55
didrocksdiwic: is there any risk of things going worse?11:55
ricotzdidrocks, ^11:55
ricotzdiwic, just put the source package somewhere11:55
didrocksdiwic: I can get some people testing from a ppa if you want11:55
diwicdidrocks, ricotz uploaded to ppa:diwic/pulseaudio-testing12:00
ricotzdiwic, alright12:02
diwicbuild starts in 2 hours12:03
didrockspitti: can we have a small bump on https://launchpad.net/~diwic/+archive/pulseaudio-testing/+build/4501878?12:04
didrocksdiwic: forum updated, they will install it once it's available, will keep you posted12:05
diwicdidrocks, thanks, I'll go for lunch in the mean time12:05
didrocksdiwic: enjoy, thanks! :)12:05
pittididrocks: done, it's now next in line12:08
didrocksthanks pitti :)12:09
diwicdidrocks, as for risks for things going worse, I guess the risks are 1) PA crashing or 2) bringing back the original bug (stale PA processes after logout/login)12:15
didrocksdiwic: ok12:16
=== mvo_ is now known as mvo
ricotzdiwic, looks good, can't reproduce it so far12:35
didrocksdiwic: one confirmation on the forum as well :)12:43
=== _salem is now known as salem_
Kalidarnnot sure if this is the place, i'm currently testing raring ringtail and have had some problems getting it to boot.12:54
Kalidarnwhile it is kubuntu (i think its actually pre to any distro stuff)12:55
PiciKalidarn: #ubuntu+1 is probably a better place if you're looking for support/12:55
Kalidarnbasically comes up with grub menu, and then when you select "Start Kubuntu" it says you need to load the kernel first.12:55
Kalidarnyeah i think it might be a bug actually.12:55
Kalidarnunfortunately the error doesn't really tell me that much, the media is fine, already checked that.12:56
Kalidarnthe error i get is:12:57
Kalidarnerror: failure reading sector 0x6d500 from `cd0'.12:57
Kalidarnerror: you need to load the kernel first.12:57
Kalidarni might actually try with standard ubuntu media not kubuntu to test that as well12:57
Kalidarni think it probably affects all variants12:57
diwicdidrocks, ricotz, ok, I'm uploading it now then13:00
didrocksdiwic: \o/ thanks a lot :)13:00
KalidarnPici: would it be recommended to get the latest beta or current daily?13:01
didrocksdiwic: 3 people confirmed on the forum now :)13:01
cjwatsonyou should certainly try a current daily, although I don't know how much difference it'll make13:02
cjwatson"you need to load the kernel first" is a consequent error and not the real cause - you should generally look at the first error not the last13:02
diwicdidrocks, thanks for organising the testing!13:02
didrocksyw ;)13:03
diwicdidrocks, uploaded, fingers crossed13:03
didrocksheh ;)13:03
Kalidarnyeah cjwatson i wonder why its failing to read that particular sector though :) the drive works fine and the media burnt fine hmm.13:03
cjwatsonevidently the boot loader is having genuine trouble with one or the other13:03
cjwatsonit tried asking the BIOS to read that sector three times, and it failed every time13:04
cjwatsonit's a fairly straight INT 13h Function 42h, and I doubt that that was the first sector it tried to read, so my money would be on a drive and/or media failure that your tests didn't pick up, with a backup option of some problem in your BIOS13:05
cjwatsonthe error here is close enough to the firmware call that I don't think it's likely that this is our bug13:05
Kalidarncjwatson: yeah that's rather odd because ive burnt it twice (two dvds) and the drive does work as other distros have no issue13:07
Kalidarnso ill try booting off a usb stick13:07
cjwatsonKalidarn: well, it could be that other distros just happen to miss the problematic bit, or maybe Linux tries harder to read it than your BIOS does and the other distros have no need to read that sector with raw firmware calls13:08
cjwatsonKalidarn: sadly, experiment does not actually rule out faulty drive/media13:09
Kalidarnthis includes previous versions of kubuntu such as quantal or ubuntu so yeah13:09
cjwatsonKalidarn: sure, but it could depend on exact position of data on the disk13:09
Kalidarnill try a different type of media entirely and see if it occurs, the debian wheezy bug (pre RC1) happened the same to me on both optical and usb drive13:09
cjwatsonKalidarn: drive cleaning kits are IME worth a shot as well, but yes, you probably stand a better chance with USB13:10
Kalidarnyeah, i doubt the drive has anything wrong with it. but i guess ill know soon enough13:10
Kalidarnit's just rather odd i only seem to be having that issue with raring ringtail13:10
cjwatsonthe boot loader code in question hasn't changed for a year or more (I did go and read it before replying to you).  Random chance can produce odd things sometimes13:12
Kalidarni guess :) time for more experimentation! :D13:12
cjwatsonthe boot loader code *is* Ubuntu's responsibility, but I think in this case whatever the bug actually is is out of our hands13:13
Kalidarni figured at that point it wouldn't matter what variant of buntu was being used.13:13
dholbachlool, ready?13:14
cjwatsonKalidarn: the boot loader code is identical, but the different flavours of Ubuntu might happen to have the kernel in a different position on the disk13:15
cjwatsonwhich in this case could make a difference13:15
looldholbach: eh was just joining #ubuntu-on-air and just moved the invite 5 mn earlier to make sure people join on time13:16
Kalidarnthanks for your time cjwatson.13:17
stokachucjwatson: hey did you see my messages from last night? (not sure if you logged off to sleep by then)13:20
cjwatsonOh, I did but hadn't quite got round to them yet - I'll look shortly, thanks13:21
stokachucjwatson: ok no problem just making sure they made it to you13:21
cjwatsonstokachu: We're before final freeze (just), so I'd like to get the raring fix in if possible13:21
cjwatsonSince it ought to be there before precise13:21
stokachucjwatson: ah ok, ive got everything attaached to the bug and sru template done13:22
stokachucjwatson: so not sure if you want to just pull that raring one in before freeze13:22
cjwatsonRight, I see.  I will stare at it a bit13:23
cjwatsonmlankhorst: http://paste.ubuntu.com/5718775/ is a rather bigger diff than the changelog suggests - is that intentional?13:41
cjwatson14:37 <seb128> tjaalton, slangasek, Laney: the libgl1-mesa-dri update makes unity segfault on start in vms13:41
cjwatsonmlankhorst: ^- and is it likely to fix that?13:41
mlankhorstare they i386 vms?13:44
seb128mlankhorst, yes13:44
cjwatsonthe one I tried was13:44
=== security is now known as megha
mlankhorstcjwatson: it was a result of a merge back to ubuntu branch from ubuntu+1, the patches that were dropped were already no longer applied.13:44
mlankhorsthm I think it might13:44
mlankhorstI have it on my ppa anyway13:45
seb128mlankhorst, do you have a deb handy ?13:45
rbasakWould it be worth sorting the rebuild failure reports in popcon order? I'm still struggling to prioritise what to look at.13:46
Laneypopcon doesn't get updated any more13:46
rbasakHow about Debian popcon?13:46
seb128cjwatson, mlankhorst: libgl1-mesa-dri_9.1.1-0ubuntu3~ppa1_i386.deb from that ppa fixes it13:47
mlankhorstand what I expected13:47
seb128mlankhorst, still a bit annoying that this slept through, we should have at least one people running unity under a vm on i386 and amd64 before upload13:48
seb128mlankhorst, thanks for the fix ;-)13:48
mlankhorstseb128: it was a case of conflicting symbols specifically for i38613:49
seb128mlankhorst, well, it means nobody tested on i386...13:49
mlankhorstand only happened specifically on nouveau < nvc0, or llvmpipe i38613:49
=== wedgwood_away is now known as wedgwood
freeflyingwonderding do we have latest kde ppa for 12.04?14:01
freeflyingsorry, wrong channel14:02
mitya57freeflying: ppa:kubuntu-ppa/backports14:04
freeflyingmitya57: thanks, typed in errors here, meant to ask in kubuntu-devel :)14:04
Sweetsha1kachiang: ping?14:20
=== Sweetsha1k is now known as Sweetshark
achiangSweetsha1k: hey, in a hangout-on-air now, but what's up?14:21
slangasekmlankhorst: so what's the plan for getting the fixed mesa uploaded?14:21
mlankhorsterm it's already been uploaded before everyone was panicking about it ?14:22
mlankhorstso I guess poking you until you accept it14:22
mlankhorstoh was already accepted 7 minutes ago14:23
mlankhorstno plans, then..14:23
Laneythe plan is to kick back with a nice jug of sangria14:23
mlankhorstmmm I think I'll go biking14:24
mlankhorstwhile the weather is nice14:24
Laneyso dutch14:24
mlankhorstand the storm hasn't calmed down yet14:24
mitya57running ReText under qt5 makes gnome-session crash... interesting14:48
mitya57s/gnome-session/Xorg/g, which is even more interesting14:49
* mitya57 installs Xorg dbg symbols, fastens seat bells and tries again15:19
bdmurrayslangasek: could you have a look at bug 1169621?15:22
ubottubug 1169621 in plymouth (Ubuntu) "encrypted LVM desktop does not boot with cirrus driver (no password prompt)" [High,New] https://launchpad.net/bugs/116962115:22
xnoxbdmurray: i can test it again. there have been updates to kernel and/or qemu as e.g. background is now colorful.15:23
slangasekbdmurray: that's been a problem for a couple of cycles, IIRC there was a change in the kernel that triggered this... it's not going to get fixed for r15:26
bdmurrayslangasek: got it, thanks15:27
mitya57FWIW I've found the issue: it's bug 1005677, for which we have a patch only in Qt 4, not in Qt 5.15:36
ubottubug 1005677 in overlay-scrollbar (Ubuntu Quantal) "Re-emergence of "Gtk-CRITICAL **: IA__gtk_widget_style_get: assertion `GTK_IS_WIDGET (widget)'" Makes vlc and other Qt apps crashing crashing" [High,Fix released] https://launchpad.net/bugs/100567715:36
GunnarHjcjwatson: ping?15:55
cjwatsonGunnarHj: pong15:55
GunnarHjcjwatson: Hi Colin. I just posted a comment on bug 1160441. I do disagree on that change.15:56
ubottubug 1160441 in ubiquity (Ubuntu Raring) "Calendar is still in English despite French is selected as the Language during the installation" [Medium,Fix committed] https://launchpad.net/bugs/116044115:56
cjwatsonSigh, "not discussed with you" != "without discussion"15:57
GunnarHjcjwatson: Ok, true, but...15:57
cjwatsonI can't wait indefinitely for feedback about every change15:58
cjwatsonYou haven't actually refuted my point about LC_TIME being a conflation of language-dependent and language-independent data15:58
cjwatsonglib and indicator-datetime notwithstanding, anything that does even just something as simple as ctime() will have day/month abbreviations from the wrong language16:00
cjwatson"wrong", anyway16:00
GunnarHjcjwatson: It's true, no doubt. But given that we won't change the fundamentals easily, such as splitting LC_TIME into two locale categories, we need to do our best to meet user expectations.16:00
cjwatsonI think day/month from "wrong" language is more likely to break those expectations than other parts of the format16:00
GunnarHjcjwatson: Possibly. But the conflict typically gets visible in the calendar, and I have an idea - admittedly hackish - how to deal with that.16:02
cjwatsonI really profoundly disagree with the notion of hacking around locale categories in individual applications16:02
cjwatsonAll it will do is introduce inconsistency among applications16:03
cjwatsonpsivaa: ^- since this was your bug16:03
cjwatsonbdmurray: ^- and you were investigating it16:03
cjwatsonIf I revert this for raring, I'm not sure how anything will change in future releases; we will still have the fundamental issue of a conflated locale category16:04
GunnarHjcjwatson: Well, it's better IMO than doing nothing. At the same time I think that doing nothing is better than preventing the users from controlling the date and time format, which is what LC_TIME primarily is about.16:06
cjwatsonI'm not preventing users from doing anything!16:06
cjwatsonThey can change the categories themselves if our guess (and it can be no better than a guess) was wrong16:07
GunnarHjcjwatson: Well, currently they will do so automatically if they use language-selector to set the region. So it's inconsistent.16:07
cjwatsonIf we start changing individual applications then we're just going to have a succession of bugs like the one psivaa reported; the system will get more complex as we add more and more and more manual workarounds16:08
cjwatsonThis is how things get to the point where nobody understands them16:08
bdmurraycjwatson: I believe the change makes sense16:08
cjwatsonI agree that we have an inconsistency here16:08
cjwatsonThat's the only reason I'm considering reverting16:08
cjwatsonIf I reverted for raring, I haven't seen any reason yet why I wouldn't put the change back in the first upload for S16:08
cjwatsonAnd I'm not at all convinced that I would consider that indicator-datetime change acceptable for raring16:09
GunnarHjcjwatson: At least it would give us a possibility to consider the issue more carefully.16:10
cjwatsonUnfortunately we have already changed something from quantal, namely the mixed-locale improvements in ubiquity, and the handling of LC_TIME was one of them16:10
cjwatsonSo we don't get to say "let's just leave it how it was in quantal and consider more carefully later"16:11
GunnarHjcjwatson: But language-selector has considered LC_TIME a region thing for many, many cycles.16:12
cjwatsonAnd we probably only didn't notice that was a problem because relatively few people set their language through language-selector rather than setting it once in the installer and leaving it there.16:12
cjwatsonSo it didn't come up in this kind of test.16:12
GunnarHjcjwatson: Those who distinguish between language and region have typically used language-selector, I think, considering that the installer only lately has made a similar distinction.16:14
xnoxGunnarHj: i live in the uk, but on many machines want Russian UI, and that means my calendar should say Четверг and not Thursday. Just because my current timezone is here, doesn't magically make me understand that language.16:14
cjwatsonPerhaps.  Some of them have probably set the locale categories manually ...16:14
GunnarHjcjwatson: That too.16:14
xnoxGunnarHj: Or are you proposing that we print time in German, when the timezone is set to Berlin? even if the rest of the UI is French?!16:14
cjwatsonxnox: Gunnar is proposing that we do the language parts of this at the application level, I believe16:15
cjwatsonWhich I think is really dangerously wrong16:16
cjwatsonFor reasons given above16:17
xnoxcjwatson: I mean the ultimate incornation of this bug is how currencies are displayed by default in Libreoffice calc. Cause when a Russian UI in the UK one would want £ currency & Четверг as name of the day.16:17
cjwatsonNo, don't drag currencies into this16:17
cjwatsonThose are LC_MONETARY which is different16:17
cjwatsonI don't believe anyone disagrees that LC_MONETARY should be location-dependent16:18
cjwatsonAnd it is, with current installer and language-selector code16:18
xnoxok, good.16:18
GunnarHjcjwatson, xnox: Personally I think I won the debate at https://bugzilla.gnome.org/687945, but Matthias had access to the button...16:20
ubottuGnome bug 687945 in i18n "Display names of days and months using the current language" [Normal,Resolved: wontfix]16:20
cjwatsonGunnarHj: Exactly the same argument applies to glib as to applications - it's the wrong place, fixing this belongs at the standards / C library level16:20
cjwatsonWhich is certainly harder, but ...16:21
GunnarHjcjwatson: So the question is what's the best thing to do until the standards are changed.16:21
xnoxGunnarHj: the questions is did you raise it for standards to consider fixing yet?16:22
Kalidarncjwatson: works off USB ;)16:22
cjwatsonKalidarn: excellent16:22
Kalidarni should try another cd drive actually.16:22
Kalidarncos i don't believe the media is bad.16:22
Kalidarni don't like problems that go away by themselves.16:23
Kalidarn(especially as two seperate discs had exactly the same issue)16:23
Kalidarni wouldn't mind betting though cjwatson it's probably my dodgy BIOS16:23
GunnarHjcjwatson: I have discussed the issue quite a lot the past few months. Winows and Apple are said to fix the distinction in accordance with the users' expectation, i.e. despite of the standards.16:24
Kalidarni've had nothing but trouble with this GA-X58A-UD3R16:24
GunnarHjxnox: No, I haven't. Isn't that a 'mission impossible'? ;-)16:25
xnoxGunnarHj: i haven't pushed anything into C std library, but e.g. ubuntu community did push a few things into other standards and languages.16:26
cjwatsonGunnarHj: I really don't see how Windows or Apple are relevant to a discussion of POSIX standards :-)16:26
cjwatsonSure, they're big OSes, but they're not exactly well-known for POSIX compliance in general16:27
Kalidarnisn't OSX more posix compliant than linux?16:27
cjwatsonGunnarHj: If we don't try then *certainly* nothing will happen16:28
xnoxGunnarHj: it's a valid problem, and needs a solution that works =) standards committees are suppose to be good at resolving such things, or at least defining/clarifying the expected when mixed LC_* locales are set.16:28
xnoxs/expected/expected behaviour/16:28
GunnarHjcjwatson: Their success is probably partly because they set user expectation before bad standards.16:28
cjwatsonGunnarHj: Sigh, I guess this discussion is useless if we're going there16:29
cjwatsonFalse dichotomies 'r' us16:29
GunnarHjcjwatson: For now, can't you please take a step back and revert?16:30
cjwatsonGunnarHj: I'll revert this change in the installer for raring, but only because it has additional interactions I hadn't thought of which are now too late for 13.04.  I intend to reinstate it as soon as raring is out.16:30
cjwatsonUnless there is a better option, and I don't count application-level changes ...16:30
GunnarHjcjwatson: Good, then I can sleep well tonight, at least. ;-)16:31
psivaacjwatson: sorry was still trying to understand the conflict and the inconsistency. i like the correct language to be displayed but if that's going to change the timezone, then i dont have a preferance :)16:31
cjwatsonpsivaa: It's not about changing the timezone16:31
jtaylorbarry, doko: ubuntu python now has native access to the multiarch tuple right?16:32
jtaylorwhere was i again?16:32
jtaylorsys._multiarch is only py2 :/16:32
dokojtaylor, depends on what you want to use it for16:32
jtaylorto find tk/tcl16:32
dokoif you can, use sysconfig.get_config_var('MULTIARCH')16:33
jtaylorok seems to work, thx16:33
psivaacjwatson: ok, I think its safe for me to leave the decision to you guys then :)16:35
jtayloror is there a compat package one can use for tk/tcl build dependencies?16:35
cjwatsonGunnarHj: Reverted. :-(  Now I really do have to go.16:36
cjwatsonOh blast, I have to wait until localechooser is approved before reuploading ubiquity.16:37
cjwatsonSo that will probably miss final freeze now.16:37
nemoHrm. I wish ubuntu software centre offered a way for devs to get in contact w/ users who give bad reviews16:37
GunnarHjcjwatson: Thanks. :)16:37
stgrabercjwatson: I can review it now if you want16:37
nemoI mean. I don't *care* that much, I just feel sorry for poor "John" who was having trouble starting the game which was almost certainly due to bad gfx driver16:37
nemoand could probably have been fixed w/ application of jockey-gtk16:37
nemoand might be having bad exp w/ other games too16:38
xnoxnemo: wrong channel =)16:38
stgrabercjwatson: accepted (confirmed that diff from ubuntu2 to ubuntu4 is only removal of .gitignore)16:38
nemoxnox: oh?16:38
xnoxnemo: i'm not sure where you can discuss apps published in the software center. Wait is that about a review on a package from Ubuntu OS or about an app you published in Software Center as a developer?16:39
nemoHedgewars. 2nd FOSS game in Games category :)16:39
nemoxnox: but. it wasn't really about the game itself16:40
nemowas more about ubuntu software centre - I wish it offered a way for me to somehow help john is all16:40
nemoevery time I go to the game, his review is there, and I feel bad16:40
xnoxnemo: hmmm...16:40
nemoI know what is happening. hwengine is crashing.  which is usually due to opengl probs, thus need for another driver. well, it sometimes is 'cause people screwed w/ sound system or pulseaudio is crashing16:41
nemobut john doesn't seem like the type to screw w/ sound system, and pulseaudio is better behaved these days16:41
nemoif john had linked to a launchpad issue, I would have commented there :)16:42
nemobut given cjwatson's complaints yesterday, I guess I shouldn't talk about filing issues :-p16:42
stokachucjwatson: that version change you made in rsyslog was that the only thing I should be aware of? i couldnt find versioning schemes for development in the wiki anywhere16:46
nemoxnox: and. I can't just write another review rebutting him, since I already did that once for the guy who said we work better on windows machines :D :D16:47
nemoer. s/rebutting/replying/  - my first review was a rebuttal./16:47
cjwatsonstokachu: Yeah16:49
cjwatsonstokachu: dch -i usually does the right thing for development releases16:49
stokachucjwatson: ah ok, yea it did do that but i manually altered it :X16:50
sabdfl let me know which is the best image version to demo on N4 and N10?16:55
=== mmrazik is now known as mmrazik|afk
=== deryck is now known as deryck[lunch]
=== deryck[lunch] is now known as deryck
weaselplease excuse my intrusion, but does ubuntu/canonical have porting machines that give developers various chroots to interactively debug stuff?20:27
roadmrweasel: not to my knowledge :/ I may be wrong though...20:33
weaselwhat a shame.  I wondered how they were maintained :)20:33
infinityweasel: We do internally, yes.20:34
weaselISTR elmo mentioning many years ago some tool that gives otherwise unprivileged developers the means to install packages from the archive in a reasonably secure way20:35
weaselbut I can't find that email anywhere20:35
infinityweasel: chapt-get20:35
infinityOr, no.  What did I name that project?20:35
* infinity goes hunting.20:35
infinityrapt.  That's it.20:36
infinityFailing old brain.20:36
infinityweasel: https://launchpad.net/rapt20:36
weaselnot packages for debian.  what a shame20:36
infinityweasel: It ain't pretty.  Just a quickie hack by mvo and I over a few days/weeks.20:36
infinityweasel: But it basically does the job.20:36
weaselyeah, we're mostly worried about tty/stdin interaction during the install process20:37
infinityweasel: The idea is to install it as /usr/local/bin/apt-get and then provide sudo access to it.20:37
weaselor at least that was one obvious attack vector20:37
infinityWhich is sketchy.20:37
infinityBut less sketchy than giving someone apt-get raw.20:37
infinityThough, it might not meet your use-case.20:37
infinityOur use case was "we don't want people removing packages", basically.20:38
infinityNot so much about security as developers not stomping on each other.20:38
weaselhmm.  might not be a perfect fit then20:38
weaselnot too different from the apt-in-chroot wrapper we already have for porters20:39
infinityPossibly not, no.20:39
weaselI'm just glancing over the code, but there's nothing stopping me from say installing a pager, apt-listchanges, and then execing a shell from the pager while apt-listchanges shows me stuff, right?20:39
weaselah.  there's a pty.fork()20:40
weaselthat's good20:40
hallyninfinity: bug 1170489 , does that suggest we should always have group admin in /etc/group?20:51
ubottubug 1170489 in libvirt (Ubuntu) "libvirt-bin postinst can try to add non-system group members to libvirtd group" [Undecided,New] https://launchpad.net/bugs/117048920:51
stgraberubuntu@lxc-testing01:~$ grep admin /etc/group20:52
stgraberhallyn: ^ clean raring system20:52
stgrabermy guess is that you probably want to look at the sudo group instead20:53
stgraberassuming you want the list of people who are able to become root on a standard ubuntu system20:53
hallynstgraber: the problem is the system may have been installed with lucid and upgraded20:53
hallynso libvirt postinst does both groups admin and sudo20:54
hallyn(i originally switched to only sudo, but mdeslaur pointed out the problem with that)20:54
stgraberhallyn: hmm, then it depends what you want to get, if you just want the local users and ignore network sources, just parse /etc/group directly. If you don't care about network group membership but want to check that the group exists locally, then use grep -q + getent group20:55
hallynwas pinging infinity bc he originally did the switch from grep to getent, so he might have thought about it already and know of a reason why it's a non-issue20:55
hallyni haven't used NIS since 1998 on an iris box...20:56
hallyncan't quite decide if, if you give yourself an NIS group called 'admin', how that's supposed to be handled20:57
stgraberah, actually, I thought NSS would aggregate when the group is provided by more than one backend, but it's not, it just returns the first one, so if you have the group in /etc/group + NIS, it'll just return the members listed in /etc/group20:58
hallynwhat if you list NIS before files?20:58
hallyncourse, then, again, it's what you wanted...20:58
stgraberso if you want to fix what's described in this bug, you can get away with "grep -q admin /etc/group && getent group admin" (and same for sudo)20:58
hallynbut do i want to :)20:59
stgraberyeah, if you list NIS before files, then if the group exists in NIS only those members will be returned, even if you have some extra in /etc/group locally20:59
infinityhallyn: I'm puzzled as to what the bug is.21:01
hallynso if you do have an nis group called admin, why shouldn't those users be added to group libvirtd?21:01
infinityhallyn: I've never seen someone complain before about NIS working exactly as advertised.21:01
hallynthat's bc it's been 15 years since anyone used it, working or not21:02
stgraberso usually people don't really like postinst scripts adding possibly hundreds of network users directly to the local /etc/group21:02
stgraberand I think that's what the reporter is complaining about21:03
infinityIt's only a complain because it's an ambiguously vague group name.21:03
hallynstgraber: but won't adduser use NIS to add the users to (NIS) group libvirtd21:03
infinityhallyn: It can, depending on how you've set it up.21:03
infinityBy default though, no.21:03
stgraberif you have a company with a NIS (or LDAP or whatever) group called "admin" with users in there and don't have the group locally (because it's a clean raring system), then all those users will end up being hardcoded in /etc/group21:03
stgraberso yeah, I guess the grep + getent change would be reasonable. It won't cause any change for standard systems and for systems using network auth, it won't give extra rights to "random" users.21:05
hallynwell if we do want to undo this, i'd say falling back to 'grep "^admin:"' makes more sense than using both grep and getent21:06
hallynIF we want to undo it21:06
pedahzurI am trying to use a latest mainline kernel to debug an issue.  The 3.9-rc6 has a linux-image-extra package, but 3.9-rc7 does not.  Has everything in the extra package been integrated into the main kernel package?21:32
gotwigDoes anyone know something about GeoClue?22:24
gotwigits death, isnt it? No maintainer, no new code, no bug fixes for several months22:24
gotwigtvoss, hey there22:30
tvossgotwig, about to leave :) how can I help, though?22:30
gotwigtvoss, hallo erstmal ;D22:31
gotwigtvoss, I saw your blueprint about geoclue222:31
gotwigtvoss, do you work on it, or is it death²?22:31
tvossgotwig, the blueprint itself is alive, geoclue2 as presented on the bp is quite unlikely at this point22:31
=== kentb is now known as kentb-out
=== salem_ is now known as _salem
=== hggdh_ is now known as hggdh
=== wedgwood is now known as wedgwood_away

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