[00:55] <jdstrand> man, I just rebooted after accumulating a bunch of updates, and 3D performance is really poor with my intel graphics
[00:55] <jdstrand> eg, just opening the dash is really bad
[00:56] <jdstrand> interesting, .xsession-errors says: libGL error: failed to open drm device: Permission denied
[00:56] <jdstrand> libGL error: failed to load driver: i965
[00:56] <jdstrand> I'm guessing that would explain it
[00:56] <sarnold> permission denied? o_O
[00:59]  * jdstrand guesses it is the mesa update
[00:59] <mdeslaur> jdstrand: you're supposed to do what everyone else does and blame apparmor first :)
[01:00] <jdstrand> hehe
[01:00] <jdstrand> I don't confine compiz or X
[01:00] <jdstrand> I probably should :P
[01:00] <mdeslaur> then you fall back to blaming upstart :)
[01:00] <jdstrand> :)
[01:01] <jpds> http://i.qkme.me/3trz9o.jpg
[01:01] <mdeslaur> hehe
[01:01] <jdstrand> hehehe
[01:01] <jdstrand> nice
[01:01] <jdstrand> perfect picture
[01:02] <sarnold> :D
[01:15] <jdstrand> fyi, bug #1302270
[01:15] <ubot2> Launchpad bug 1302270 in xorg (Ubuntu) "Poor performance with recent update with i965: libGL error: failed to open drm device: Permission denied" [Undecided,New] https://launchpad.net/bugs/1302270
[02:36] <Sarvatt> jdstrand: your xorg.0.log is fine and from a recent boot but the xorg.0.log.old is using modesetting instead of intel and X was started again really late, guess you rebooted before filing it? all the dmesg info that might have helped was lost, might be worth attaching /var/log/kern.log that has the historical info
[02:45] <Sarvatt> tjaalton: ping re: ^, arrandale and might be the mesa 10.1 bug you were talking about
[02:52] <jdstrand> Sarvatt: I did not reboot before filing. I logged in, noticed it, made a comment here, did ubuntu-bug and am still running it
[02:52]  * jdstrand is testing a bunch of stuff and can't really downgrade/etc atm
[02:53] <jdstrand> I don't know about the modesetting... I don't recall messing with anything like that in ages and ages
[02:53] <jdstrand> maybe I did at some point...
[02:54] <Sarvatt> jdstrand: using kde? i think it might be https://bugs.freedesktop.org/show_bug.cgi?id=75723
[02:54] <ubot2> Freedesktop bug 75723 in Drivers/DRI/i965 "(regression since Linux 3.14?) brw_get_graphics_reset_status: Assertion `brw->hw_ctx != ((void *)0)' failed" [Major,New]
[02:54] <jdstrand> Sarvatt: unity7
[02:54] <Sarvatt> ah
[02:55] <jdstrand> I hadn't rebooted in several days at least, but had been upgrading all along
[02:55] <jdstrand> so I can't really pin point it
[02:55] <jdstrand> is any of this interesting:
[02:55] <jdstrand> [    1.716252] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver
[02:55] <jdstrand> [    1.815666] fbcon: inteldrmfb (fb0) is primary device
[02:55] <jdstrand> [    2.335498] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[02:55] <jdstrand> [    2.342002] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[02:56] <jdstrand> I have 965, but I can't remember if ^ is normal
[02:56] <Sarvatt> yeah thats normal
[02:56] <jdstrand> I figured I'd downgrade mesa when I had a chance
[02:57] <Sarvatt> your https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1302270/+attachment/4064372/+files/XorgLogOld.txt looks bad but the current one looks fine..
[02:57] <ubot2> Launchpad bug 1302270 in xorg (Ubuntu) "Poor performance with recent update with i965: libGL error: failed to open drm device: Permission denied" [Undecided,New]
[02:57] <jdstrand> that's weird
[02:59] <jdstrand> I'm still in the affected session
[03:06] <duflu> Sarvatt: Same issue with being stuck in software rendering for me today :( Permissions are broken for both DRM and my software config too (I can't change servers any more)
[03:14] <RAOF> duflu:
[03:14] <RAOF> duflu: Fallout from the systemd upload?
[03:17] <stgraber> today's changes to systemd shouldn't cause anything like that, though the upgrade may restart logind which if it can't read its state properly could cause this... in theory switching VTs may do the trick, otherwise logging out and back in should (or just reboot if you're in a hurry).
[03:18] <duflu> RAOF: I spy more (older duplicates). It's not specific to Intel graphics. But whatever sets the seat permissions isn't working (randomly)
[03:18] <jdstrand> Sarvatt: fyi, https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1302270/comments/4
[03:18] <ubot2> Launchpad bug 1302270 in xorg (Ubuntu) "[regression] Poor performance with recent update with i965: libGL error: failed to open drm device: Permission denied" [High,Confirmed]
[03:18] <duflu> Also affects nouveau and my ability to change apt configs
[03:18] <jdstrand> seems duflu came upon it
[03:18]  * duflu goes to link up the dupes
[03:18] <jdstrand> if I add myself to the video group, it works-- so yeah, something changed with the perms
[03:21] <duflu> Maybe I won't link the dupes. But it seems to be a common problem with getting permissions (nouveau too)
[03:24] <duflu> RAOF: Yeah looking at the updates I got today, only systemd starts out as suspicious
[03:25] <RAOF> systemd or cgroupmgr would be my high-suspicion targets.
[03:25] <duflu> Oh and libudev-dev
[03:25] <duflu> udev even
[03:27] <duflu> Oh, udev comes from source "systemd"
[03:27] <RAOF> Indeed it does.
[03:30] <duflu> Yes! I reverted all the systemd packages from today's update and it's fixed
[04:18] <stgraber> quick heads up, the last systemd change indeed causing this for machines without cgmanager due to extra error processing code which wasn't needed and caused an assert...
[04:18] <stgraber> jdstrand is testing fixed packages, if those work, I'll push in the archive very soon
[04:19] <stgraber> people affected may need to manually start logind after the update (not entirely clear if it'll do that on its own if it crashed before...)
[06:52] <hikiko> hello
[06:55] <hikiko> Laney, hi :) could you get a look at this branch: https://code.launchpad.net/~hikiko/unity-control-center/unity-control-center.clamp-ui-scale/+merge/214019
[06:56] <hikiko> it clamps the ui scale to a value at which the slider will remain visible
[06:57] <dholbach> hiya
[06:57] <dholbach> are things funny for anyone else on 14.04 today?
[06:57] <dholbach> I seem to have no audio interface, just a "dummy interface"
[06:57] <dholbach> and every now and then compiz is using 200% cpu
[06:58] <sarnold> dholbach: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1302264
[06:58] <ubot2> Launchpad bug 1302264 in systemd (Ubuntu) "systemd-logind assert failure: error.c:319: Assertion failed in nih_error_get: context_stack != NULL" [Critical,Fix released]
[07:04] <hikiko> dholbach, I dist-upgraded a while ago and the only "strange" thing I ve noticed was some dpkg errors
[07:06] <dholbach> hikiko, I didn't see any - which ones did you see?
[07:07] <hikiko> dholbach, these: http://pastebin.ubuntu.com/7202139/
[07:08] <dholbach> hikiko, looks like it's bug 1302300
[07:08] <ubot2> Launchpad bug 1302300 in isc-dhcp (Ubuntu) "package isc-dhcp-client 4.2.4-7ubuntu9 failed to install/upgrade: subprocess new pre-installation script returned error exit status 2" [Undecided,Fix released] https://launchpad.net/bugs/1302300
[07:09] <dholbach> hikiko, is the situation fixed on your end already? if not, you might want to try another dist-upgrade; or run sudo dpkg --configure -a
[07:09] <hikiko> no, -f didnt solve it so I guess I have to configure dpkg
[07:12] <hikiko> dholbach, with dpkg --configure -a, and apt-get -f install it's not fixed so I suppose it's a bug
[07:13] <dholbach> hikiko, did you try   sudo apt-get update; sudo apt-get dist-upgrade   as well?
[07:14] <hikiko> yes
[07:14] <dholbach> mvo, ^
[07:14] <hikiko> Preparing to unpack .../isc-dhcp-client_4.2.4-7ubuntu10_amd64.deb ...
[07:14] <hikiko> /var/lib/dpkg/tmp.ci/preinst: 17: /var/lib/dpkg/tmp.ci/preinst: Syntax error: "fi" unexpected (expecting "then")
[07:14] <hikiko> there's a syntax error in the installation script
[07:14] <dholbach> mvo, do you have an idea how to recover from an issue like that if the usual tricks (dist-upgrade, dpkg --configure -a, etc.) don't work?
[07:15] <sarnold> hikiko: you need to find a mirror that has ubuntu11
[07:16] <dholbach> ahhhh ok, that makes perfect sense - thanks sarnold
[07:16] <hikiko> I changed my repositories to use ubuntu .de :)
[07:17] <hikiko> let's see if it goes away
[07:17] <dholbach> mvo, unping :)
[07:22] <dholbach> mvo, can we make "apt-get changelog <...>" act on source package names as well? :)
[07:24] <sarnold> +1 :)
[07:25] <mvo> dholbach: let me look into that
[07:25] <hikiko> hello
[07:25] <sarnold> hikiko: success I hope? :)
[07:25] <dholbach> hikiko, better?
[07:26] <hikiko> noooo
[07:26] <sarnold> :(
[07:26] <hikiko> well
[07:26] <hikiko> dpkg
[07:26] <hikiko> decided to remove isc-dhcp-common :D
[07:26] <hikiko> so...
[07:26] <hikiko> I cant run dhclient eth0
[07:27] <hikiko> and I have no clue how to install the dhclient :p could you help me?
[07:27] <sarnold> hikiko: check /var/cache/apt/archives/ to find an old package..
[07:27] <hikiko> :D
[07:27] <hikiko> well
[07:28] <hikiko> the archived package
[07:28] <hikiko> has the syntax error
[07:28] <hikiko> so it cant be installed
[07:28] <sarnold> you may have e.g. ubuntu7 or something?
[07:28] <hikiko> no I ll download one
[07:29] <hikiko> but wont there be any dependency issues?
[07:30] <hikiko> mmm what if I download the daily build and change my sources.list to use the cd-rom to install the latest package?
[07:30] <sarnold> ooof that sounds like a lot of work :)
[07:30] <hikiko> yes :/
[07:30] <hikiko> is there any easiest way to do it?
[07:32] <sarnold> hikiko: I'd use ip or ifconfig to set an ip at random, use ip or route to add a route to your gateway, then use apt-get install isc-dhcp-whatever=specific.version.number
[07:32] <hikiko> yes!! static ip !!
[07:32] <sarnold> hikiko: bed tie for me, good luck :)
[07:33] <hikiko> thanks a lot sarnold
[07:33] <hikiko> have a good night
[07:33] <sarnold> thanks :)
[07:36] <czajkowski> morning
[07:51] <hikiko>  just for the record I have internet with my static ip but the isc-dhcp-common cannot be installed...
[08:01] <seb128> good morning desktopers
[08:01] <seb128> hey hikiko
[08:01] <seb128> hikiko, what's the issue/error when you try to install it?
[08:02] <hikiko> line 17 in a script
[08:02] <hikiko> just a sec
[08:02] <hikiko> to switch desktop
[08:02] <hikiko> and paste it
[08:02] <pitti> hey seb128
[08:02] <seb128> pitti, hey, how are you? how is IoM?
[08:03] <pitti> seb128: small, green, cold, and wet :)
[08:03] <hikiko> back :)
[08:03] <seb128> haha
[08:03] <seb128> pitti, how cold?
[08:03] <hikiko> sorry there's a new error now: http://pastebin.ubuntu.com/7202265/
[08:03] <pitti> seb128: about 8 to 10 degrees..
[08:03] <seb128> brrr
[08:04] <seb128> hikiko, do you use an outdated mirror?
[08:04] <Laney> greetings
[08:04] <Laney> happy friday, how did that happen so soon?
[08:05] <seb128> hikiko, current version is ubuntu11, it should fix the shell script error you had earlier
[08:05] <seb128> Laney, happy friday!
[08:05] <hikiko> which mirror do you use in your sources.list?
[08:05] <hikiko> I used .de
[08:06] <seb128> no mirror, archive.ubuntu.com
[08:06] <hikiko> ok I will change it then
[08:10] <Laney> hikiko: the idea seems reasonable
[08:10] <CrazyLemon> guys i dont know what was in todays update.. but 14.04 is barely usable for me untill i kill deja-dup-monitor .. compiz is also CPU hungry
[08:10] <Laney> Not sure if it's arbitrary to use the current window size though
[08:11] <hikiko> Laney, seb128
[08:11] <Laney> Maybe it could instead say 'a 640x480' (or whatever) window must fit on the screen
[08:11] <hikiko> hello
[08:11] <Laney> hey!
[08:11] <Laney> also can you have the same issue with the gtk values or not?
[08:11] <hikiko> I have a branch for review
[08:12] <hikiko> Laney, seb128 there was a problem with the mpt's design for u-c-c: that when a toplevel win is larger than the screen size, the window manager places it to a predefined position and ignores the program's requests
[08:12] <hikiko> so I ve done a new branch where we just clamp the values
[08:12] <hikiko> https://code.launchpad.net/~hikiko/unity-control-center/unity-control-center.clamp-ui-scale
[08:12] <Laney> yeah that's what I'm looking at
[08:13] <hikiko> this branch has another "issue" but bregma said it's acceptable
[08:13] <hikiko> the issue is that
[08:13] <hikiko> the window size depends on 2 parameters
[08:13] <hikiko> 1- an integer scale factor
[08:14] <hikiko> 2- the size of the widgets it contains that depend on their font size and number of characters etc and it's not predictable
[08:15] <Laney> It's why a dialog would be better, but I get that we are where we are
[08:15] <hikiko> so, since in order to clamp the slider we take the window size into account
[08:15] <hikiko> for different scale factors in gsettings
[08:15] <hikiko> the user might see the slider clamped to a different value
[08:16] <hikiko> eg: for scale factor 1, clamp=1.88 for scale factor 1.5 clamp = 1.75
[08:16] <seb128> what do you call "clamp"? you limit the max value to what would put the dialog offscreen?
[08:16] <hikiko> yes
[08:16] <hikiko> not the dialog, the u-c-c window
[08:16] <hikiko> there's no dialog
[08:16] <seb128> that's what I called dialog, sorry
[08:17] <seb128> but limiting the values range seems fine to me
[08:17] <hikiko> so, the window never exceeds the screen boundaries
[08:17] <seb128> before we landed the slider I was already suggesting to limit to 2
[08:18] <hikiko> but the user might see different clamp values
[08:18] <seb128> because in practice nobody is going to want to go over 2
[08:18] <hikiko> well now it's limited to 1.75-1.88 in normal screens
[08:18] <hikiko> because in 2 it goes offline
[08:18] <hikiko> :s/offline/offscreen :p
[08:18] <hikiko> sorry
[08:18] <hikiko> :)
[08:19] <seb128> that approach seems reasonable to me
[08:19] <hikiko> great :)
[08:19] <hikiko> I just wanted to make sure
[08:19] <hikiko> that there's no problem!
[08:19] <seb128> it's a bit hackish, but that should do
[08:19] <seb128> Laney, what do you think?
[08:20] <Laney> I was suggesting to use some reference size instead of the size of the current window
[08:20] <Laney> but the idea is fine
[08:20] <seb128> that would work for me as well
[08:20] <seb128> seems even easier
[08:20] <hikiko> what do you mean by reference size?
[08:20] <seb128> don't get the geometry, just a fixed value
[08:21] <Laney> like "you can't make a 600px window go oversize"
[08:21] <Laney> or whatever constant
[08:21] <hikiko> that's what I am doing
[08:21] <hikiko> aaa
[08:21] <hikiko> no
[08:21] <hikiko> well
[08:21] <hikiko> I might not explain it well
[08:22] <seb128> you do
[08:22] <hikiko> instead of limiting the win size to <fixed pixels>
[08:22] <hikiko> I limit it to <screen's pixels>
[08:22] <hikiko> in both cases there will be an unpredictable maximum value
[08:22] <Laney> But you perform your calculation based on the height of the window
[08:23] <Laney> right?
[08:23] <hikiko> no
[08:23] <hikiko> what I do
[08:23] <hikiko> is that:
[08:23] <Laney> + gtk_window_get_size (win, &win_width, &win_height);
[08:23] <hikiko> I check that the window height
[08:23] <hikiko> doesnt exceed
[08:23] <hikiko> the screen height
[08:23] <hikiko> because height <= width
[08:23] <hikiko> and I want the window
[08:23] <knome> (not necessarily, what about pivot setups?)
[08:24] <hikiko> to be all visible
[08:24] <hikiko> I used to choose
[08:24] <hikiko> MIN (width, height)
[08:24] <hikiko> but that was resulting
[08:24] <knome> hikiko, can you please not use enter as punctuation? it makes the text really hard to read
[08:25] <hikiko> ok sorry
[08:26] <Laney> We understand what you're doing, my suggestion is to instead say "int win_height = 600;"
[08:26] <Laney> But I don't think it's a big deal
[08:26] <hikiko> I see :)
[08:26] <hikiko> sorry
[08:27] <hikiko> I thought you mean
[08:27] <hikiko> win_height < 600
[08:27] <Laney> It means you use a fixed size and say "A window of height 600px must always fit on the screen" instead of "This panel window must always fit on the screen" which you do at the minute
[08:27] <hikiko> Laney, I'll fix this right now! I just misunderstood it!
[08:28] <hikiko> you are right :)
[08:28] <seb128> that seems a bit less "random"
[08:28] <Laney> Well, see if it works - it'll make the code simpler
[08:28] <hikiko> yes, it's a very good idea :)
[08:28] <Laney> seb128: can you test something for me? bdmurray said it didn't work for him but it seems to here...
[08:29] <seb128> Laney, I was just about to ask you to test something for me as well :p
[08:29] <seb128> let's trade testing!
[08:29] <Laney> woo!
[08:29] <seb128> Laney, https://launchpad.net/~ci-train-ppa-service/+archive/landing-017/+packages
[08:29] <seb128> Laney, the url-dispatcher workaround from ted
[08:29] <Laney> ok, first try to reproduce this please https://bugs.launchpad.net/ubuntu/+source/whoopsie-preferences/+bug/1261096
[08:29] <ubot2> Launchpad bug 1261096 in whoopsie-preferences (Ubuntu) "whoopsie-preferences respawns whoopsie in an infinite loop" [High,Confirmed]
[08:29] <Laney> it's "start a-l-m → diagnostics, watch top for whoopsie-preferences/init spinning"
[08:30] <Laney> while I put my possible fix into a branch
[08:33] <seb128> Laney, ok, init/dbus toping
[08:33] <seb128> dbus-monitor says
[08:34] <seb128>       string "ARG0=/com/ubuntu/Upstart/jobs/startpar_2dbridge/whoopsie_2d_2dstopped"
[08:34] <hikiko> Laney, there's a define: #define MINIMUM_HEIGHT 530 because according to gnome wiki: In order to fit on Netbooks screens all panels should be 675x530px
[08:34] <hikiko> maybe I should just use this
[08:36] <Laney> seb128: lp:~laney/whoopsie-preferences/g-spawn-sync
[08:38] <Laney> man that guy loves doing things in upstart jobs
[08:38] <seb128> lol
[08:38] <Laney> I'd have expected some defensive measures in the code too
[08:39] <Laney> With this you can still get it created with the wrong permissions, they'll just get fixed up later
[08:41] <seb128> do you want to block the landing on that?
[08:41] <Laney> lemme see what happens now
[08:43] <seb128> Laney, I don't understand your patch
[08:44] <Laney> https://developer.gnome.org/glib/stable/glib-Spawning-Processes.html#g-spawn-sync
[08:44] <Laney> I guessed that the call was going wrong because those flags weren't set
[08:45]  * seb128 kicks google
[08:45] <seb128> Laney, first result gave me http://www.gtk.org/api/2.6/glib/glib-Spawning-Processes.html#g-spawn-sync
[08:45] <seb128> which doesn't have that note
[08:46] <seb128> also the note doesn't explain what happens when you don't use those flags
[08:46] <seb128> it feels weird it's looping on the command
[08:46] <Laney> maybe we know a guy who knows
[08:46] <seb128> desrt, !
[08:46] <seb128> ;-)
[08:51] <seb128> Laney, that branch doesn't fix it
[08:51] <Laney> hmm ok, I didn't manage to get it again with that
[08:52] <hikiko> Laney, fixed and it works very well in my monitor :)
[08:52] <Laney> hikiko: great
[08:52] <seb128> CrazyLemon, your deja-dup issue might be https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1302416
[08:53] <ubot2> Launchpad bug 1302416 in deja-dup (Ubuntu) "deja-dup monitor was taking 6GB of memory" [Undecided,New]
[08:54] <CrazyLemon> seb128 it might.. but there was a wide number of issues which are now gone - thankfully. I changed the server from si.archive.ubuntu.com to archive.ubuntu.com and that one had all the latest bugfixed which solved every issue.
[08:54] <seb128> good
[08:55] <CrazyLemon> is there any way i can close the bug report on LP? i opened a u-c-c bug repored and i can find the 'close' button
[08:55] <CrazyLemon> cant*
[08:56] <seb128> change the status to invalid
[08:56] <seb128> the yellow round icon next to "new" in the status column
[08:57] <CrazyLemon> i found it..thanks :)
[09:00] <seb128> Laney, things go crazy when whoopsie-preferences exit
[09:01] <Laney> yeah I got it to happen again in the end
[09:01] <seb128> it's easy to trigger, just kill whoopsie-preference while the panel is open
[09:03] <Laney> url-dispatcher seems okay
[09:03] <seb128> great
[09:03] <Laney> I didn't manage to get wrong permissions yet anyway
[09:03] <seb128> I still need to restart my session
[09:04] <seb128> to see if that fix my permissions
[09:06] <Laney> it did for me
[09:08] <seb128> Laney, the whoopsie issue is that whoopsie_preferences_on_set_report_crashes() keeps being called in loop
[09:08] <seb128>     g_signal_connect (interface, "handle-set-report-crashes",
[09:08] <seb128>                       G_CALLBACK (whoopsie_preferences_on_set_report_crashes),
[09:08] <seb128>                       NULL);
[09:10] <seb128> hum, no
[09:11] <dholbach> hiya
[09:12] <dholbach> I don't know what just happened, but my keyboard settings changed to english on their own
[09:12] <dholbach> do we have a bug report for that somewhere? anything I can do to debug?
[09:12] <ochosi> maybe the ibus bug?
[09:12] <seb128> dholbach, hey, we don't know either ;-)
[09:12] <ochosi> there's one we see in xubuntu where it always falls back to en_US
[09:13] <seb128> Laney, ok, I'm going to let you debug the whoopsie thing, it's weird, it seems like whoopsie-preference keeps respawning, I guess a bug in a-l-m's code
[09:13] <seb128> dholbach, did you use another session than Unity?
[09:13] <dholbach> seb128, in the settings dialog it says that I'm still on German
[09:13] <dholbach> seb128, not recently
[09:13] <seb128> I hate keyboards
[09:14] <attente> :(
[09:14] <ochosi> dholbach: https://bugs.launchpad.net/ubuntu/trusty/+source/ibus/+bug/1284635
[09:14] <ubot2> Launchpad bug 1284635 in ibus (Ubuntu Trusty) "Keyboard layout changes after login" [High,Triaged]
[09:14] <knome> possibly unrelated, but who knows
[09:15] <seb128> attente, not saying that because of you!
[09:15] <seb128> knome, ochosi: you guys are for sure nagging about that issue :p
[09:15] <seb128> dholbach, bug #1292412 as well
[09:15] <ubot2> Launchpad bug 1292412 in unity-settings-daemon (Ubuntu) "Keyboard layout is always English(!)" [Medium,Confirmed] https://launchpad.net/bugs/1292412
[09:15] <seb128> dholbach, can you change back using the indicator?
[09:15] <ochosi> seb128: in all fairness, it's the first time *i* mentioned it
[09:15] <dholbach> ochosi, knome: I didn't use another session and it was German up until a few minutes ago - it just changed
[09:15] <seb128> dholbach, is that a one time thing?
[09:15] <dholbach> seb128, yes, first time
[09:16] <seb128> ochosi, yeah, that's true, I included you in the xubuntu group who keeps mentioning it ;-)
[09:16] <dholbach> seb128, hum, let me see if I can re-enable the indicator somehow
[09:16] <seb128> dholbach, is unity-settings-daemon running?
[09:16] <ochosi> seb128: and i only mentioned it cause it seemed ibus related and also fell back to en_US. so i think that's not too bad ;)
[09:16] <dholbach> seb128, yes
[09:16] <seb128> dholbach, since when?
[09:16] <seb128> e.g did it segfault or something?
[09:17] <desrt> seb128: hi :)
[09:17] <seb128> desrt, hey
[09:17] <desrt> what am i supposed to know? :)
[09:17] <dholbach> seb128, no crash file
[09:17] <Laney> many things, but not the thing that we thought was the thing
[09:17] <Laney> which turns out not to be the thing
[09:17] <Laney> so the thing is still an unknown thing
[09:18] <seb128> desrt, what happens if you use g_spawn_sync () with  standard_output and standard_error being NULL without using  G_SPAWN_STDOUT_TO_DEV_NULL and G_SPAWN_STDERR_TO_DEV_NULL
[09:18] <Laney> but the thing is still an interesting thing, but no longer the thing
[09:18] <desrt> they go to the stdout/err of the parent process
[09:18] <knome> seb128, hey, it's our best bet... :)
[09:18] <seb128> dholbach, since when is the process running (ps should tell you)
[09:19] <seb128> desrt, well anyway, that's probably not our issue, there is a command that seems to be ran in loop, Laney spotted that error and though it could be creating the bug, but that's not it
[09:20] <dholbach> seb128, which ps flag do I have to use for that_
[09:20] <dholbach> ?
[09:20] <seb128> dholbach, ps ux | grep unity-settings-daemon
[09:20] <dholbach> seb128, since I rebooted the machine
[09:21] <seb128> k
[09:21] <dholbach> 09:34
[09:21] <seb128> but the issue started after that?
[09:21] <seb128> attente, do we have a gsettings key or something supposed to contain the current config?
[09:22] <dholbach> seb128, yes, just 5m before I pinged you guys in here
[09:22] <seb128> dholbach, do you remember what you did just before it happened?
[09:23] <seb128> brb, need to restart my sesison
[09:23] <attente> seb128: like under /org/gnome/desktop/input-sources?
[09:24] <attente> dholbach: are you using an ibus input method?
[09:25] <dholbach> attente, no
[09:26] <attente> dholbach: if you add a different keyboard layout and switch to that, does it still persist as en_US?
[09:26] <dholbach> attente, http://paste.ubuntu.com/7202445/
[09:26] <dholbach> ok, let me trz
[09:26] <dholbach> try
[09:27] <dholbach> attente, no, doesn't seem to have an effect
[09:27] <attente> dholbach: it just happened randomly during the session or at start up?
[09:28] <seb128> seems like a similar description to bug #1292412
[09:28] <ubot2> Launchpad bug 1292412 in unity-settings-daemon (Ubuntu) "Keyboard layout is always English(!)" [Medium,Confirmed] https://launchpad.net/bugs/1292412
[09:29] <seb128> attente, it happened during the session
[09:29] <seb128> attente, the "current" key should be 0 not 1 right?
[09:29] <seb128> in his dconf's pastbin
[09:29] <dholbach> attente, during the session
[09:29] <seb128> what changes that index?
[09:29] <attente> seb128: yeah, but what flipped it
[09:30] <dholbach> does any log help?
[09:30] <attente> unity-settings-daemon, indicator-keyboard
[09:30] <seb128> attente, that's a good question... is that source handled by u-s-d only, or is ibus touching it?
[09:30] <dholbach> I think I had indicator-keyboard disabled for a long time
[09:30] <seb128> dholbach, those are in .cache/upstart
[09:30] <attente> i don't think ibus is touching it
[09:30] <dholbach> can't remember having seen it in months
[09:31] <seb128> it's not supposed to show if there is only one layout (I think)
[09:31] <attente> it shows if there is one, but doesn't if there are none
[09:31] <dholbach> unable to create file '/home/daniel/.cache/dconf/user':
[09:32] <seb128> dholbach, can you pastebin the full logs?
[09:33] <dholbach> attente, seb128: no indicator-keyboard log
[09:34] <dholbach> http://paste.ubuntu.com/7202465/
[09:35] <seb128> shrug
[09:35] <dholbach>  .cache/dconf was owned by root.root
[09:35] <seb128> wth?
[09:35] <dholbach> I have never touched it
[09:35] <dholbach> I'm quite certain of that
[09:35] <seb128> what was the timestamp?
[09:36] <dholbach> Dec 23
[09:36] <seb128> well, dconf should use XDG_RUNTIME_DIR
[09:36] <seb128> dholbach, echo $XDG_RUNTIME_DIR
[09:36] <dholbach> I installed the machine on Dec 22
[09:36] <dholbach>  /run/user/1000
[09:37] <seb128> dholbach, .cache/dconf is not supposed to be used
[09:38] <dholbach> ok, I just changed the permissions anyway
[09:38] <seb128> well, that's an issue but probably doesn't explain why the keymap changed during the session
[09:38] <dholbach> if you want I can restart the session again and see if that helps
[09:38] <seb128> attente, was there any debug info you wanted while in the session?
[09:39] <seb128> dholbach, can you share your dbus.log and gnome-session-Unity.log?
[09:40] <dholbach> sure
[09:41] <dholbach> seb128, dbus> http://paste.ubuntu.com/7202496/
[09:43] <dholbach> holy cow
[09:43] <attente> dholbach: sorry, what did you mean by you had indicator-keyboard disabled? like the process isn't running?
[09:43] <dholbach> 94M gnome-session-Unity.log
[09:43] <seb128> dholbach, hum, don't bother about sharing that
[09:44] <seb128> dholbach, maybe clean .cache/upstart, and restart your session and let's see where we stand ;-)
[09:44] <seb128> your dconf seems unhappy though
[09:44] <dholbach> attente, /usr/lib/x86_64-linux-gnu/indicator-keyboard-service --use-gtk is running
[09:46] <dholbach> seb128, http://people.canonical.com/~dholbach/tmp/gnome-session-Unity.log.xz
[09:46] <seb128> dholbach, crazyness ;-)
[09:46] <seb128> dholbach, next clean the logs and restart session and let's see how are things
[09:47] <dholbach> seb128, you mean remove the logs?
[09:47] <seb128> dholbach, yeah, jusr mv .cache/upstart/* somewhere
[09:47] <seb128> so you are sure to have only logs about the new login
[09:47] <seb128> to avoid confusion
[09:48] <dholbach> ochosi, knome: uploading xubuntu-artwork - just a small note: it's "LP: #123456", not "LP #123456@
[09:48] <ubot2> Launchpad bug 123456 in xine-lib (Ubuntu) "podcast crashes amarok" [Undecided,Fix released] https://launchpad.net/bugs/123456
[09:48] <dholbach> seb128, gotcha
[09:49] <ochosi> dholbach: thanks a bunch! where's that @? just to know where to avoid typos the next time
[09:50] <dholbach> ochosi, debian/changelog
[09:50]  * knome bows
[09:50] <ochosi> dholbach: weird, didn't see it here: http://bazaar.launchpad.net/~xubuntu-art/xubuntu-artwork/trusty/revision/263
[09:50] <ochosi> it says "Add new wallpaper for Trusty (LP #1298711)"
[09:50] <ubot2> Launchpad bug 1298711 in xubuntu-artwork (Ubuntu) "[UIFe] New Xubuntu wallpaper" [Undecided,Fix committed] https://launchpad.net/bugs/1298711
[09:51] <ochosi> or are the brackets what you shouldn't be there?
[09:52] <dholbach> ochosi, the :
[09:53] <ochosi> dholbach: weird, i also don't see a ":" there. are we using different char-encoding?
[09:54] <knome> ochosi, you *should* have the :
[09:55] <dholbach> seb128, .dbus and .gvfs and .config/enchant also belonged to root
[09:55] <dholbach> I changed them as well and will now move the logs and restart
[09:55] <seb128> dholbach, what did you do to your box?
[09:55] <seb128> dholbach, k
[09:55] <dholbach> seb128, as I said: fresh install before Christmas, almost no changes
[09:55] <ochosi> dholbach: oh ok, sry, now i get it. will keep that in mind"
[09:56] <dholbach> I even still have the default wallpaper
[09:56] <seb128> dholbach, you must have run a graphical app under sudo that screwed up with your directories
[09:56] <dholbach> I guess
[09:56] <dholbach> brb
[09:58] <dholbach> no dice :(
[09:58] <seb128> still buggy?
[09:58] <dholbach> this is going to be a very long day :(
[09:59] <dholbach> yes
[09:59] <seb128> can you share your new logs?
[09:59] <dholbach> sure
[10:00] <dholbach> seb128, people.canonical.com/~dholbach/tmp/upstart.tar.xz
[10:01] <seb128> dholbach, so what is buggy? still the keyboard?
[10:02] <dholbach> seb128, yes, still English and I can't change it
[10:02] <dholbach> I added a new keyboard layout, switched back, etc
[10:05] <seb128> dholbach, is unity-settings-daemon running?
[10:06] <seb128> dholbach, $ lsof -p $(pidof unity-settings-daemon)| grep libkeyboard
[10:08] <dholbach> seb128,
[10:08] <dholbach> unity-set 2074 daniel  mem       REG                8,5    57152  791889 /usr/lib/unity-settings-daemon-1.0/libkeyboard.so
[10:09] <seb128> dholbach, can you unity-settings-daemon --replace --debug
[10:09] <seb128> then try to change keymaps using the keybinding your configured/which is listed in the keyboard settings
[10:09] <seb128> than copy the log?
[10:11] <dholbach> seb128, super+space
[10:11] <dholbach> seb128, that made it switch back
[10:11] <dholbach> maybe I hit it accidentally?
[10:11] <seb128> well, that doesn't explain why the indicator is not working
[10:11] <dholbach> still I should have been able to switch back, right?
[10:12] <seb128> picking a layout should work
[10:12] <seb128> does it work now?
[10:12] <attente> is the indicator changing the dconf setting?
[10:12] <dholbach> seb128, I changed the layout in the settings page
[10:12] <dholbach> seb128, I don't have a keyboard indicator - I think I must have clicked "don't show indicator" somehwere
[10:12] <seb128> dholbach, that was not working earlier?
[10:12] <dholbach> how can I get it to show again?
[10:12] <dholbach> seb128, changes in the settings page didn't do anything
[10:12] <seb128> it's at the bottom of the settings dialog
[10:13] <dholbach> it was just super+space which fixed it
[10:13] <dholbach> ahhh, there it is
[10:13] <seb128> hum, it's confusing
[10:13] <seb128> is the setting page working now if you change
[10:13] <seb128> does it get buggy again if you use ctrl-space?
[10:13] <seb128> super-space rather
[10:13] <dholbach> seb128, ok: super-space works, indicator works too, changes in the settings page don't work
[10:14] <dholbach> does that clear it up?
[10:14] <dholbach> attente, ^
[10:14] <dholbach> thanks a lot for the help
[10:15] <seb128> dholbach, I'm unsure the settings are supposed to change the active one, they change the order
[10:15] <seb128> dholbach, so you basically hit super-space by error and didn't know the keybinding/had the indicator hidden so you didn't have a way to go back
[10:15] <tjaalton> ok to add this to u-s-d? https://github.com/GNOME/gnome-settings-daemon/commit/3a8beaaf380a483ce33363031d8d276c371d7af1
[10:16] <dholbach> seb128, yes, that's the case
[10:16] <seb128> tjaalton, https://launchpadlibrarian.net/171554356/unity-settings-daemon_14.04.0%2B14.04.20140310-0ubuntu2_14.04.0%2B14.04.20140402-0ubuntu1.diff.gz ?
[10:16] <tjaalton> seb128: ooh
[10:16] <seb128> dholbach, ok, sorry it took us so many step to understand the issue
[10:16] <tjaalton> should've checked
[10:17] <dholbach> seb128, no worries - I could have thought of using super+space myself ;-)
[10:18] <seb128> dholbach, the fact that you are hidding the indicator also didn't make it obvious to change back
[10:18] <seb128> or to show the actual layout
[10:19] <seb128> attente, NOTABUG in the end ;-)
[10:19] <seb128> attente, have a good w.e btw!
[10:19] <seb128> tjaalton, ;-)
[10:19] <tjaalton> makes ara happy :)
[10:20] <seb128> great!
[10:20] <dholbach> attente, seb128: thanks!
[10:20] <seb128> dholbach, yw!
[10:21] <tjaalton> hmm, something else is missing though, micmute on my thinkpad doesn't seem to work
[10:24] <tjaalton> cgmanager takes 100% cpu after dist-upgrade
[10:24] <Laney> get a bt of what it's doing and file a bug
[10:25] <Laney> that's a stgraber thing
[10:25] <tjaalton> hmm no it didn't dist-upgrade, wth
[10:25] <tjaalton> ok I'll try again after this is done
[10:25] <tjaalton> maybe micmute will work too :P
[10:26] <seb128> Laney, https://code.launchpad.net/~hikiko/unity-control-center/unity-control-center.clamp-ui-scale/+merge/214019 looks fine to me, wdyt?
[10:27] <Laney> seb128: looks ok indeed
[10:27] <seb128> ok, great, let me test build/run it and then put it in a silo
[10:29] <tjaalton> seb128: yep micmute works after all.. phew
[10:29] <seb128> tjaalton, great!
[10:30] <seb128> bah, I'm again having a non working ssh agent
[10:30] <seb128> xnox, stgraber: is there any chance somebody look at those upstart script issues?
[10:30] <seb128> often ssh-agent is taking over gnome-keyring-daemon's agent and I end up with a non working config
[10:33] <xnox> seb128: correct. we don't have jobs for seahorse...
[10:34] <xnox> seb128: i think we should add gpg, ssh, secret-service upstart jobs such that gnome-keyring would take over, on top, again.
[10:37] <seb128> xnox, the issue is not seahorse, it's gnome-keyring (that's the agent for ssh/gpg)
[10:38] <xnox> seb128: right, and gnome-keyring ships 4 xdg/autostart files, which race with upstart's ssh-agent job. And gnome-keyring, ideally should provide 4 upstart jobs. Or drop in an override to disable ssh-agent.
[10:39] <xnox> seb128: you can try $ echo manual > ~/.config/upstart/ssh-agent.override
[10:39] <xnox> seb128: and can you tell me if that fixes everything for you?
[10:39] <seb128> https://launchpad.net/ubuntu/+source/openssh/1:6.6p1-1 had changes to help there
[10:39] <seb128>   * Don't start ssh-agent from the Upstart user session job if something
[10:39] <seb128>     like Xsession has already done so (based on work by Bruno Vasselle;
[10:39] <seb128>     LP: #1244736).
[10:39] <ubot2> Launchpad bug 1244736 in gnome-session (Ubuntu) "upstart configuration for user launches an extra ssh-agent" [Undecided,Confirmed] https://launchpad.net/bugs/1244736
[10:39] <seb128> xnox, ok, let me try that
[10:40] <seb128> xnox, thanks
[10:41] <xnox> yeah, that helps preventing duplicate ssh-agents, it doesn't help that we want gnome-keyring to be our SSH agent on the desktop and take that role over the top of `ssh-agent' =)))
[11:04] <seb128> xnox, do we do anything to uninstall indicator-sync on upgrades?
[11:04] <seb128> (I still have it installed)
[11:05] <xnox> seb128: well, we will need to sru something in the indicator-sync for stable releases to e.g. become a dummy empty package.
[11:05] <xnox> seb128: or maybe we can make something conflict and replace it?
[11:06] <seb128> not sure
[11:07] <seb128> we should at least teach update-manager/the dist upgrader to uninstall it on upgrade
[11:07] <seb128> there is a list of deprecated packages/things to clean iirc
[11:54] <seb128> Laney, do you have an opinion on https://code.launchpad.net/~seb128/unity-control-center/depends-on-indicators/+merge/212137 ?
[12:01] <Laney> seb128: I agree with you both, so feel free to do it
[12:01] <seb128> Laney, thanks, I'm going to push that through today, it starts becoming a frequently reported issue on e.u.c
[12:57] <pesari> hey, do you think that the trusty kernel will be backported to precise ~soon?
[13:02] <xnox> pesari: only just after trusty release.
[13:02] <xnox> pesari: by end of ~monthish.
[13:02] <pesari> okay sounds good, thanks
[13:02] <xnox> pesari: in practice it will only be ready and supported with 12.04.5 approximatelly targeted for august.
[13:03] <pesari> ok
[13:03] <xnox> cause X and related packages would need updates as well, but 12.04.5 desktop images will default to trusty hwe stack.
[13:03] <xnox> (hwe = hardware enablement)
[13:14] <brainwash> tedg: hey, we are testing a patch to start indicator-services via upstart in xubuntu. it works fine, but we need to hide the autostart launchers, so that they don't show up in our autostart managing app. is the right approach to remove XFCE from OnlyShowIn= or add it NotShowIn= ?
[13:15] <brainwash> I've edited the .desktop files accordingly and the indicators still launch properly for me
[13:15] <tedg> brainwash, Remove from OnlyShowIn
[13:17] <brainwash> what about indicator-bluetooth and -power? they don't have this line
[13:17] <xnox> brainwash: tedg: the right aproach is to ship override in the /usr/share/upstart/xdg no?
[13:17] <xnox> brainwash: tedg: cause that xdg dir is added in sessions that are managed by upstart, which xubuntu is.
[13:17] <tedg> xnox, Read backlog from yesterday :-)
[13:17] <xnox> tedg: oh, i'm so out of date, always =)
[13:18] <tedg> xnox, Yes, this is about their configuration app, not starting them :-)
[13:18] <brainwash> exactly :)
[13:18] <xnox> tedg: bah, meh. I'm wrong as always =)
[13:18] <tedg> brainwash, Hmm, does your configuration app use the OnlyShowIn attribute?
[13:18] <brainwash> we don't want to confuse the user with showing unfunctional autostart launchers in our config app
[13:18] <tedg> brainwash, Guessing it's ignoring that? Because if it's "OnlyShowIn" for Unity it really shouldn't show up.
[13:19] <brainwash> right, but -sound and -application do contain XFCE
[13:19] <tedg> Yes, those should go. But I'm worried it won't be a complete solution if the app doesn't look at OnlyShowIn.
[13:19] <brainwash> -power and -bluetooth don't even have OnlyShowIn
[13:20] <tedg> Oh, that's right, their updates are still stuck in CI Train.
[13:20] <brainwash> it does consider OnlyShowIn
[13:20] <brainwash> -session and -datetime are already hidden
[13:20] <tedg> seb128, Can we land all the startup fix branches?
[13:20] <seb128> tedg, I doubt it so close from release
[13:20] <xnox> tedg: prepare SRUs
[13:20] <seb128> tedg, we seem to already have issues with the ones we landed
[13:20] <tedg> seb128, We kinda need them to fix this issue on XFCE
[13:21] <brainwash> we are still testing the patch to launch them via upstart
[13:21] <tedg> seb128, And we're fixing those, but we need them to be consistent to have a good fix.
[13:21] <seb128> tedg, they were complaining about -sound yesterday which has the branch landed
[13:22] <tedg> seb128, Yes, and they're testing the fix for that, but it breaks other indicators because they're not consistent.
[13:22] <seb128> shrug, what a mess
[13:22] <brainwash> long story =S
[13:22] <seb128> we should have stayed on the old autostart
[13:23] <tedg> No, we should have landed the startup fixes in Feb when they were done and just moved on :-)
[13:23] <seb128> so we have even more bugs today
[13:23] <seb128> I hate those changes, they are bringing complexity and bugs without benefits
[13:24] <seb128> which is why I've tried to stay away from them
[13:24] <seb128> I'm not going to block others to land them, but I'm not really wanting to step into that
[13:24] <tedg> They're removing code that is maintained in libindicator which is poorly done to Upstart, which has a better process management.
[13:24] <seb128> except that upstart is not managing all sessions
[13:24] <seb128> so we end up keeping the old way
[13:24] <seb128> and adding the new one
[13:25] <seb128> not to mention that we now get stuff like indicators not stopped on the greeter
[13:25] <seb128> which let cgroups/logged users actives where they shouldn't
[13:25] <Laney> Pretty sure you don't want to mess with OnlyShowIn
[13:25] <Laney> Those desktop files have NoDisplay=true so whatever UI ought not to be showing them
[13:25] <tedg> I'm all for dropping the old way. It's just there for compatibility with folks like GNOME2.
[13:26] <tedg> seb128, Those bugs would have happened regardless, because I'm betting in that case dbus is sticking around too. Because if it died, the indicators would die.
[13:27] <seb128> could be
[13:27] <seb128> anyway it feels like close from release to land those
[13:27] <seb128> if you get Laney/release team about it those I can put a landing for you though
[13:28] <seb128> I just decline responsability for bugs that are coming from those changes
[13:28] <tedg> I feel like we need consistency or we're just going to find rough edges if they don't work the same.
[13:28] <Laney> What's the problem if they're started by both in reality?
[13:28] <Laney> The second one just bails out
[13:28] <brainwash> we'll investigate and see if we can simply hide the launchers based on NoDisplay=true
[13:29] <tedg> Laney, The issue right now is that not all the indicators have the NoDisplay entry in the upstart directory.
[13:30] <tedg> There's no real consistency
[13:31] <Laney> I mean for trusty, for umbongo we can do the good thing when there's 6 months to fix stuff
[13:31] <Laney> The only problem I have on my !upstart session is that application doesn't work
[13:31] <knome> the problem is that trusty is the LTS, umbongo isn't
[13:31] <Laney> because of the no watchers thing
[13:31] <Laney> that's not the problem
[13:31] <Laney> if there was a big issue then it would be
[13:31] <Laney> but there isn't
[13:32] <Laney> That's a reason to not do risky things less than a week before the final freeze
[13:32] <tedg> For trusty we have some indicators doing the NoShowIn in /etc/xdg and some have Hidden in /usr/share/upstart/xdg
[13:33] <knome> i vote for consistency, whatever the way it was
[13:33] <knome> we will adapt to that.
[13:33] <tedg> We do have the watchers thing as well, not sure how the folks are handling that now.
[13:34] <Laney> The hidden thing is right, but I don't get what the actual problem is with leaving it inconsistent
[13:34] <Laney> We discovered straight away that one desktop isn't ready for the change
[13:35] <Laney> (that came because OnlyShowIn there was updated to include XFCE)
[13:35] <Laney> (the other ones just have Unity which is fine with it)
[13:39] <tedg> The branches have been in queue since the middle of Feb. Saying "too late" seems like a bad answer.
[13:44] <dobey> Laney, seb128: do you guys usually build system-settings with srcddir == builddir or something?
[13:44] <seb128> I usually bzr bd it and work in the builddir
[13:49] <seb128> Laney, btw, do you receive/filter the "request review" emails? or do those end up in your spambox?
[13:49] <Laney> for what?
[13:49] <seb128> spam->launchpad ;-)
[13:49] <seb128> Laney, u-c-c, I was wondering if you saw e.g https://code.launchpad.net/~seb128/unity-control-center/crp-gcc-unity/+merge/214018
[13:50] <Laney> yeah but Robert had already done it
[13:50] <seb128> right, I sent it yesterday morning though and it was a trivial one
[13:50] <seb128> I was wondering if you queue/flush or if you didn't see it
[13:50] <seb128> I would usually be fine waiting some days, but we are getting close from freeze ;-)
[13:50] <Laney> I did queue it but then didn't get back to it that day
[13:51] <Laney> soz
[13:51] <seb128> k, fair enough
[14:02] <seb128> tedg, speaking about indicator upstart jobs, do you have any idea about https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1302123 ?
[14:02] <ubot2> Launchpad bug 1302123 in indicator-application (Ubuntu) "Won't respawn when restarting unity-panel-service" [High,Confirmed]
[14:04] <tedg> seb128, Yup, fixed in the branch.
[14:04] <seb128> tedg, "the" branch?
[14:04] <tedg> seb128, It's also the reason nm-applet doesn't show on the greeter
[14:04] <tedg> seb128, The startup-cleanup branch for indicator-application
[14:05] <seb128> tedg, no, I landed that branch a month ago
[14:05] <seb128> tedg, http://bazaar.launchpad.net/~indicator-applet-developers/indicator-application/trunk.14.04/revision/246
[14:05] <tedg> seb128, yeah, the problem there was that I hadn't pushed the last changes to it :-(
[14:05] <seb128> tedg, sorry, more recently, https://launchpad.net/ubuntu/+source/indicator-application/12.10.1+14.04.20140324-0ubuntu1
[14:05] <seb128> tedg, there is still no mp with those fix that I can see?
[14:06] <seb128> tedg, https://code.launchpad.net/indicator-application/+activereviews
[14:06] <tedg> https://code.launchpad.net/~ted/indicator-application/startup-cleanup/+merge/212726
[14:06] <tedg> I forgot to change it's status :-(
[14:07] <seb128> thanks
[14:07]  * seb128 test build that
[14:16] <tedg> seb128, It looks like bug 1296715 has LO setting those actions to disabled. We're rendering it correctly.
[14:16] <ubot2> Launchpad bug 1296715 in libreoffice (Ubuntu) "Menu items are greyed out in Libreoffice menu." [Undecided,New] https://launchpad.net/bugs/1296715
[14:16] <seb128> tedg, thanks for investigating
[14:16] <tedg> Sweetsha1k, ^
[14:16] <seb128> Sweetsha1k, ^ one for you
[14:17] <tedg> Oh, one thing to note that screwed me up, It's not the "add" menu but the "insert" menu. Guessing a reverse translation.
[14:18] <tedg> Started with "Oh, my, the whole add menu is missing!"
[14:18] <Sweetsha1k> seb128, ricotz: libreoffice 4.2.3.3 tagged upstream, tarballs build, source package build, binaries building locally right now ...
[14:18] <Sweetsha1k> tedg: meh
[14:19] <Sweetshark> lucky me. That bug by tedg was for that Sweetsha1k guy, not for me.
[14:19] <seb128> Sweetshark, sponsoring time!
[14:20] <seb128> lol
[14:21] <Sweetshark> seb128: is the accessodf thing sponsored btw? see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743634
[14:21] <ubot2> Debian bug 743634 in libreoffice-accessodf "libreoffice-accessodf: MessageBox API changed in LO 4.2 :/" [Important,Open]
[14:22] <seb128> Sweetshark, no, that's what happens when you use IRC pings rather than bugs/ubuntu-sponsors :p
[14:22] <seb128> Sweetshark, let me do it now
[14:22] <Sweetshark> seb128: thx
[14:23] <seb128> Sweetshark, done
[14:29] <seb128> Sweetshark, bah, got rejected, the version is older than the one in trusty-proposed
[14:31] <Sweetshark> seb128: urgh, seeing that now - will fix that.
[14:32] <seb128> thanks
[14:47] <l3on> darkxst around ?
[14:58] <seb128> l3on, he's in .au, it's like middle of the night there
[14:58] <l3on> thanks seb128 :)
[14:58] <seb128> yw
[14:59] <Sweetshark> seb128: next try http://people.canonical.com/~bjoern/trusty/accessodf_0.1-4ubuntu1_source.changes and http://people.canonical.com/~bjoern/trusty/accessodf_0.1-4ubuntu1.diff
[15:02] <ricotz> Sweetshark, nice, did you push the source-package somewhere already?
[15:03] <Sweetshark> ricotz: not yet, will do if the build finishes ...
[15:03] <Sweetshark> ... and whatever
[15:04] <Sweetshark> ricotz: pushing it now.
[15:04] <Sweetshark> s/and/ah/
[15:04] <ricotz> Sweetshark, alrighty ;)
[15:09] <seb128> Sweetshark, https://launchpad.net/ubuntu/trusty/+source/accessodf/0.1-4ubuntu1
[15:15] <Sweetshark> seb128: \o/
[15:21] <seb128> mvo, do you think you could have a look to https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1301776? Not sure if that's a compiz or update-manager issue (I mentioned it to Trevinho some time ago in the cycle)
[15:21] <ubot2> Launchpad bug 1301776 in update-manager (Ubuntu) "Update manager is really small and not resizeable" [High,Confirmed]
[15:34] <mvo> seb128: looking
[15:34] <seb128> mvo, danke
[15:41] <mvo> seb128: hm, looking at the code it might be on purpose, is design cool with the window being resizable?
[15:41] <seb128> mvo, I don't know, that's a question for mpt ;-)
[15:42] <seb128> mvo, if it's on purpose, can we make it a bit less small maybe? https://launchpadlibrarian.net/171657786/update-manager-is-small.png is a bit ridiculous ;-)
[15:42] <Sweetshark> ricotz: packages are at https://launchpad.net/~bjoern-michaelsen/+archive/libreoffice-staging
[15:43] <mvo> seb128: aha, I think I get it - with details its supposed to be resizable, when no details are there it seems to be its not supposed to be resizable
[15:44] <seb128> mvo, I'm never going to understand designers I think, why don't they let users resign their windows if they want? ;-)
[15:44] <ricotz> Sweetshark, thx!
[15:46] <seb128> bregma, andyrock: what's the status of the lockscreen/power manager? any chance it lands this week still?
[15:46] <seb128> bregma, you should probably put a landing back for the force quit dialog thing as well
[15:48] <bregma> seb128, I'll be doing that Unity landing in a bit
[15:48] <bregma> seb128, I've already pinged andyrock on the lockscreen status, I'm waiting for his reply
[15:49] <seb128> bregma, ok, thanks
[15:49] <Laney> seb128: http://people.canonical.com/~laney/package-junkyard/ could you try this one please
[15:50] <seb128> mvo, well, even if we let resize the default shouldn't be that small
[15:51] <andyrock> bregma, can land tomorrow if I work tomorrow
[15:52] <seb128> Laney, seems to fix it
[15:52] <andyrock> seb128, ^^^
[15:52] <Laney> seb128: *phew*
[15:52] <seb128> andyrock, are you supposed to work tomorrow? ;-)
[15:52] <andyrock> it's saturday
[15:52] <andyrock> I can try
[15:52] <seb128> andyrock, right, sorry about that, but it's getting close from release freeze :/
[15:53] <andyrock> seb128, yeah and it's a complicated piece of software
[15:53] <andyrock> :D
[15:53] <seb128> Laney, well done ;-)
[15:53] <Laney> well, i don't understand why it's broken
[15:53] <seb128> andyrock, I warned you guys that it was late to land a feature like the lockscreen, when you did it...
[15:53] <Laney> but we love a good workaround
[15:53] <mvo> seb128: yeah, so this looks like this is a issue with compiz :/ I can resize just fine with metacity running
[15:54] <mvo> seb128: and the code set the correct gtk_window_set_resize(True/False) at the right spots AFAICT
[15:54] <seb128> mvo, well, different behaviour doesn't mean bug
[15:54] <seb128> k
[15:54] <seb128> so one for Trevinho then
[15:54] <mvo> seb128: how do you mean?
[15:56] <seb128> mvo, I mean that some wm let you resize things that they shouldn't, e.g the "it works with $otherwm" doesn't always mean it's compiz which is buggy (even if it's often the case ;-)
[15:57] <mvo> seb128: fair enough :) in this case it seems u-m is setting the hints at the correct times but for some reason they are not picked up
[15:57] <seb128> Laney, what is looping (I didn't look at the code)? Do we end up with something owning the bus name and a codepath trying it loop to claim it and failing or..?
[15:58] <seb128> mvo, http://irclogs.ubuntu.com/2014/03/11/%23ubuntu-desktop.html#t18:54
[15:59] <seb128> mvo, that was the previous discussion with Trevinho ... I'm going to add compiz to the bug/assign to him
[15:59] <mvo> seb128: thanks, gtg to get dinner now
[15:59]  * mvo waves
[15:59] <seb128> mvo, do you still think we should change the default geometry to bit less small though?
[15:59] <seb128> mvo, enjoy, and have a good w.e!
[15:59] <mvo> seb128: yes, that is a good idea
[16:01] <Laney> seb128: AFAICT when whoopsie-preferences went away it emitted PropertiesChanged which triggered the handler inside alm which then got into a loop with the checkbox toggled handler
[16:01] <Laney> But it's all done with gdbus-codegen so quite hard to get at
[16:02] <Laney> I think that sometimes it was seeing the wrong result for some reason
[16:03] <seb128> looks like something for desrt ;-)
[16:03] <Laney> I think the backend managed to get the opposite idea of the checkbox state to the ui
[16:03] <Laney> which triggered a loop toggling the setting on and off
[16:04] <Laney> from the property callback to the toggled callback on the togglebutton
[16:04] <seb128> k
[16:05] <seb128> isn't that a bug that whoopsie-preferences is emitting that PropertiesChanged?
[16:05] <seb128> the "out of sync" seems also a bug on the alm side
[16:05] <seb128> that code is not great :/
[16:05] <seb128> well, at least we have a working workaround
[16:05] <Laney> It does it all through gdbus so dunno
[16:05] <Laney> Never emits that signal explicitly
[16:05] <Laney> But it could be using that wrong
[16:05] <Laney> anyway ;-)
[16:21] <seb128> Laney, you didn't manage to do your shifted piloting day it seems ;-)
[16:21] <Laney> yeah, my bad
[16:22] <Laney> I'll shift it one more time(!)
[16:22] <seb128> well, monday is likely to have more in the queue ;-)
[16:22] <Laney> if it's the first thing on monday then I can't get stuck doing something else before it
[16:22] <Laney> bah
[16:22] <seb128> (assuming some contributor are going to use the w.e to get work up for review)
[16:22] <Laney> stupid gcal permissions
[16:23] <seb128> ok, on that note I'm away for a bit
[16:23] <seb128> no exercice today, I feel tired, but still going to walk around for a bit and see some outside
[16:23] <Laney> get on your bike!
[16:24] <seb128> be back in a bit to clean up emails backlog and stuff and then calling it a week
[16:24] <seb128> Laney, that's an idea ;-)
[16:24] <seb128> k, bbiab
[16:24] <seb128> have a good w.e for those who are taking off before I'm back!
[16:24] <Laney> hf, you too!
[16:25]  * Laney gets a webkit ready to upload for building over the weekend
[16:25] <Laney> will block it in proposed, that's if it actually does build ¬_¬
[16:30] <andyrock> seb128, do you know if when the screen is locked but not is on
[16:30] <andyrock> org.gnome.screensaver GetActive
[16:30] <andyrock> should be True or False
[16:30] <andyrock> ?
[17:33] <seb128> andyrock, no idea about that sorry
[21:41] <xclaesse> does mediascanner has another purpose in life than taking 100% CPU ?
[21:42] <brainwash> eating memory maybe?
[21:54] <darkxst> l3on, am now
[21:54] <l3on> darkxst, bug 1302077
[21:54] <ubot2> Launchpad bug 1302077 in nautilus (Ubuntu) "Hardcoded css style checks on GTK Theme instead of XGD_CURRENT_DESKTOP" [Undecided,New] https://launchpad.net/bugs/1302077
[21:55] <l3on> but I have to go right now
[21:56] <l3on> this tricks are odd ...
[21:56] <l3on> *these
[22:00] <l3on> even the patch ubuntu_show_titlebar.patch (always in nautilus) should be dropped. It's just a workaround because unity+compiz does not handle csd_windows correctly. You should instead fix compiz (or unity)
[22:01] <darkxst> l3on, nautilus uses a non-standard headerbar/csd implemention
[22:01] <darkxst> and Ubuntu doesnt want CSD's
[22:01] <darkxst> but Ubuntu GNOME does
[22:02] <l3on> so, you have a problem :P
[22:04] <darkxst> and the checks were based on theme, since they mess up things with high contrast and adwaita
[22:06] <l3on> so darkxst, you're in gnome-shell and you're using Ambiance. what happen to nautilus?
[22:06] <l3on> or, you're in Unity and you're using Adwaita. what happen to nautilus?
[22:07] <darkxst> first case will display without CSD's
[22:07] <darkxst> second will be with CSD's
[22:08] <darkxst> things will be a bit saner next cycle with gtk 3.12
[22:11] <l3on> ok with next cycle. but right now your patch does not work properly in Unity if users used onther theme with .header-bar { border-radius: some.px }
[22:14] <l3on> am I wrong ?
[22:17] <darkxst> l3on, overrides are only applied to ubuntu themes
[22:20] <l3on> yep, I'm wrong. Anyway you're overring also un gnome-shell if I use Ambiance. This is wrong
[22:21] <bigon> hey, so let's ask here too
[22:22] <bigon> I'm thinking about pkging nautilus-sendto 3.8 in debian (the version that removes all the plugins) now that empathy has drop its own nst plugins
[22:22] <bigon> is it a problem for you?
[22:23] <darkxst> l3on, Ambiance is very broken in gnome-shell anyway
[22:23] <l3on> someone's working on https://code.launchpad.net/~l3on/ubuntu-themes/gnome-shell-fixes