[00:09] hey all, I just installed ubuntu 12.04 on a computer. When I turn it on, the log in page comes up. When I log in, it seems to hang. It shows the background and my mouse and nothing else. The desktop never comes up. Thoughts? [00:10] !support [00:10] The official ubuntu support channel is #ubuntu. Also see http://ubuntu.com/support and http://ubuntuforums.org and http://askubuntu.com [00:12] ty === Aww is now known as NotAww === NotAww is now known as Aww === Aww is now known as Nick[serv] === Nick[serv] is now known as Aww [05:29] Good morning [06:11] hey pitti, how are you? [06:11] (didn't look at IRC, lost in emails until now) [06:11] hey didrocks [06:11] didrocks: quite fine, thanks! how about yourself? [06:11] pitti: I'm good, thanks! [06:12] yay for another huge Mir thread [06:13] yeah, not a really productive one… === Aww is now known as EvilAww [06:28] didrocks: Sorry, was that my fault? Should I avoid the list in future? [06:32] duflu: we are not talking about the same thread I guess :) (the one on ubuntu-devel) [06:33] duflu: you didn't talk on that one? [06:33] didrocks: Good, no, different. Good morning then :) [06:33] (or maybe you did but your message is still moderated) [06:33] hey duflu! how are you? [06:33] didrocks: Good. You? [06:33] I'm good, thanks! [06:58] * didrocks soon to be renamed professional packages reviewer [07:04] bonjour [07:05] bonjour Monsieur mlankhorst, comment vas-tu ? [07:05] and the equivalent in english: sup? [07:06] let's say, the equivalent in the US Midwest :) [07:06] mlankhorst: hey! how are you? [07:09] es geht gut [07:14] good morning [07:15] salut jibel, ça va? [07:16] salut didrocks , bien et toi? [07:16] ça va [07:33] good morning desktopers [07:35] bonjour seb128 [07:35] pitti, salut, ça va ? [07:35] seb128: il fait très chaud; je vais bien, mais je dois manger beaucoup de glace :) [07:36] seb128: et toi ? [07:36] ici aussi il fait (trop) chaud [07:36] glace \o/ [07:38] * pitti -> out for a bit [07:38] pitti, bonne glace ! [07:38] not for glace, some errands :) [07:39] hehe [07:39] salut seb128 [07:39] didrocks, salut ! en forme ? pas trop chaud ? [07:40] seb128: si, chaud, enfin là, ça va encore mais d'ici 2/3 heures, ça va être la fournaise :) [07:40] et toi? [07:40] ça va, je profite de la fraicheur matinale ;-) [07:40] * seb128 wants temperate weather [07:40] not 16°C, not 35°C, just good old 25°C [07:41] heh [07:53] sil2100: no more "bootstrap" case now, you can add whatever you need after "automatic revision from…" apart from something containing: "(ppa:.*)" [07:53] which is only used for feature branches [07:57] \o/ [07:57] /o/ [07:57] \o\ [08:02] morn' [08:02] Laney, good morning [08:02] hey Laney [08:02] hey [08:02] how's it going? [08:02] I'm fine, thanks! yourself? [08:02] good! you? [08:03] had to get up at dawn to scare off some fighting birds :P [08:03] but otherwise good [08:10] lol, be nice to the birds! [08:12] heheehhehe [08:17] anybody else gets "self-signed certificate" warnings when using google online accounts? [08:17] maybe talk.google.com is an abandoned host? [08:21] asac, I get those as well yes [08:23] or MITM :p [08:23] https://talk.google.com didn't give me a warning, fwiw.. [08:24] maybe you checked "Remember this choice for future connections" at some point [08:25] ah i see what you mean [08:26] mlankhorst: Well, that's HTTPS, not XMPP. [08:26] maybe this is a jabber connection? [08:26] :) [08:26] yeah [08:26] Considering they've [08:26] ...abandoned that for hangouts. [08:26] i presume that gtalk just ships this as a whitelist in their app [08:26] or something [08:26] asac: No, it is no more. [08:26] something else? not xmpp? [08:26] https://en.wikipedia.org/wiki/Hangouts [08:27] hmm. [08:27] so then its probably because we use a legacy service :) [08:28] hmm. no official api? [08:28] not even a subset for just chat? [08:28] that sucks :) [08:28] i hope i am not getting this right [08:30] https://developers.google.com/+/hangouts/ [08:30] ok thats in-hangout api [08:30] asac: No, it's completely closed service. [08:31] guess they dont like us leaeching their services :) [08:33] http://tech.slashdot.org/story/13/05/20/2315216/google-drops-xmpp-support [08:33] so actually pretty recently [08:34] Quite. [08:44] jpds: so seems they continue to support xmpp on client, just not federation after all http://arstechnica.com/information-technology/2013/05/hands-on-with-hangouts-googles-new-text-and-video-chat-architecture/ [08:44] i believe we should hardcode the cert as "known to be good" and not annoy the user :) [08:44] seb128: ? [08:45] asac: Haven't you used Hangouts before? [08:45] jpds: i know hangouts [08:45] probaly have been 1k hours on them already :) [08:45] counting [08:46] asac, I'm not sure I've a grasp on the issue ... are they discontinuing the service (in this case we should stop using it at all) or do they keep running in (in which case why is the certificate buggy)? [08:46] seb128: they will continue to support xmpp for clients [08:47] but not jabber federation [08:47] (to lock out MS and FB to leech on them) [08:47] so that seems to be OK [08:47] now the real issue is that there are warnings about self-certs ... those we can fix by whitelisting this known good cert maybe? [08:48] asac, that makes sense [08:48] not sure if that error comes from empathy or uoa [08:48] xclaesse, ^ do you know? [08:48] not sure how to really know though that its a good server that we currently talk to :) [08:48] I'm getting that warning about chat.facebook.com FYI [08:48] hmm [08:48] maybe its a bug on how we do ssl? [08:49] or maybe they really dont bother and just whitelist their own certs in their apps [08:49] it worked before [08:49] so something has changed [08:50] seb128, what's the problem ? [08:50] facebook & gtalk connects fine here [08:52] infact it's MSN and GTalk too :-) [08:52] MSN connects fine via xmpp here too :) [08:52] did not see any cert issue [08:53] if the cert cannot be validated, empathy will ask the user to accept it or not [08:53] yeah [08:59] xclaesse, it seems everyone on saucy see certificat confirmation dialog, do you know what could be going on there? [08:59] seb128, smcv on #telepathy is our cert expert ;-) [08:59] seb128, afaik we are using GIO something to validate certs [09:00] bah, nautilus keeps segfaulting when I open it here [09:00] xclaesse, http://ubuntuone.com/2uxNfUpH4SLqTOzoY05D3p [09:00] is what I see [09:01] xclaesse, let's move to #telepathy [09:01] seb128, maybe saucy's CA doesn't work well === Sweetsha1k is now known as Sweetshark [09:08] xclaesse, I've no clue about CA, let's see if/when Simon replies [09:09] seb128, it works fine on raring, so something changed in saucy [09:10] does it have different version of gabble? [09:10] https://launchpad.net/distros/ubuntu/+source/telepathy-gabble [09:10] gnutls maybe [09:10] 0.16.5 -> 0.16.6 [09:10] we updated glib-(networking) to 2.37 [09:10] you said that's used for cert verification [09:11] https://launchpad.net/ubuntu/+source/gnutls26 [09:11] that didn't change [09:12] hm, release notes of gabble .6 have lots of stuff about tls actually [09:12] seb128, could you try with gabble .5 on saucy ? [09:13] quickly checking gabble code, it is gnutls doing the checks, no gio. But I'm not really familiar with that code [09:15] xclaesse, downgrading gabble doesn't change anything [09:16] wocky does not seems to be using GTlsConnection yet, so I don't think it is using GIO' stuff [09:16] gcr? [09:16] yep could be gcr issue [09:17] seb128, btw I think you guys should push gabble .6 to raring [09:17] seb128, release notes says "This release fixes a man-in-the-middle attack. You should upgrade." [09:17] xclaesse, security team backported that fix it seems: https://launchpad.net/ubuntu/+source/telepathy-gabble/0.16.5-0ubuntu1.1 [09:18] ah ok, good :) [09:22] Laney, xclaesse: not easy to downgrade gcr without empathy :/ [09:22] even with rebuilding? [09:22] I didn't try that [09:22] empathy: error while loading shared libraries: libgcr-ui-3.so.1: cannot open shared object file: No such file or directory [09:23] when just trying to downgrade gcr [09:24] not sure I care enough atm to spend more time on that though [09:24] Laney, if you want to give that a try please do [09:25] but I'm not sure how useful that is, even if we determine it's the gcr update, we will still need to fix the bug in the new version [09:25] those things have always been fragile :( [09:30] ok, I'm out for some exercice before it gets too hot for that [09:32] aloha [09:42] well I tried building empathy against gcr 3.6 and it doesn't fix it [09:52] seb128: can you approve https://blueprints.launchpad.net/ubuntu/+spec/client-s-xorg-general [09:55] hey czajkowski-from-the-other-side-of-the-world :) [09:56] at least here I have sunshine! [09:57] also jet lag :P [09:57] 3am yesterday 4am today :/ [09:58] * ogra_ hands czajkowski a handfull of melatonin for tomorrow night .... helps a lot with that [09:59] seb128: xclaesse: Downgrading gnome-keyring to 3.6.3 fixes it here [09:59] (just that) [10:00] whoo new laptop X1 carbon to play with when I come back to UK [10:01] wiping and installing Ubuntu on it, handed back the air I was given, got some odd looks for that [10:04] czajkowski: you can install ubuntu on a mac air you know :) [10:05] i hear it's a pain though [10:06] works fine enough [10:06] how's it stability wise? [10:06] had to install some daemon to control the fans [10:06] but good [10:06] davmor2: I'd never hear the end of it from the other half :) [10:06] cool [10:07] are the installation steps suitable for mere mortals, or do you need to be halfway godlike to do so? [10:07] pretty standard [10:08] hmm cool [10:08] that's not to say that i wouldn't choose a thinkpad given the free choice [10:09] heh [10:09] how are the newer thinkpads with hardware support? [10:09] my thinkpad e220s is crap [10:10] trackpoint doesn't work properly with suspend/resume, gets detected as ps/2 generic mouse.. [10:10] and snb-i915 gpu hangs every few hours [10:45] having not used empathy before is there a way to stop the notifications displaying ? [10:52] mlankhorst, done [10:52] Laney, ok, it might be worth opening a gnome-keyring upstream bug about it, do you want to do it or should I? [10:53] I am trying to boot GNOME OS to verify it but I can't get it to work :P [10:53] if you could that would be good [10:53] sure, shower first though [11:18] Laney, seb128: which version of gnome-keyring? [11:18] with the gnome3 ppa on raring it works [11:18] 3.8.2-0ubuntu1~raring1 [11:19] that should be what saucy has, no? [11:19] 3.8.2 bad 3.6.3 good [11:19] just replacing that one package in saucy [11:19] Laney, 3.8.2 works here on raring + gnome3 ppa [11:25] also works for me in a fedora vm [11:28] maybe it's something to do with UOA [11:29] I doubt that [11:29] didrocks: https://code.launchpad.net/~sil2100/cupstream2distro-config/missing_libical/+merge/170040 [11:30] Laney, check debug msg of empathy-auth-client [11:30] sil2100: ? libical isn't in the stack we are interested in [11:30] sil2100: it makes no sense to add it [11:30] we don't want to add every dep on our stacks :) [11:30] G_MESSAGES_DEBUG=all EMPATHY_DEBUG=all /usr/lib/empathy/empathy-auth-client [11:30] then connect your account [11:30] didrocks: but it's failing to do the check job now [11:31] didrocks: how can we make it pass then? [11:31] SInce it's failing because of extra installed packages [11:31] sil2100: check with whole ppa? to disable the check? [11:31] didrocks: and will that work from that time onwards? [11:31] sil2100: just for that run [11:32] ah [11:32] didrocks: so next time indicators will fail then [11:32] ? [11:32] sil2100: hum no [11:32] sil2100: because it will move to the release pocket [11:32] xclaesse: abort_verification: Verification error 6, aborting... [11:32] sil2100: and will be installed by default as the transition will end [11:32] right? [11:32] xclaesse: repros for me in a VM too so if you can set one of those up you should be able to get it [11:33] didrocks: hm, right! [11:33] sil2100: maybe we'll need to redo the container tomorrow morning if it didn't pick the right iso yet, but then, we should be fine [11:35] sil2100: I pasted the discussion on the MP for reference :) [11:36] didrocks: good! Sometimes I need to remember that it's all 'transition' right now, noting that! [11:36] sil2100: no worry, I prefer you ask than doing without this :) [11:37] sil2100: even for me, sometimes the big puzzle is quite hard :p [11:37] didrocks: is a simple revert like this fine? https://code.launchpad.net/~sil2100/libappindicator/revert_debian_rules ;) [11:37] sil2100: perfect, #nochangelog wasn't really needed as you touched debian/changelog, but fine with it as well :) [11:38] Laney, xclaesse: p11-kit changed in saucy as well and changed the location of the key files, not sure if some files is still at the old location or something [11:45] didrocks: https://code.launchpad.net/~sil2100/libappindicator/revert_debian_rules/+merge/170050 then ;) I know I could have pushed directly, buuut I noticed that Mathieu did the commit through a MR, so I would feel silly to push directly without a request [11:46] seb128, could be that, indeed === MacSlow is now known as MacSlow|lunch === greyback is now known as greyback|lunch [12:04] ah [12:04] seb128: try installing p11-kit [12:05] Laney, that fixes it? [12:05] I think so, but I've been monkeying with versions so ... [12:06] that's where the new trust module thingy is [12:06] which was removed from g-k in 3.8 [12:07] p11-kit is not installed here [12:07] Laney, yeah, that fixes it! [12:07] cool [12:08] should we have g-k depend on that? [12:08] (FTR, needs MIR) [12:09] yeah ... [12:09] should be eligible though [12:10] oh no wait, the source is already in main === dednick is now known as dednick|lunch [12:11] pitti, it's only a binary of a source already in main? [12:11] it is [12:11] Laney, not sure, is g-k using it or empathy? [12:11] oh, indeed [12:11] having g-k depends on it works for me [12:12] well I see this in NEWS: * Remove the roots-store module replaced by p11-kit 0.16+ trust module [12:12] but tbh I don't know how it all fits together [12:13] yeah they added it in Debian [12:13] I'll do that now then [12:15] Laney, thanks [12:19] asac, ^ btw [12:20] asac, install "p11-kit", should fix the certificate issue [12:20] grr [12:20] * Laney brings the VCS up to date [12:21] Laney: oh, speaking of VCS [12:21] * Laney runs [12:21] Laney: I recently updated the sessioninstaller bzr [12:21] Laney: no worries :) [12:22] Laney: and I noticed that you applied some debian/patches/ bits with changes from upstream [12:22] Laney: this is much easier with bzr bd [12:22] seb128: will that come through ubuntu-desktop now? [12:22] Laney: next time, just bump the bzr revno in the 0.1.2+bzr1234 version number [12:22] if so i will wait for that :) [12:22] asac, yes === greyback|lunch is now known as greyback [12:22] (i have since set this warning to ignore, so i might not see it [12:22] ) [12:22] pitti: hm, never done anything like that [12:22] Laney: bzr bd is clever enough to see this, check out upstream at that rev, build an orig for that, and build a package [12:23] interesting [12:23] Laney: like in https://launchpad.net/ubuntu/+source/sessioninstaller/0.20+bzr134-0ubuntu4 [12:23] mterry did a few of those as well [12:23] I mean the magic orig stuff [12:23] oh, come on nautilus, wth, every day it segfaults the first time I click on it [12:24] sounds cool! [12:24] Laney: anyway, it's effing awesome magic, and much easier than quilting around :) [12:24] Laney: just FYI [12:24] thanks for the tip [12:24] seb128: oh, je ne suis pas seul ! [12:25] pitti, non, moi aussi ... j'ai gagné le droit de le débugger ? [12:26] seb128: non, mais j'ai le mis sur Launchpad [12:27] 3.8 time ;-) [12:27] * pitti looks at today's /var/crash/_usr_bin_nautilus.1000.crash [12:30] seb128: seems I got the one in gtk_icon_info_get_attach_points(), you as well? [12:30] pitti, yes [12:30] I wonder if those are after upgrades when the icon cache is refreshed or something [12:31] Laney, speaking of 3.8 I should build/install it, it's almost ready in the gnome3 vcs [12:32] peut-être, il souvent bloque dans les matins [12:32] oh, 3.8 for nautilus or for everything/ [12:32] ? [12:32] I'm just about to start backporting the g-s-d power 3.8 bits to 3.6 (for bug 1180513) [12:32] Launchpad bug 1180513 in gnome-settings-daemon (Ubuntu) "lid close actions are ignored laptop always suspends" [High,Triaged] https://launchpad.net/bugs/1180513 [12:33] pitti, nautilus, g-s-d/g-c-c are the only one missing 3.8 atm I think [12:33] pitti, so we sort have the set already [12:33] g-s-d/g-c-c being trickier because of the number of changes they did and our number of patches [12:33] the fact that they made harder to have external panels (that we need) [12:33] the depends on the new ibus as well (which is quite broken out of GNOME) [12:36] pitti, my gut feeling is that it's going us to take at while before having g-s-d/g-c-c ready for the archive, especially that our focus is mobile this cycle ... I wouldn't count on 3.8 to be in saucy [12:37] ack [12:37] btw, bug 1187709 [12:37] Launchpad bug 1187709 in nautilus (Ubuntu) "nautilus crashed with SIGSEGV in gtk_icon_info_get_attach_points()" [Medium,Confirmed] https://launchpad.net/bugs/1187709 [12:37] thanks, I will check upstream/valgrind it === MacSlow|lunch is now known as MacSlow [13:28] seb128: ping :) [13:28] sil2100, hey [13:29] seb128: I'm looking at lp:gnome-control-center-unity/raring right now and the latest commit looks like a fix, but no bug has been attached to it [13:31] seb128: would it be much bother to open up a bug for that? Since I guess this way we'll have all the fixes in an SRU documented by bugs that the SRU team could assert [13:31] seb128: I would modify the changelog then [13:31] sil2100, indeed, I wonder why it has no bug info [13:31] sil2100, https://launchpad.net/ubuntu/+source/gnome-control-center-unity/1.3daily13.06.13-0ubuntu1 [13:32] sil2100, that saucy upload had one ... I guess I forgot the --fixes lp: when doing the backport [13:32] sil2100, #1173818 is the bug to use [13:32] sil2100, let me update the bug to be SRU compliant [13:33] seb128: thanks! Great, I'll modify the changelog then [13:35] sil2100, bug updated [13:51] Laney: any idea what would cause a geoip crash on raring ? [13:51] keep getting them today [14:15] czajkowski: 'fraid not [14:15] do you have any more details? [14:15] like the program or package that is crashing? [14:15] https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1157232 is quite a high one on errors [14:15] Ubuntu bug 1157232 in ubuntu-geoip (Ubuntu) "ubuntu-geoip-provider crashed with SIGSEGV in _dbus_header_get_byte_order()" [High,Confirmed] === sivatharman__ is now known as psivaa [14:20] Laney: it says it'll send a report but no bug opens [14:21] it'll be reporting to errors [14:21] it probably reports the issue to errors.ubuntu.com [14:21] al I know is I'm having to reboot the machine every 20 mins [14:21] :/ [14:21] a geoip crash is making you reboot? [14:21] Laney: everything dies [14:21] wifi goes [14:24] seems like a kernel issue or something [14:25] czajkowski: look for a file with the right-ish timestamp in /var/crash (ls -l /var/crash) and then apport-bug /that/file [14:25] seb128: yeah but geoip is the only thing coming up [14:26] Laney: ahhh http://pastebin.ubuntu.com/ [14:28] don't think you meant that :P [14:28] nothing to see here [14:28] move along :) [14:29] Laney: http://pastebin.ubuntu.com/5777262/ [14:30] apport-bug /var/crash/_usr_lib_ubuntu-geoip_ubuntu-geoip-provider.1000.crash [14:31] czajkowski, firefox 'http://errors.ubuntu.com/user/'$(printf $(sudo cat /sys/class/dmi/id/product_uuid) | sha512sum) [14:31] czajkowski, that should show you the issues you reported to e.u.c [14:32] ah [14:33] mine is some huge list of uuids [14:34] would hate to have to find a single crash in that [14:34] Laney, talk to ev ... ;-) [14:34] might as well file a bug :P [14:35] wow [14:35] I've a whole lot of data there [14:35] thanks seb128 [14:35] yw [14:37] * Start gsd via user session if starting 'unity' too. This is in preparation [14:37] for starting unity directly. [14:37] Laney: ^ is that ok to upload? [14:38] Laney: I'm about to do a g-s-d upload to make seb128 happy again [14:38] pitti: yes, should be a noop currently [14:38] that unity job doesn't get used [14:38] but if you want to test it I won't complain ;) [14:50] hi, is someone planning to finish the indicator-datetime upload? :) [14:51] seb128: there, g-s-d uploaded for respecting lid handling action config again [14:53] pitti, \o/ [14:53] jbicha, sil2100 is working on it [14:56] * pitti goes to update gvfs to 1.17.2 [14:57] ah, back in the land of gnome updates? [14:57] Laney: it's too hot to do anything which requires serious thought.. [14:57] (after fiddling with g-s-d for two hours ..) [14:58] :-) [14:58] you can come troll the desktop team meeting in a minute then :P [14:58] well, 30 minutes [14:59] rather yes ;-) [15:17] seb128: hey what do you think about me uploading gnome-session 3.8 once ical is done? it's been in the desktop ppa for a week [15:17] urg [15:17] jbicha, stop pushing so much crack in the archive ;-) [15:17] or we could talk about it first :) [15:18] jbicha, sorry I forgot to test it, I will mention it during the meeting and install it now [15:18] are there intrusive changes in -session? [15:18] and test tomorrow [15:18] there's not much crack left :) [15:18] pitti, some yes [15:18] je peux faire ça aussi, si tu veux [15:18] pitti, ça serait utile, merci [15:22] jbicha, pitti: hum, I don't like that much [15:22] The following NEW packages will be installed: [15:22] libsystemd-journal0 [15:22] oh? not here [15:22] oh, already had it, nevermind [15:22] pitti, you probably had it [15:22] Size: 55804 [15:22] do we know how the lib behave if journald is not there? [15:23] will it spawn an extra service? [15:23] I thought pitti said that library was ok but I think it's fairly simple to patch it out if we definitely don't want it [15:25] it at least survived a reboot, and unity session start [15:25] guest session is broken in lightdm, but that was the case before already [15:27]