=== m_conley is now known as m_conley_away === shengyao_afk is now known as shengyao === duflu_ is now known as duflu [06:53] Good morning [06:58] robru: that's psivaa's email about symlinks? [08:23] Hello [08:25] @larsu funktioniert auch mit installierten Schemas nicht, gesettings-qt ist trunk direkt mit bzr runtergeldaen, allerdings muss ich dazu sagen, unter suse nicht ubuntu... [08:25] damianatorrpm: Error: "larsu" is not a valid command. [08:53] damianatorrpm: sorry, I was afk making some tea :) [08:54] damianatorrpm: so you're not running gnome then? [08:54] damianatorrpm: how are you using the schema? You need to run glib-compile-schemas after installing it [08:57] Yes I'm running gnome at the moment. sudo glib-compile-schemas /usr/share/glib-2.0/schemas is of course done [08:58] but the same problem is also with standard key's like org.gnome.whatever [08:58] in dconf-editor I can correctly see and edit any key [08:58] damianatorrpm: do you have the same problem with the gsettings command line tool? [08:59] gsettings get org.gnome.deskotp.interface gtk-theme [09:01] larsu: I'm 99% certain that gsettings get org.gnome.deskotp.interface gtk-theme works properly. Today I have meeting in the office and am not at home so I will try this evening, [09:03] hey there [09:03] Laney: morning [09:03] good morning desktopers! [09:04] hey Laney, larsu [09:04] damianatorrpm: please do, and also try with the keys that you installed. If that doesn't work, it's likely that something's wrong with your schema [09:04] Laney, e-d-s migrated [09:05] yes, I got a lot of emails \o/ [09:05] \o/ [09:05] pitti is going to be happy [09:05] all those exciting new bugs to discover [09:05] right [09:05] :P [09:05] * pitti waves hello to the crowd [09:06] speaking of bugs, I don't get why I'm the only one seeing telepathy-mission-control sigabrt at every login === larsu is now known as crowd [09:06] hello pitti! [09:06] oh nice! that means upstream merge proposals should now be unblocked, I'll re-run a few [09:06] hey pitti, wie gehts? === crowd is now known as larsu [09:06] * pitti hugs the cloud^Wcroud^Wlarsu [09:06] seb128: gut, danke! und dir? [09:06] lol [09:06] gut auch, danke! [09:06] seb128: "auch gut" [09:06] ah, danke ;-) [09:07] * larsu wonders when we can finally switch the official language of this channel to German [09:07] now that seb128 is almost there... [09:07] :-p [09:08] so I debugged that telepathy sigabrt I see at every greeter use, found quite some issues [09:08] the first one is what is creating the bug [09:08] [ 61.537359] type=1400 audit(1385628593.901:86): apparmor="DENIED" operation="mkdir" parent=3888 profile="/usr/lib/telepathy/mission-control-5" name="/var/lib/lightdm/.local/share/telepathy/" [09:08] do you guys see that in your dmesg as well? [09:08] dmesg | grep DENIED [09:08] I don't get why you wouldn't... [09:09] pitti: yea, i *think robru's ping was about my email [09:09] then mission control has a bug where it reuse a GError without setting it to NULL in between, which is in the codepath for when that dir is not writable [09:09] no denied here [09:09] Laney, is the dir existing for you? [09:09] yeah [09:10] ok, that would explain it [09:10] nod [09:10] if you remove it and go the greater, do you get the deny? [09:10] I wonder if my apparmor config is different somehow [09:10] or if you guys just happened to have the directory created at some point and staying there since [09:11] it got recreated [09:11] shrug [09:12] why is apparmor stopping that for me and not for you :/ [09:12] maybe one of us messed with the policies [09:12] I didn't afaik [09:12] and I'm the special case it seems, nobody else mentioned that issue [09:14] that's what I did [09:14] oops [09:14] was scrolled up [09:15] hum, my /etc/apparmor.d/usr.lib.telepathy has [09:15] owner /var/lib/gdm/.local/share/telepathy/ rw, [09:15] owner /var/lib/gdm/.local/share/telepathy/mission-control/ rw, [09:15] owner /var/lib/gdm/.local/share/telepathy/mission-control/* rwk, [09:15] [09:15] no lightdm entries [09:16] I though HOME was not working out of /home without changing the tunables [09:16] I guess I need jdstrand, that's going to be for next week with thanksgiving [09:21] some days I hate trusty [09:21] Does anyone have time to try and see what's wrong with the extensions in https://code.launchpad.net/~noskcaj/ubuntu/trusty/gthumb/3.2.5/+merge/196783 [09:21] lightdm/xorg are screwed on user switching [09:21] seb128: frusty! ;) [09:21] frusty fahr? [09:21] didrocks, yeah, wth [09:21] Xorg hits a sigabrt with "no display found" error [09:21] lightdm or something gets confused [09:22] and I get a blank screen/vt over vt7/my session when that happens [09:22] urgh, doesn't sound good [09:22] I can see the cursor changing shape [09:22] but I can't get back the pixels [09:22] going to vt, restarting compiz or another wm doesn't work [09:22] just need to reboot [09:23] so this just happens sometimes, not all of the time? [09:23] robert_ancell said he can reproduce on trusty and seems an xorg error [09:23] we should just drop xorg [09:23] larsu, right, seems a timing issue, between lightdm and xorg [09:23] haha [09:23] anyway, I figured out why I get the telepathy issue [09:24] Laney, do you have gnome-online-account installed ? [09:24] looking at my bootcharts, it does [09:24] lightdm -> unity-greeter -> indicator-datetime -> e-d-s -> goa -> telepathy [09:24] Noskcaj: not sure if anyone here is going to know particularly; we don't ship gthumb [09:24] the indicator should probably not init/use e-d-s at all on the greeter profile, I'm going to bug charles about that [09:25] no, it's not [09:25] the issue stopped after I uninstalled "gnome-online-account" [09:25] ok, that explains then [09:25] btw in the category [09:25] "larsu told you so" [09:25] Laney, ok. I was just a recommendation from dholbach. Xubuntu still does, and no one can fix this [09:26] nomination is bug #1255719 [09:26] Launchpad bug 1255719 in indicator-sync (Ubuntu) "Upstart job keeps respawing indicator-sync on the greeter" [High,New] https://launchpad.net/bugs/1255719 [09:26] Noskcaj: check NEWS and so on to find out if they were dropped by upstream [09:26] larsu, ^ I was thinking about you when I filed this one :p [09:26] Noskcaj: also see where they were coming from in the previous package [09:26] larsu, I couldn't troll ted though, those slackers are off eating turkey [09:28] seb128: I will enjoy this moment in silence :) [09:28] ooh, my PS4 is "dispatching soon" [09:28] larsu, ;-) [09:28] thanksgiving? [09:28] Laney, oh, you got one of those? [09:28] * Laney will be "sick" tomorrow [09:28] larsu, yes [09:28] * seb128 slaps Laney [09:28] yep! [09:28] haha [09:28] lol [09:28] PS4> WANT [09:28] Laney, give it to me! [09:28] go to a midnight launch tonight [09:29] pretty please? [09:29] (being nice is supposed to work :p) [09:29] yeah, so I can get a cold and really be sick with a PS4 tomorrow? :p [09:29] ok I'll get right on that [09:29] sounds like a winning plan to me [09:29] haha [09:30] I would have bought one already, if it was reading PS3 games, but it doesn't :/ [09:30] Laney: shouldn't be too hard this time of year. Just get into a subway and touch all the handles [09:30] my PS3 is having some issues, it tends to freeze/lock [09:30] yeah I skipped PS3 so that's not a problem for me except that I would have bought GTA [09:30] I'm not sure if I should buy a PS3 slim to replace it or go with a PS4 [09:31] guessing those ps3s are quite cheap now [09:31] seems like there is almost no game available for it atm :/ [09:31] oh, still not so much [09:32] ~200€ [09:38] larsu, I think your o-s change has a bug, I'm getting gedit to segfault sometimes since yesterday [09:39] gdk_window_has_native: assertion 'GDK_IS_WINDOW (window)' failed [09:41] oh [09:41] do you have a stacktrace? [09:43] seb128: hello! :) [09:43] larsu, let me install the dbg (and makes sure it's not the GTK update, but I doubt it) [09:43] sil2100, hey, what's up? [09:44] oha ! my clock is right after switching languages back and forth on the phone ... [09:44] ogra_, hey ... weird, does it persist after a reboot? [09:44] no more AM/PM [09:44] or is that a one time workaround? [09:45] it only happens after a reboot ... and then stays that way [09:45] seb128: do you think you'll have time for a quick preNEW review of lp:unity-voice today? :) [09:45] i assume we dont update ~/.pam-environment on upgrades ? [09:45] sil2100, you already pinged about that yesterday, I can have a try, still dealing with some other issues [09:45] sil2100, if that's really urgent maybe didrocks can help you? [09:45] ogra_, what upgrades have to do with the user config? [09:46] so that my manual setting/unsetting/setting actually added something there [09:46] seb128: it's not, I just want to MIR it later on [09:46] so that mterry isn't the only one having to MIR everything :) [09:46] didrocks, well, I got 4 pings in a day for it now so I start wondering [09:46] seb128, well, if we add a setting the user needs to get it with a proper value on upgrade [09:47] ogra_, I don't understand what that has to do with upgrades [09:47] if my ~/.pam-enviroment was missing a var and key ... [09:47] seb128: I think as the CI system was down for some some days, upstreams want to get their code released :p [09:47] didrocks, gotcha, anyway it's on my todo [09:47] no need to ping more :p [09:47] thanks seb128 :) [09:47] yw! [09:48] ogra_, it's good now, even after a reboot? [09:48] ogra_, that bug doesn't make sense to me [09:48] seb128, if there is a fix thats based on the user having a sprecific var with a specific setting, it should not be needed that the user has to set/unset something in the settings app to get the fix [09:48] seb128, yes, it seems to persist [09:48] ogra_, right, it should not, but days only have 24 hours [09:49] there is a limit on how much we can get done in a day [09:49] seb128, sure, i'm just trying to identify the reason of the bug [09:50] ogra_, I guess you picked your locale in the setting at a time where we were setting the language only and no lctime and such [09:50] right [09:50] so your user config was incomplete [09:50] thats what i mean ... ~/.pam_environment just stayed that way [09:50] we could try to tweak pam configs on upgrades [09:50] right [09:50] but well, imho that's not worth the efforts atm [09:51] only early adapter are running touch, and it's easy to go in settings and pick your language again [09:51] well, most of our users will do OTA upgrades and not reinstall all the time [09:51] right [09:51] our current users are technical enough to be able to workaround it [09:51] well, i wasnt [09:51] it bothered me for several weeks and i only worked around it by accident [09:52] well, you just fixed it no? ;-) [09:52] I guess it's part of being an early adopter [09:52] heh, k [09:52] don't get me wrong, I would like to fix all bugs and all weird cases [09:53] but we just can't justify spending that amonth of efforts on the experience for early adapter updating [09:53] we need to focus on making the product good [09:53] those would started very early might have to deal with some upgrade issues [09:54] but the other alternative is to spend a ridiculous amonth of efforts for a few users and put us behind for the important work [09:54] well, we should at least have some hooks prepared for such cases ... they will likely also happen on released images at some point [09:54] right [09:54] there is a lot of things we should have [09:54] surely not urgent right now [09:54] but something we should at least have a plan for before release [09:55] we have the migration tool didrocks wrote, it's working [09:55] it didnt in my case :) [09:55] it just requires somebody to actual write the migration code for that case, if you want to handle it [09:55] well, somebody needs to write a script that migrate the config [09:56] it's not rocket science, but it's touch pam config and has possibility to create real issues at login [09:56] so it needs some thinking and testing [09:56] rihgt [09:56] if you want to do it and send a patch, please do [09:56] *right even [09:56] but it's just not enough of an issue atm to make the top of my list [10:00] * Laney builds new glib [10:00] (muhahaha) [10:01] ;-) [10:01] shrug [10:01] Laney, your e-d-s ppa somewhat made my system unhappy :/ [10:01] well I installed that transition back then [10:01] which part? [10:01] the goa bit? [10:01] but trusty doesn't resolve it [10:01] yes [10:02] it removed empathy and I can't install it back [10:02] it's probably diverged somewhat from the archive now [10:02] you should ppa-purge it [10:02] empathy : Dépend: libgoa-1.0-0 (>= 3.5.1) mais ne sera pas installé [10:02] if that can handle transitions [10:02] shrug [10:02] I've a libgoa-1.0-0b [10:03] yes, the goa transition [10:03] which isn't in archive [10:03] blocked on webkit? [10:03] yeah [10:03] there might be a working qemu/arm64 now though [10:03] https://launchpad.net/ubuntu/+source/qemu/1.6.0+dfsg-2ubuntu3 [10:04] will try it later [10:05] $ sudo apt-get instarusty libevolution/trusty evolution-data-server/trusty libgoa-1.0-common/trusty libgoa-1.0-0b- evolution-plugins/trusty gnome-control-center/trusty unity-scope-gdrive/trusty unity-lens-photos/trusty gir1.2-gdata-0.0/trusty gir1.2-goa-1.0/trusty [10:05] that fixes it [10:05] * seb128 doesn't trust ppa purge, just do stuff by hand [10:06] seb128, i have truned bug 1255530 into a wishlist bug for session-migration and closed the indicator-datetime task [10:06] Launchpad bug 1255530 in session-migration (Ubuntu) "/home/phablet/.pam_environment does not get updated on OTA upgrades" [Wishlist,New] https://launchpad.net/bugs/1255530 [10:06] ogra_, thanks [10:06] yeah that seemed to mess up with reverting the transition here [10:09] for once aptitude was useful in doing that [10:09] like the third option was to downgrade everything to trusty [10:53] larsu, do you want to fix update-manager for the box/scaling issue? [10:53] or should I have a look? [10:55] seb128: I had planned to do it. I'm working in the theme right now though, so if you have time or want to do it, I'd be happy if you did [10:55] larsu, I'm having a look [11:26] larsu, https://code.launchpad.net/~seb128/update-manager/box-use-vertical-space/+merge/197042 fixes the update-manager issue for me === MacSlow is now known as MacSlow|lunch [11:26] oh, speaking of update-manager [11:26] hey mvo ;-) [11:26] on that note, lunch time, bbiab [11:27] seb128: are you setting that expand property on a box? [11:27] seb128: ah nvm, enjoy lunch! [11:40] * Laney installs new glib packages [11:40] * Laney watches PC catch on fire [11:44] seb128: hey! just saw your MP [11:45] didrocks: ping? [11:46] mvo, hey, how are you? [11:46] mlankhorst: pong [11:46] larsu, yes, seems to work [11:47] didrocks: I was porting pointer barriers to unity-2d, but I noticed that it believes it should create a pointer barrier at 0x0, stretching to 0x0 [11:47] * seb128 sends some water in Laney's direction [11:47] which somehow works on raring xserver [11:47] Laney, how is the world seen from a new glib? [11:47] but fails with the new pointer barrier implementation [11:48] I didn't restart my session yet because it's building webkitgtk/arm64, but nothing blew up so far [11:48] mlankhorst, what do you mean "ported pointer barriers to unity-2d"? [11:48] downloading a trusty iso to put it in there [11:48] Laney, good [11:48] let me scp it to people and you ca... oh wait, i386 [11:48] mlankhorst: this is for precise I guess? [11:48] didrocks: yes :) [11:49] Laney, ;-) [11:49] Laney, if you push the vcs somewhere I'm happy to test build/install it [11:49] easily fixed! [11:49] s'already building [11:49] seb128: saucy xserver has the upstream pointer barrier abi [11:50] so if i want to backport saucy xserver to precise the pointer barrier implementation of unity and unity-2d need to be changed at runtime [11:51] mlankhorst: maybe the unity8 guys have some code for that, and can be backported to unity2d [11:51] didrocks: I already ported it [11:51] but I don't see why the pointer barrier is created with 0x0 0x0 [11:51] Kaleo: do you remember? ^ [11:52] it's on the s-lts-backport ppa [11:52] mlankhorst, ok, I was not sure if you were adding the feature (e.g if unity-2d has it, it was not feature complete compared to 3d) [11:52] if unity-2d didn't have pointer barriers I wouldn't spend the effort on it :P [11:52] didrocks, unity 2D has it, not unity8 [11:54] Kaleo: I think his question was: [11:54] "why the pointer barrier is created with 0x0 0x0 " [11:54] yeah [11:55] if I look at shell/Shell.qml p2: Qt.point(x, declarativeView.screen.geometry.y + declarativeView.screen.geometry.height) [11:55] p1: Qt.point(x, declarativeView.screen.geometry.y) [11:56] so I'm guessing declarativeView.screen.geometry.height = 0 [11:59] didrocks, mlankhorst dunno [11:59] didrocks, mlankhorst: better ask greyback or Saviq [12:03] mlankhorst: would suspect libunity-2d-private/src/screeninfo.h isn't getting the screen geometry correctly [12:06] mlankhorst: else that piece of qml is being called before the screen geometry has been fetched - and isn't updated when the screen geometry is then corrected [12:07] that would seem likely [12:13] yeah [12:14] calling xrandr afterwards causes it to create barriers again with more reasonable x/y coordinates [12:15] seb128: don't know if you can point me in the right direction with this one. I updated my Saucy Laptop yesterday and now even though the only keybord I have installed is English(UK) it seems to be a US layout [12:15] davmor2, no idea, what's the difference between both? [12:15] I though they were both qwerty [12:16] seb128: @ becames ", shift 2 becomes @ [12:16] davmor2, what is the indicator in the panel saying? [12:16] is that persistant accross reboots? [12:16] seb128: yeap [12:17] deb http://people.canonical.com/~laney/package-junkyard ./ [12:17] ^ glib [12:20] oh wait, floats, grr :P [12:21] Laney, desrt: you guys are boring, I like that! [12:22] (new glib installed, restarted session, no visible change) [12:23] good good [12:23] seb128: http://ubuntuone.com/7I0RGTAaCn1z9pZOpgsjpT So here I clicked on the indicator and opened the keyboard layout but that isn't what I have :) [12:23] davmor2, is gnome-settings-daemon running? [12:24] ok looks like a printf error, sigh [12:24] back to square 0 [12:26] seb128: running ps aux | grep gnome-settings-daemon I have listed /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper and nothing else [12:26] davmor2, that's your issue I guess [12:27] davmor2, do you have any apport file for it or an error in .cache/upstart/gnome-settings-daemon.log ? [12:28] seb128: http://paste.ubuntu.com/6489263 [12:28] seb128: I'll check it now [12:28] davmor2, do you use an nvidia card/driver? [12:28] seb128: I do [12:28] davmor2, is your machine an optimus one?. [12:28] seb128: it is [12:28] davmor2, talk to tseliot, that's a known issue with nvidia drivers/optimus [12:28] davmor2, https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1224254 [12:28] Launchpad bug 1224254 in xserver-xorg-video-modesetting (Ubuntu) "xrandr Xerrors with the nvidia binary drivers" [Medium,Triaged] [12:29] seb128: thanks [12:29] davmor2, uw [12:29] yw === Sweetsha1k is now known as Sweetshark [12:29] davmor2, gsettings set org.gnome.settings-daemon.plugins.xrandr active false [12:30] davmor2, that should workaround it (it might make your monitors config wrong though, if that's the case use the nvidia tool I guess) [12:30] seb128: thanks [12:30] yw [12:33] seb128: Yay work around worked I have me @'s back it makes it much easier to send emails now :) Thanks again :) [12:34] davmor2, yw! [12:34] davmor2, what did you change btw? I'm curious why that just started... [12:34] davmor2, new nvidia drivers? [12:35] Let me have a look at the update history and see what got installed [12:37] davmor2, one other option is that you did use the monitor configuration tool and got a configuration written and that g-s-d started to try to apply it (where you had none before and it was not trying to apply changes) [12:37] glib is up ... [12:37] davmor2, you can try re-enabling the key and deleting .config/monitors.xml [12:39] seb128: only xorg change seems to be xserver-xorg-glamoregl [12:39] davmor2, what's the timestamp of .config/monitors.xml ? [12:39] desrt: ↑, should make you happy :-) [12:40] seb128: no such file or directory [12:42] davmor2, hum, ok, so probably nvidia/optimus by itself then... not sure when that just started being buggy for you [12:42] Laney, WAIT [12:42] Laney: if glib is up, does that automatically mean that flippant is on the rise too? [12:42] ;-) [12:42] haha, you can't scare me with that [12:42] there's HOURS to put a britney block in yet :P [12:43] hehe [12:43] well, no issue so far and I restarted my session [12:43] so looks good [12:44] davmor2: flippant took a hit on the news, but loquacious is riding its coat tails [12:44] Laney: as long as sarcasm isn't in decline I don't care :D === MacSlow|lunch is now known as MacSlow [12:50] didrocks/greyback/Kaleo: turns out that something in kapplication probably already calls XGetEventData, so XGetEventData call was failing in my handler [12:50] which caused the event to be dorpped [12:51] mlankhorst: that's annoying [12:51] yeah, at least new pointer barriers work now :) [12:51] shrug [12:52] Laney, new glib is buggy, put a block please [12:52] Laney, desrt, larsu: with glib 2.39 I can't change indicator-power settings (e.g display % in panel, in the indicator menu), it displays those on start [12:53] g_simple_action_set_state: assertion 'state_type != NULL' failed [12:53] desrt, larsu, Laney: http://paste.ubuntu.com/6489372/ [12:54] works fine if I LD_PRELOAD the 2.38 libgio [12:57] * larsu takes a look [12:59] true, seems a change in glib causes this [13:03] hm, this might be it? https://git.gnome.org/browse/glib/commit/?id=83869120bba2aa745a1b23fb415ab0eddd6f9327 [13:05] Is the bug that you're not giving the type when constructing the GSimpleAction? [13:06] Laney: yep, just found that in indicator-power [13:06] nod [13:06] it's g_settings_binding something to the state of an action that was not created with g_simple_action_new_stateful [13:07] Isn't it that you're using g_simple_action_new(..., NULL) instead of the type there? [13:07] oh, maybe not [13:07] * Laney gets it [13:07] no, the second argument to that function is the activation parameter [13:07] yeah [13:07] I'll have a patch up in a bit, this doesn't seem hard [13:08] * larsu compiles glib [13:08] no need [13:08] deb http://people.canonical.com/~laney/package-junkyard ./ [13:08] ah, thanks :) [13:08] or get the debs from https://launchpad.net/ubuntu/+source/glib2.0/2.39.1-0ubuntu1/+build/5277767 [13:09] yeah if you like downloading stuff :P [13:13] I wonder why charles didn't just use a gsettingsaction === alan_g is now known as alan_g|lunch [13:17] seb128, a fun one for you: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1255970 [13:17] Launchpad bug 1255970 in gnome-screensaver (Ubuntu) "multi-monitor: when the screen saver self-engages only the focused screen is visually protected" [Undecided,New] [13:18] apw, can you reproduce? I had that once like a month ago and couldn't reproduce it after that :/ [13:19] seb128, if you hand-engage the screensaver with C-A-l it changes behaviour [13:20] seb128, but if you reboot and let it lock by itself it seems reproducible [13:20] (as someone who manually locks most of the time that is why it took me so long work out how it occurred) [13:20] apw, ok, that would explain why I couldn't reproduce, I usually lock by suspending/closing lid/manual action [13:21] never by timeout [13:21] apw, thanks! [13:21] yeah timeout seems to be the key [13:21] and only timeout any other seems to fix it somehow [13:23] seb128: https://code.launchpad.net/~larsu/indicator-power/use-gsettings-actions/+merge/197066 [13:27] larsu, looking [13:27] larsu, do you know why charles did it the complex way rather than the simple one? [13:28] seb128: probably because he didn't know about g_settings_create_action when he wrote this, or that function didn't exists back then. I'll ask him for a review when he's up [13:29] larsu, it's thanksgiving, he's off until next week (like most americans) [13:29] ah, right :-/ [13:29] larsu, I'm testing it, codes looks fine to me... do you want a second review from e.g desrt or Laney before having it approved? (I don't want to wait for next week since new glib got uploaded) [13:30] Laney: ^ [13:30] sure [13:32] It looks sensible to me but let's wait for desrt's ack [13:32] he should be along quite soon [13:33] larsu, do you want a bug report for the record/discussion with charles next week? [13:35] seb128: I can also just send him an email [13:35]