[04:28] Good morning [04:48] hey pitti [07:27] Hello, world!\n === work_alkisg is now known as alkisg [08:04] good morning desktopers! === davidcalle_ is now known as davidcalle [08:22] pitti: hey, I know this might be a bit OT here, but now that gdm/lightdm/kdm are logind aware (and thus not registering a ck session anymore) shouldn't be the nox11 option be removed from the call to the ck pam module? [08:24] bigon: TBH I don't even remember any more what that does [08:32] pitti: the nox11 prevent the pam module to register a session if a DISPLAY is set [08:33] bigon, gdm/gnome-shell still work with ck in theory, you just loose a bunch of features [08:33] well in debian since yesterday in unstable, it is compiled with logind support [08:33] and ck-list-session is empty [08:33] that's why I think that the nox11 should be remove [08:34] d [08:35] bigon, right, if its built with logind, ck can go [08:36] indeed, I'm running a ck-free desktop now [08:36] bigon: I guess in that case we might rather remove ck altogether? [08:37] pitti, seems about right, its really only need on !linux now [08:38] yes indeed !linux [08:38] and application that really require ck with no support of logind [08:39] so ck should stay [08:39] unfortunately [08:39] ah right [08:39] perhaps only build CK on !linux theN? [08:39] http://codesearch.debian.net/search?q=org.freedesktop.ConsoleKit [08:40] there are other pkg that are using exclusively ck that run on linux too [08:40] but like I said ATM there is no session registred with gdm3 (and logind support enabled) [08:41] I'm wondering if it's also the case with lightdm and such [08:41] that's why I was proposing to let the pam module register the session instead of the DM itself [08:43] I'll open a bug for this in debian BTS === alkisg is now known as work_alkisg === mlankhor1t is now known as mlankhorst [08:58] hum [08:59] didrocks, larsu, pitti: is anyone having issues with the canonical sites (irc, imap server)? [08:59] seb128: hum, no issue here for now [08:59] hum, k [08:59] seb128: irc works fine. I don't use their imap anymore [08:59] the lag-o-meter on IRC keeps increasing here [09:00] I've had some lag earlier today, but not right now [09:00] k [09:00] oh, just got disconnected, weird [09:08] hey seb128 [09:08] Bug 1299912 [09:09] (the bots are dead?) [09:11] darkxst, hey [09:11] not sure about the bots [09:11] thanks, that's in the sponsoring queue right? [09:11] I saw the email, but I'm still in backlog from the w.e [09:12] right, it is [09:12] seb128, trusty part is atleast [09:12] seems merges against ubuntu-desktop don't show up in the queue? [09:13] well it is there this time though [09:15] not sure how the sponsoring page is generated [09:15] it might depends of who is set as reviewer [09:16] seb128: IRC works quite fine here; I don't use Canonical email; canonicaladmin also WFM [09:16] pitti, thanks, I'm still in lag-o-meter land on the IRC, go figure [09:17] seb128, no lag here, from this side of the world ;) [09:18] darkxst, the issues I have are on the Canonical infra, not on the public IRC [09:18] oh ok [09:18] well I got reconnected and now lag is to 0 again [09:18] let's see if it resolves itself over the day === dpm_ is now known as dpm === vrruiz_ is now known as rvr [09:22] mvo: it might theoretically be possible to run without the backported kernel, but it's not a supported path [09:26] hey morgen pitti, I read you had a nice and productive systemd/GNOME sprint :-) [09:28] hey dpm [09:28] dpm: I did, thanks! [09:28] dpm: I haven't gotten around to your mail yet, sorry; last week was full of firefighting [09:30] pitti, no worries, it's nothing urgent atm for MAE, as we're shipping the Simplified Chinese langpack on the phone anyway, but I'm trying to get the wheels moving to have a good i18n story for the phone - thanks! === FJKong is now known as FJKong_afk === davidcalle_ is now known as davidcalle [10:10] hi there [10:13] does unity do anything with xinput touch events? [10:38] seb128, ok to bump dep on gnome-settings-daemon-schemas to (< 3.12) in unity-settings-daemon, its causing problems with our PPA's [10:39] I promise I won't break anything in the updates when they land ;) [10:39] darkxst, what is the version used atm? [10:41] darkxst, we added it because the new version of g-s-d was changing keys in an incompatible way and generating abort reports that were starting ranking high on e.u.c [10:41] seb128, its currently gnome-settings-daemon-schemas (>= 3.8), [10:41] gnome-settings-daemon-schemas (<< 3.10), [10:42] we need a 3.10 that doesn't drop keys before relaxing that << === TyzzyT is now known as TyzzyT2 === TyzzyT2 is now known as TyzzyT [10:43] seb128, which g-s-d was causing errors? [10:43] 3.10 [10:44] seb128, there are no public 3.10 packages on trusty as yet? [10:44] well, ricotz had some in a ppa [10:44] and that was creating quite some reports on e.u.c [10:44] oh, right [10:44] that's why I added the << [10:44] his packages are probably just git snapshots [10:45] the packaging I did had reverted all key removals [10:46] could have been https://git.gnome.org/browse/gnome-settings-daemon/commit/data?h=gnome-3-10&id=1709bf58a60b76bce77038bb804991447d215f49 [10:46] the issue is that we can't tell yours with the revert and ricotz's one appart :/ [10:47] well I guess users running a ppa with git snapshot get what they opted in for then [10:49] seb128, hi, i dont remember doing a snapshot of g-s-d for quite some cyclesand my ppas doesnt contain one, do you happen to find the offending package? [10:51] ricotz, it was maybe simply a 3.10 version from upstream [10:51] they dropped keys from their schemas there [10:51] e.g https://git.gnome.org/browse/gnome-settings-daemon/commit/data?h=gnome-3-10&id=1709bf58a60b76bce77038bb804991447d215f49 [10:51] seb128, i know, i am curious where the package came from [10:51] I don't remember, one of your ppas [10:53] i guess it could be gnome3-team/gnome3: gnome-settings-daemon - 3.10.2-0ubuntu1~saucy6 [10:53] darkxst, ^? [10:58] maybe, that had http://pastebin.com/U69RM6ww [10:59] which I suppose never made it into u-s-d in the end [11:00] same patch is likely in our 3.12 packages [11:05] although the actual key in seb128 link was likely fallout from the ibus update [11:05] which shouldnt affect u-s-d? [11:07] https://errors.ubuntu.com/problem/d7ee33f4be4368596fc6c3afbfab8604799370a8 [11:07] was the issue iirc [11:07] https://errors.ubuntu.com/oops/7e0c117e-c6e9-11e3-9099-fa163e707a72 [11:07] gnome-settings-daemon-schemas 3.12.0.1-0ubuntu1~trusty1 [origin: LP-PPA-gnome3-team-gnome3-staging] [11:09] ricotz, ^ they had stuff with "origin: LP-PPA-ricotz-testing" but the g-s-d-s was from the gnome3 ppa it seems [11:09] but it has been some time I don't remember the specifics [11:12] seb128, yeah, i see, i was assuming that [11:13] darkxst, this suggests that the problem persists with the latest g-s-d upload then [11:13] yes its related to the upower port [11:14] * ricotz didn't look at those links since it requires some u1 login again [11:15] ricotz my first link was unrelated [11:15] I think this is what is the issue [11:15] https://bugzilla.gnome.org/show_bug.cgi?id=709736 [11:15] yes it is === MacSlow is now known as MacSlow|lunch [11:54] if I'm correctly looking at lightdm, it both create a logind and ck session when available [11:55] is this correct? [12:06] hm looks like i can produce a lot of xorg-server spew by simply using my touchpad through evdev instead of synaptics [12:07] darkxst: glib-2.0 finally came to the party but now something weird that I dont understand with pygobject, just amd64 https://launchpadlibrarian.net/174588843/buildlog_ubuntu-precise-amd64.pygobject_3.8.0-2%7Evinux1_FAILEDTOBUILD.txt.gz [12:07] if you're busy though, I understand :) [12:15] Fudge, test_add_watch_no_data (test_iochannel.IOChannel) ... /bin/bash: line 4: 2884 Segmentation fault PYTHONPATH=..:../tests:${PYTHONPATH:+:$PYTHONPATH} LD_LIBRARY_PATH=./.libs:$LD_LIBRARY_PATH GI_TYPELIB_PATH=.:$GI_TYPELIB_PATH XDG_DATA_DIRS=$XDG_DATA_DIRS:/usr/share MALLOC_PERTURB_=85 MALLOC_CHECK_=3 G_SLICE=debug-blocks TESTS_BUILDDIR=. /usr/bin/python2.7-dbg -Wd ../../tests/runtests.py [12:32] darkxst: forgive me if that is a solution as I dont understand how to implement it [12:35] Fudge, that is the error [12:35] I have no idea why its crashing! [12:36] oh right, always something for me, things love to crash :D [12:36] Fudge try running the tests locally and see if you can get a backtrace! [12:37] it may just be a missing dep, but can't really say from the log message [12:39] thank you for taking the time :), I'll try tomorrow [12:46] bt === davidcalle_ is now known as davidcalle === MacSlow|lunch is now known as MacSlow [13:16] pitti: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747071 << if you care about the ck-ectomie [13:18] bigon: I'm not quite sure how to do that in CK -- the session needs to be registered by a CK client, i. e. PAM-ck or the DM [13:18] bigon: IMHO DMs should use CK on !linux and logind on linux, and we stop supporting CK on linux? [13:22] GDM is not registring the session, looking at lightdm code, this one is still doing so [13:23] not sure about KDM [13:24] if we only want to support ck on !linux then indeed things are way more simple [13:28] bigon: hm, reconsidering -- I think it makes more sense to do that dynamically and ignore the platform [13:29] bigon: i. e. try logind, and if that fails, fall back to registering a CK session [13:29] bigon: that mirrors what e. g. g-settings-daemon is doing, and opens the possibility that the logind API gets a shim (or otherwise implemented) in bsd [13:30] gdm is doing that too [13:31] well gdm is registering a logind session and then falls back to ck [13:31] but not both [13:31] that seems fine? [13:32] ok that XI bug is annoying :P === gatox is now known as gatox_lunch [16:06] seb128: around? === gatox_lunch is now known as gatox [17:54] Anyone from bugcontrol here? Could you please nominate bug 1316243 for precise?