[04:52] <alkisg> Good morning
[04:53] <alkisg> attente, seb128: I'll be around for hours, trying to help in the keyboard layout switching thing, please ping me if you have patches for me to test, and I'll be trying to provide patches as well. Thank you.
[05:21] <Mirv> seb will probably be around in 2.5 hours
[07:39] <darkxst> pitti, bug 1314441
[07:39] <ubot2> Launchpad bug 1314441 in gobject-introspection (Ubuntu) "add GI marshalling test interface" [Undecided,New] https://launchpad.net/bugs/1314441
[07:41] <pitti> hey darkxst
[07:43] <pitti> darkxst: ah, there's no 1.40.1 with that yet? I'll sponsor the utopic package then
[07:43] <pitti> darkxst: and the same as 2ubuntu0.1 for trusty-proposed, I figure?
[07:44] <pitti> oh wait, it's -1 in trusty; but I'll deal with that
[07:45] <darkxst> pitti, right there was no g-i release with that yet
[07:46] <darkxst> and thanks
[07:47] <pitti> darkxst: done
[07:57] <darkxst> pitti, also bug 1314432, we should just re-sync with debian here? right?
[07:57] <ubot2> Launchpad bug 1314432 in modemmanager (Ubuntu) "[systemd] Modemmanager missing unit file" [Undecided,New] https://launchpad.net/bugs/1314432
[08:04] <pitti> darkxst: we might still need http://launchpadlibrarian.net/167591018/modemmanager_1.0.0-2_1.0.0-2ubuntu1.diff.gz in case it fails again on ppc64el
[08:04] <pitti> darkxst:  but we can try with a sync first, yes
[08:05] <Laney> guten morgen
[08:05] <pitti> hey Laney, wie gehts?
[08:06] <Laney> pitti: müde, aber okay, danke
[08:06] <Laney> und du?
[08:07] <seb128> good morning desktopers
[08:07] <seb128> hey Laney pitti
[08:07] <pitti> Laney: mir gehts gut, danke!
[08:07] <pitti> bonjour seb128
[08:08] <seb128> Laney, du -> dir?
[08:08] <seb128> pitti, lut
[08:08]  * pitti applauds seb128
[08:08] <seb128> ;-)
[08:08] <Laney> yeah?
[08:08] <Laney> I thoguht I was using the nominative case
[08:12] <mlankhorst> morning btw :p
[08:16] <rsalveti> xnox: updated bug https://bugs.launchpad.net/ubuntu/+source/android/+bug/1305315
[08:16] <ubot2> Launchpad bug 1305315 in gcc-i686-linux-android (Ubuntu) "Android container fails to start when built with the gcc-i686-linux-android toolchain" [Undecided,New]
[08:16] <rsalveti> ops, this was for #u-devel
[08:16] <pitti> Laney: no, it's the dative; "Mir" gehts gut
[08:17] <pitti> Laney: "ich" gehe gut -> that's the actual walking
[08:17] <Laney> 'ich bin müde' … und ?
[08:18] <pitti> Laney: there the "ich" is the subject indeed, so it's Ich/Du
[08:18] <seb128> Laney, I though you were referring to the "wie gehts?"
[08:19] <Laney> yeah I thought that ich bin <something> was a normal way to reply to that
[08:20] <pitti> Laney: so walking: "wer geht?" (subject); for inquiring the object: "wem geht es gut?" or "wem gehoert der Apfel"? -> dative
[08:21] <pitti> that bit confused me in French -- "je vais à cafe" and "je vais bien" is exactly the same, although two different meanings of aller
[08:21] <pitti> ("au cafe")
[08:22] <pitti> and café, argh :)
[09:00] <darkxst> pitti, oh, gjs autopackage tests failed with the new g-i, have upload gjs update which should fix it ;)
[09:01] <pitti> darkxst: sweet, thanks; curious that it fails on an additional test API?
[09:03] <darkxst> pitti, may have just been broken? no idea why that triggered it though https://git.gnome.org/browse/gjs/commit/?id=a6d342ba894522c62f3f7c75ebc97100c2b9edfe
[09:05] <darkxst> or maybe that test was just not running, due to the missing API! and that patch is just a white herring
[09:06] <darkxst> red even
[09:09] <darkxst> pitti, oh this is odd? https://jenkins.qa.ubuntu.com/view/Trusty/view/AutoPkgTest/job/utopic-adt-gjs/ARCH=i386,label=adt/6/console
[09:11] <pitti> darkxst: known bug, I'm on it
[09:11] <pitti> darkxst: I retried the test
[09:15] <mlankhorst> xnox: oops missed a spot
[09:15] <mlankhorst> i figured some of the files were autogenerated, but they weren't
[09:15] <mlankhorst> there we go, at least it tries now :P
[09:28] <Laney> did we forget to fix/update the evolution ubuntu one mail?
[09:28] <Laney> https://bazaar.launchpad.net/~ubuntu-desktop/evolution/ubuntu/view/head:/debian/patches/09_add_ubuntuone_email.patch
[09:28] <seb128> Laney, do we have u1 mention in the default email?
[09:29] <seb128> Laney, seems we did indeed
[09:30] <Laney> just drop?
[09:30] <seb128> yes
[09:30] <seb128> none of the things listed there are still a thing afai
[09:30] <seb128> k
[09:30] <seb128> evo is not even our default mailer anymore
[09:35] <Laney> I'm not sure that patch even work
[09:35] <Laney> s
[09:35] <seb128> seems another reason to drop it ;-)
[09:36] <Laney> yes I was checking to SRU it
[09:37] <seb128> let me check on my test laptop as well
[09:38] <Laney> just tried in a precise & trusty VM with clean evolution profiles and neither of them had the message
[09:38] <Laney> I'm assuming the 'On this computer' inbox is where it's supposed to be
[09:39] <seb128> I'm surprised it's not working in precise
[09:39] <seb128> I though we had it tested there back then
[09:52] <mlankhorst> ugh xkb-data is evil :P
[10:07] <seb128> Laney, yeah, I don't see u1 emails here either in trusty
[10:09] <Laney> cool (but bad in another way), no need to SRU that then
[10:10]  * Laney fixes hunspell-en-us
[10:26] <dpm> hi happyaron, around?
[10:38] <happyaron> dpm: hey
[10:38] <dpm> hey, how are you doing?
[10:39] <happyaron> fine, :)
[10:39] <dpm> excellent, thanks so much for the translations in scopes!
[10:39] <happyaron> np, :)
[10:40] <dpm> I've just sent an e-mail with the latest one we've enabled for translation. Sorry for these coming piecemeal instead of all at once, but I think we should now be good to go with i18n in scopes. If you've got the chance, do you think you could look at translating these new 8 strings I sent?
[10:42] <happyaron> sure
[10:43] <happyaron> ah, timeout and F5
[10:44] <GunnarHj> dpm: Hi David, is there a near deadline for those translations?
[10:45] <dpm> great, thanks again happyaron!
[10:45] <happyaron> seems there's something wrong with LP atm.
[10:45] <mlankhorst> xnox: well mapping lwin + rwin has been a mess, no luck so far :P
[10:47] <dpm> hi GunnarHj, not really. For the Simplified Chinese ones we're aiming at getting them done this week, as we'll be presenting the phone at Mobile Asia Expo. For all languages (including zh_CN), the translations should automatically land in the images as soon as new images are promoted
[10:47] <GunnarHj> dpm: Aha, so that's why you are pushing happyaron. :)
[10:47] <dpm> GunnarHj, asking, not pushing ;)
[10:48] <GunnarHj> dpm: ;)
[10:52] <happyaron> dpm: done
[10:53] <dpm> awesome thanks happyaron!
[10:54] <dpm> happyaron, do you happen to have an Ubuntu phone, or have you run the emulator to see what the status of the zh_CN native language support is?
[10:54] <happyaron> nope
[10:57] <mlankhorst> xnox: hah it works!!
[10:58] <mlankhorst> but I have to redefine space, no idea if that breaks anything
[11:00] <mlankhorst> xnox: http://paste.debian.net/96534/ -- but some locales define a 'no break space' which wouldn't work with win_space_toggle
[11:03] <mlankhorst> or even worse latvia ndefines other keys on top of the space bar ;P
[11:09] <om26er> seb128, Hi!
[11:09] <om26er> seb128, can you please get someone to look into this bug 1304285 ?
[11:09] <ubot2> Launchpad bug 1304285 in network-manager-applet (Ubuntu) "nm-connection-editor crashed with SIGSEGV while importing OpenVPN settings" [High,Confirmed] https://launchpad.net/bugs/1304285
[11:13] <mlankhorst> some other languages do too, but hey if you want win_space toggling there you have it ;-)
[11:32] <xnox> mlankhorst: most Latvians use apostrphe variant to be honest, and the latvian layout is not used (nobody knows how to type on it)
[11:33] <mlankhorst> xnox: yeah but just warning that it may break some keyboards
[11:35] <mlankhorst> if they expect a non-breaking space
[11:35] <mlankhorst> but honestly I don't have a clue how common that is :P
[11:48] <mlankhorst> xnox: can you test? it appears to work locally
[11:58] <seb128> om26er, hey, it's already assigned to cyphermox did you try to check with him?
[11:58] <om26er> seb128, I assigned that so that it appears in his email. I am waiting for him to wake up.
[11:59] <seb128> k
[12:50]  * work_alkisg is writing down all keyboard layout issues starting from the installation and up to after manually configuring the keyboard layout, in http://goo.gl/1lx0jz.
[12:51] <alkisg> I've written 13 separate issues so far
[12:51] <alkisg> All recent issues, they were never there before gnome decided to override xkb... :(
[12:51] <alkisg> About half of them are Ubuntu-specific
[12:52] <alkisg> Tomorrow I'll start testing the patches, to see which patch solves which bugs :)
[12:57] <seb128> alkisg, thanks, your overstatements about the issues or how they are not looked at doesn't help there though
[12:57] <alkisg> seb128: which ones? I can give you write access if you could spend a few minutes to delete them
[12:58] <alkisg> I don't want to overempasize things
[12:58] <seb128> alkisg, well the end of your introduction about the many launchpad bugs not receiving the attention they deserve
[12:58] <alkisg> Ah, there are about 100 bugs that are around for years
[12:58] <alkisg> I don't think it's an overstatement, but I can delete it
[12:59] <seb128> well, that's true from any project/bugtracker/topic
[12:59] <xnox> alkisg: just delete introductory paragraph. the rest is very useful.
[12:59] <alkisg> Done
[12:59] <seb128> launchpad bug numbers are over 1M
[12:59] <seb128> the team is small compared to that
[12:59] <alkisg> Deleted the intro
[12:59] <seb128> thanks
[12:59] <alkisg> What I wanted to avoid is, the quick "file bugs" "solution"
[13:00] <xnox> is it at all possible to use keyboard combos to change keyboard layouts on the console?
[13:00] <xnox> there is no X running, so how would that work?!
[13:00] <alkisg> I can only provide patches for a few of them, I'd need help for many of the rest...
[13:00] <seb128> we need help as well
[13:00] <alkisg> Understood
[13:00] <xnox> oh, alt-shift works, hm, i have no clue how that works.
[13:00] <seb128> some of those issues are also limitation reached by the GNOME design choices/xorg
[13:00] <alkisg> xnox: I think the kernel handles some basic layout switching stuff
[13:01] <alkisg> Through setupcon etc
[13:01] <alkisg> seb128: I think only [10] is there in fedora 20, the rest of them are solved
[13:01] <alkisg> I.e. the "apps grabbing the keyboard" thing
[13:03] <seb128> alkisg, lot of those issues seem to be the same bug
[13:03] <seb128> alkisg, "the indicator doesn't pick changes done through xkb cycling"
[13:04] <alkisg> seb128: some of them might be, but I tried to only list the ones that _might_ not be the same bug
[13:04] <alkisg> In cases I was 100% sure it's the same bug, I didn't write it... anyway I'll spend more days re-writing that, as I gather more info about how patches affect those issues
[13:05] <alkisg> I'll also link to existing bugs in launchpad, whenever I can find them
[13:05] <seb128> ok, thanks
[13:06] <alkisg> So what I'd like from you guys, is to provide patches in any of those issues I list that you know your way around that code and can easily pinpoint the affecting lines
[13:06] <alkisg> And I could compile/test them...
[13:07] <seb128> alkisg, start by filing bugs reports (no need if there are already bugs about those issues) and pointed the bug numbers here
[13:07] <seb128> we can then work on them in order
[13:08] <alkisg> OK, will do that tomorrow (it's getting kinda late here). Thanks a lot!
[13:08] <seb128> thank you for working on those!
[13:08] <om26er> seb128, who to talk about X crashes ?
[13:08] <seb128> om26er, mlankhorst
[13:09] <om26er> mlankhorst, Hi!
[13:09] <om26er> seb128, thanks
[13:10] <om26er> moved to #ubuntu-x
[14:03] <kenvandine> i can't decide... update my desktop or phone to utopic first...
[14:04] <didrocks> kenvandine: or both? :)
[14:05] <kenvandine> too scared :)
[14:06] <seb128> kenvandine, update the phone, you don't need it to get work done ;-)
[14:11] <didrocks> kenvandine: update the laptop, you don't need it as well to get work done ;)
[14:12] <didrocks> just code by thinking :p
[14:12] <kenvandine> hehe
[14:12]  * seb128 stands to the "the LTS needs to be tested as well"
[14:16]  * kenvandine starts small, creating a schroot for sbuild :)
[14:19] <seb128> that seems a good step 1!
[14:20] <Laney> I upgraded because I accidentally did sbuild -d utopic and couldn't be bothered to rebuild it for trusty
[14:20] <kenvandine> that was too easy... created and built libphonenumber in it already!  maybe i need to just upgrade :)
[14:20] <Laney> and I got gtk 3.12 out of my local repo and now have borked dialogs
[14:20] <Laney> fun
[15:41] <mlankhorst> seb128: but a crashing bt attached with gdb /usr/bin/Xorg $(pidof Xorg) + info locals would help me a lot too
[15:41] <mlankhorst> if valgrind doesn't work
[15:42] <seb128> mlankhorst, don't you have a bt in the apport retrace?
[15:44] <mlankhorst> well valgrind would be best
[15:44] <seb128> well, I don't get errors in there :/
[15:44] <seb128> not others than the ones from the log I had yesterday at least
[15:44] <mlankhorst> valgrind says screen = NULL, which is weird..
[15:45] <mlankhorst> just for fun can you try a vt switch?
[15:45] <seb128> I keep vt switching
[15:46] <mlankhorst> hm
[15:47] <seb128> I've my valgrind log displays on a vt
[15:47] <seb128> so I play with xorg and go to the vt to see the log and come back
[15:47] <mlankhorst> ah i simply log to a file in append mode
[15:48] <seb128> right, you just need to tail the log from somewhere
[15:48] <mlankhorst> can you try with pointer barriers? just for attempting
[15:48] <seb128> or open it
[15:48] <seb128> I don't have a multiscreen
[15:49] <mlankhorst> you also get pointer barriers if you tell the dock to hide
[15:50] <seb128> well, the touchscreen gets in weird state when running under valgrind
[15:51] <seb128> like I can't left click anymore
[15:51] <seb128> but I think that might be another old/known issue
[15:51] <mlankhorst> I thought that was fixed :/
[15:58] <seb128> me too
[15:58] <seb128> well it happens under valgrind
[15:58] <seb128> instead of the segfault...
[15:59] <mlankhorst> hm funstuff, I'll prepare a xorg-server 1.16rc2 in some ppa tomorrow, at least that should give us another data point
[16:01] <seb128> yeah
[16:02] <mlankhorst> nothing in there looks like it would fix anything though, grr
[16:03] <mlankhorst> afk, food!
[19:18] <deviantp> Hey guys, quick question at work I've got an Ubuntu install for some testing, when I plug in a PCI-e SSD I get dropped into an initramfs shell saying the UUID of the boot disk can't be found. Doing a blkid shows the "missing" UUID is the same as device /dev/sdd5. Usually (and in other slots) the boot disk is  enumerated as /dev/sda5
[19:19] <deviantp> I didn't do a good job of explaining that, the boot disk is a normal HDD. The PCI-e ssd is supposed to be a secondary
[22:52] <xnox> if deviantp appears again redirect to myself or cking
[23:22] <xnox> mlankhorst: that paste from the morning is perfect!
[23:22] <xnox> mlankhorst: works like a charm.