[00:23] <GunnarHj> Hi robert_ancell!
[00:33] <GunnarHj> robert_ancell: ping?
[01:55] <robert_ancell> GunnarHj, hello
[01:58] <GunnarHj> robert_ancell: Hi!
[01:59] <GunnarHj> robert_ancell: Since you were afk, I posted a comment on bug 1189382.
[01:59] <ubot2> Launchpad bug 1189382 in unity-control-center (Ubuntu) "Misleading icons for “Keyboard” and “Text Input”" [Low,Confirmed] https://launchpad.net/bugs/1189382
[01:59] <robert_ancell> yep, saw that
[02:00] <GunnarHj> robert_ancell: Isn't it a little late?
[02:00] <robert_ancell> GunnarHj, I didn't actually propose it for merging. Thought I would see how hard it would be to do
[02:00] <robert_ancell> The current state of having them split is a bit insane though
[02:01] <GunnarHj> robert_ancell: Basically I agree. And they are already interlinked.
[02:02] <robert_ancell> Yeah, it was nice to delete those silly links in the branch :)
[02:02] <GunnarHj> robert_ancell: What more exactly would the merged capplet look like? What would the name of it be?
[02:02] <robert_ancell> Keyboard
[02:03] <robert_ancell> because they all relate to the keyboard
[02:03] <robert_ancell> I'll attach a screenshot to the bug
[02:04] <GunnarHj> robert_ancell: Do IM users look for IBus settings under Keyboard? ;-)
[02:04] <robert_ancell> why wouldn't they?
[02:04] <robert_ancell> All the other keyboard shortcuts and keyboard behaviours are there
[02:06] <robert_ancell> GunnarHj, https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/883256/+attachment/4043804/+files/Merged%20keyboard%20capplet.png
[02:06] <ubot2> Launchpad bug 883256 in unity-control-center (Ubuntu) "unnecessary separation of keyboard and keyboard layout" [Wishlist,Triaged]
[02:07] <GunnarHj> robert_ancell: Maybe you are right. Guess I'm colored by the discussions on the way keyboard layout and input methods were integrated. There was much criticism. And now this last minute change...
[02:07] <robert_ancell> It's just a branch, not a change
[02:07] <GunnarHj> robert_ancell: Yeah, personally I think that screenshot looks nice.
[02:08] <GunnarHj> robert_ancell: Are you saying that you are not going to propose it for 14.04?
[02:08] <robert_ancell> The other panel that annoys me is a vague "brightness and lock"
[02:08] <robert_ancell> I'll see if anyone else thinks it's worth itr
[02:08] <robert_ancell> i.e. design / seb
[02:09] <robert_ancell> I suspect it would be too late / not high enough priority
[02:10] <GunnarHj> robert_ancell: I'd vote fore too late for 14.04, but personally I'm all for it in 14.10.
[02:16] <GunnarHj> robert_ancell: In any case this shows that the creation of u-c-c opens possibilities to make the UI more sensible. :)
[02:16] <robert_ancell> GunnarHj, yes. It's kind of sad it will be obsolete so soon :(
[02:16] <robert_ancell> Should have done it years ago
[02:17] <GunnarHj> robert_ancell: Replaced by u-s-s?
[02:17] <robert_ancell> yes
[05:51] <pitti> Good morning
[09:02] <seb128> good morning desktopers!
[09:06] <Laney> hey
[09:09] <mlankhorst> morning!
[09:49] <cking> I see that phone convergence code is getting creating some minor regressions on the desktop, for example: bug 1289532, can somebody look into this?
[09:49] <ubot2> Launchpad bug 1289532 in network-manager-applet (Ubuntu) "NetworkManager is polling every 4 seconds on the Desktop looking for /var/lib/ofono " [High,New] https://launchpad.net/bugs/1289532
[09:52] <seb128> cyphermox, ^
[09:52] <seb128> cking, thanks for spotting those/pointed them out
[09:53] <cking> no problem, we're making good progress in squashing these kinda issues
[11:20] <Sweetshark> Moin!
[11:23] <Sweetshark> seb128: http://people.canonical.com/~bjoern/trusty/4.2.3/ and http://people.canonical.com/~bjoern/precise/3.5.7/ubuntu6/ have the packages for sponsoring. Since we have the preliminary FFE for LibreOffice, do you need any additional redtape/bureaucracy from me?
[11:49] <seb128> Sweetshark, hey, looking
[12:01] <seb128> Sweetshark, trusty ones sponsored, looking to precise a bit later
[12:07] <Sweetshark> seb128: aye
[12:51] <ritz> seb128, thank you, you are fast
[12:51] <seb128> ritz, yw, well that one was already uploaded before, I just don't like regression on done todo items ;-)
[12:52] <ritz> hehe :)
[13:01] <Guest60910> how can install app from flash drive
[13:01] <Guest60910> ?
[13:04] <Guest60910> how can install app from flash drive?
[13:09] <cyphermox> cking: hey, looking at the NM issue; what were you using to see these wakeups again?
[13:09] <Guest60910> how can install app from flash drive?
[13:09] <cking> cyphermox, health-check
[13:09] <davmor2> seb128: don't know if you can help me, the keyboard shortcut that is now shown on a first startup from a fresh install.  Is it just unity or a different package?
[13:09] <cyphermox> because this is happening as a side-effect of g_file_monitor_directory or something; I'm never calling inotify directly :/
[13:11] <cking> cyphermox, the tool just monitors the system calls, so goodness knows where the real culprit is
[13:11] <cking> i guess gdb is the next best hunch
[13:11] <cyphermox> cking: yeah, no problem; I'll figure out how to unbreak it
[13:11] <seb128> davmor2, unity, what's the issue?
[13:12] <davmor2> seb128: the clicking on the cross to close it does nothing
[13:12] <cyphermox> I think I could jsut skipping creating that monitor at all if the directory doesn't initially exists, since the function will get called again if ofono eventually appears on the bus
[13:14] <Guest60910> how can install app from flash drive?
[13:17] <timmytimtimo> i need help?
[13:18] <seb128> timmytimtimo, that channel is not an user support one, try #ubuntu
[13:48] <kgunn> seb128: ping
[13:48] <seb128> kgunn, contentless ping warning
[13:57] <jdstrand> seb128: fyi in case you haven't seen it: bug #1288241. Not saying you should treat it special, just want to get it on your radar if it isn't
[13:57] <ubot2> Launchpad bug 1288241 in lightdm (Ubuntu) "gnome-screensaver is running twice and prompts twice to unlock" [High,Confirmed] https://launchpad.net/bugs/1288241
[13:58] <jdstrand> I guess I could use rls-t-incoming
[13:58]  * jdstrand does so
[14:00] <seb128> jdstrand, hey, I saw it, I'm unsure to understand how that can happen though
[14:00] <jdstrand> me too, yet, it does
[14:01] <seb128> jdstrand, note that there is also bug #1292451
[14:01] <ubot2> Launchpad bug 1292451 in unity (Ubuntu) "screensaver re-locks itself after unlocking if the configured screen-off timer goes off while screen is locked" [High,Confirmed] https://launchpad.net/bugs/1292451
[14:01] <seb128> andyrock is supposed to work on those issues and said he would have a fix on monday, we are still waiting though :/
[14:02] <andyrock> i fixed the double lock
[14:02] <andyrock> that's a different issue
[14:02]  * jdstrand notes he has two screensavers running right now
[14:03] <andyrock> i mean i proposed a branch
[14:03] <jdstrand> mdes laur postulated it could be related to bug 1271591
[14:03] <ubot2> Launchpad bug 1271591 in gnome-keyring (Ubuntu) "upstart job race prevents gnome-keyring from being ssh agent" [High,Triaged] https://launchpad.net/bugs/1271591
[14:03] <jdstrand> ie, some sort of upstart race
[14:03] <seb128> jdstrand, it could be, because
[14:03] <seb128> $ LC_ALL=C gnome-screensaver
[14:03] <seb128> ** (gnome-screensaver:19175): WARNING **: screensaver already running in this session
[14:04] <seb128> and it exit
[14:04] <jdstrand> interestingly, sometimes I have one screensaver, other times two, but I never seem to have 3
[14:04] <seb128> how are those started
[14:04] <seb128> ?
[14:04] <seb128> do you have a ppid? or are those dbus activated? or...?
[14:04] <seb128> but yeah, those upstart race are annoying
[14:05] <jdstrand> seb128: I promise I am not lying: http://paste.ubuntu.com/7156861/ :)
[14:05] <seb128> I wish somebody from foundation would help there
[14:05] <seb128> xnox, stgraber: ^
[14:06] <mdeslaur> FYI, I only have it running once, and am getting prompted twice to unlock
[14:07] <seb128> mdeslaur, right, that's bug #1292451 and the one andyrock is working on
[14:07] <ubot2> Launchpad bug 1292451 in unity (Ubuntu) "screensaver re-locks itself after unlocking if the configured screen-off timer goes off while screen is locked" [High,Confirmed] https://launchpad.net/bugs/1292451
[14:07] <seb128> unity and g-s both triggering a lock
[14:07] <mdeslaur> ah, yes, that looks like it
[14:07] <seb128> jdstrand issue is different
[14:08] <seb128> he manages to get 2 g-s running
[14:08] <seb128> jdstrand, can you get the /proc/$pid/environ for each (and same for the compiz process)
[14:08] <jdstrand> with both, the parent process is 'init --user'
[14:08] <seb128> jdstrand, just to see if they have the same bus
[14:08] <seb128> hum
[14:08] <seb128> so both started by upstart? wth :/
[14:09] <seb128> when do we switch to systemd? ;-)
[14:09]  * seb128 hides
[14:11] <jdstrand> seb128: UPSTART_SESSION=unix:abstract=/com/ubuntu/upstart-session/1000/2579
[14:11] <jdstrand> seb128: same for both
[14:11] <ogra_> seb128, yeah, will be fun to have to compile all your job descriptions instead of having them in plain text :P
[14:11] <seb128> jdstrand, does "initctl --session list" has both pids?
[14:11] <mdeslaur> jdstrand: do they both have the same DBUS_SESSION_BUS_ADDRESS?
[14:12]  * mdeslaur doesn't understand how two can be started when there is code in them to specifically prevent that
[14:12] <seb128> I don't know how that is possible, but it seems like an upstart bug to me
[14:13] <jdstrand> seb128: "initctl --session list" lists neither pid
[14:14] <mdeslaur> me neither
[14:14] <jdstrand> mdeslaur: re DBUS_SESSION_BUS_ADDRESS> *no*
[14:14] <mdeslaur> jdstrand:  NO???
[14:14] <seb128> so they are started by 'init --user' but not listed by initctl?
[14:15] <mdeslaur> jdstrand: how many dbus-daemons are running?
[14:15] <jdstrand> $ cat /proc/3033/environ | tr '\0' '\n'|grep DBUS_SESSION
[14:15] <jdstrand> DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-ZUvIbevG83,guid=269ab2f67b14acf19089d23953308de7
[14:15] <jdstrand> $ cat /proc/3657/environ | tr '\0' '\n'|grep DBUS_SESSION
[14:15] <jdstrand> DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-y9007CBDK2,guid=4a97bdd2ecc021bd3585368753308de8
[14:15] <seb128> jdstrand, mdeslaur: not having the same DBUS_SESSION_BUS_ADDRESS seems the only reasonable explanation at why the running instance detection doesn't work
[14:15] <mdeslaur> jdstrand: there's your problem, you're getting a screensaver for each dbus, that makes perfect sense
[14:15] <mdeslaur> screensaver is activated by dbus
[14:16] <seb128> we are back to bug #1271591 imho
[14:16] <ubot2> Launchpad bug 1271591 in gnome-keyring (Ubuntu) "upstart job race prevents gnome-keyring from being ssh agent" [High,Triaged] https://launchpad.net/bugs/1271591
[14:16] <seb128> upstart/env issues
[14:16] <jdstrand> $ ps auxww | grep [i]nit
[14:16] <jdstrand> root         1  0.0  0.0  34688  3820 ?        Ss   Mar24   0:03 /sbin/init
[14:16] <jdstrand> lightdm   1760  0.0  0.0  35592  1328 ?        S    Mar24   0:00 init --user --startup-event indicator-services-start
[14:16] <jdstrand> jamie     2579  0.0  0.0  36880  2912 ?        Ss   Mar24   0:07 init --user
[14:17] <mdeslaur> jdstrand: ps auxww | grep dbus-daemon
[14:17] <jdstrand> yeah, I see know one was for lightdm and the other for me
[14:17] <jdstrand> s/know/now/
[14:18] <jdstrand> http://paste.ubuntu.com/7156914/
[14:18] <jdstrand> so, system, accessibility, and two sessions started with different args
[14:19] <mdeslaur> jdstrand: that's normal
[14:19] <mdeslaur> jdstrand: so your /tmp/dbus-y9007CBDK2 dbus daemon is no longer there
[14:19] <seb128> clients should exit when the bus goes away no?
[14:20] <mdeslaur> seb128: not necessarily
[14:20] <jdstrand> mdeslaur: how do you know that //bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session isn't /tmp/dbus-y9007CBDK2?
[14:20] <seb128> jdstrand, check the /proc/pid/environ?
[14:21] <jdstrand> seb128: it doesn't have anything for dbus in its environment
[14:22] <jdstrand> but that does have GNOME_KEYRING_CONTROL
[14:22] <mdeslaur> jdstrand: yeah, that's the one spawned by gnome-keyring
[14:22] <jdstrand> oh, both do
[14:22] <mdeslaur> or maybe somethig else...I dunno, there is _supposed_ to be two in your session + the accessibility one
[14:23] <jdstrand> so, 2766 has DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-ZUvIbevG83. 2898 does not
[14:24] <jdstrand> and by 'does not' I mean 2898 doesn't have  DBUS_SESSION_BUS_ADDRESS in the env at all
[14:24] <mdeslaur> jdstrand: so you had a /tmp/dbus-y9007CBDK2 at some point, which went away, and you have a hanging screensaver
[14:24] <jdstrand> that seems plausible
[14:24] <jdstrand> but how to prevent that?
[14:25] <mdeslaur> jdstrand: do you have an extra file in /etc/X11/Xsession.d?
[14:26] <jdstrand> http://paste.ubuntu.com/7156950/
[14:27] <mdeslaur> wow...a lot of stuff in there that are supposed to be dead
[14:27] <mdeslaur> consolekit?
[14:28] <jdstrand> is 75dbus_dbus-launch supposed to be there?
[14:28] <mdeslaur> fwiw, this is mine: http://paste.ubuntu.com/7156960/
[14:29] <jdstrand> mdeslaur: you never see 2 screensavers?
[14:29] <mdeslaur> nope
[14:29] <Laney> Anything which adds something to STARTUP, like 75dbus and 90consolekit, doesn't get used if you are using upstart user sessions
[14:29] <mdeslaur> what's in 60seahorse*?
[14:30] <mdeslaur> Laney: right, possibly something in there isn't using STARTUP and that results in spawning a session dbus
[14:30] <jdstrand> http://paste.ubuntu.com/7156969/
[14:33] <mdeslaur> jdstrand: hrm, try removing 90apparmor-notify and rebooting?
[14:33] <seb128> jdstrand, mdeslaur: does that happen in a consistant way on every login?
[14:33] <jdstrand> mdeslaur: thinking that notify-osd is the culprit?
[14:34] <seb128> jdstrand, mdeslaur: it might be useful to install bootchart and get a chart
[14:34] <jdstrand> seb128: no, not every time
[14:34] <mdeslaur> jdstrand: yeah, perhaps notify-osd is getting triggered before dbus is up, which spawns it's own
[14:34] <seb128> those sometime give a clue about what process trigger what
[14:34] <seb128> jdstrand, you don't have it already installed by any chance? ;-)
[14:35] <jdstrand> bootchart?
[14:36] <jdstrand> no
[14:36] <jdstrand> I forget how to enable it
[14:36] <jdstrand> do you know otoh?
[14:37] <seb128> just install and reboot
[14:37] <seb128> it's enabled by default and log to /var/log/bootchart
[14:37] <seb128> well, install pybootchartgui
[14:37] <seb128> that's needed to get the images I think
[14:40] <mdeslaur> jdstrand: apparmor-notify should go in /etc/xdg/autostart
[14:42] <jdstrand> mdeslaur: should I just move it there and see if it resolves my issues?
[14:42] <mdeslaur> jdstrand: try removing 90apparmor-notify and restarting first
[14:42] <mdeslaur> jdstrand: just to see if it's that
[14:43] <jdstrand> well, note, it doesn't happen on every boot
[14:43] <jdstrand> which is highly annoying
[14:43] <mdeslaur> it's probably only happening when you have denials, as that's when notify-osd would spawn before dbus
[14:43] <jdstrand> I can trigger a denial
[14:44] <jdstrand> give me a few minutes
[14:44] <mdeslaur> in any case, it shouldn't be there as it will definitely cause the problem if the conditions are right
[14:45] <mdeslaur> but there may be more than one problem
[14:51] <seb128> jdstrand, mdeslaur: the bootchart might still be useful to confirm that
[14:52] <jdstrand> mdeslaur: you seem to be right. if I log out, make sure no screensavers are running, then login, only one is running. if I trigger a denial, apparmor-notify gives me a notification and another screensaver is started
[14:52] <mdeslaur> jdstrand: yeah, so it needs a desktop file and needs to be moved to /etc/xdg/autostart
[14:52] <jdstrand> if I kill the new screensaver, then trigger another denial, then another screensaver starts
[14:52] <seb128> shrug
[14:52] <seb128> so apparmor-notify is on the wrong environment/bus
[14:53] <mdeslaur> seb128: yes, because it's starting before the session bus, so notify-osd is spawning it's own bus
[14:53] <seb128> k
[14:53] <seb128> I knew it was the security team's fault! :p
[14:53] <seb128> mdeslaur, thanks for helping debugging!
[14:55] <jdstrand> this used to work. I wonder if it changed when we moved to upstart user sessions
[14:55] <mdeslaur> seb128: yeah, for once it's our fault :)
[14:55] <mdeslaur> jdstrand: yes, it used to work because dbus was spawned there
[14:55] <mdeslaur> jdstrand: but isn't anymore
[14:55] <jdstrand> (it may never have been 'correct', but it didn't use to do this
[14:55] <jdstrand> )
[14:56] <jdstrand> interesting
[14:56] <seb128> jdstrand, mdeslaur: I guess you are going to deal with the bug/reassign?
[14:57] <jdstrand> I will once I confirm the fix
[14:57] <seb128> thanks
[14:58] <jdstrand> seb128, mdeslaur: thanks for your help with this. it was highly annoying :)
[14:59] <mdeslaur> jdstrand: I figure for every thousand times seb blames apparmor, there can be an actual bug once :)
[14:59] <jdstrand> heh
[14:59] <jdstrand> I would draw a line between apparmor and apparmor-notify :)
[15:00] <Trevinho> larsu: hey!
[15:00] <mdeslaur> although seb128 seems to have moved to blaming upstart for everything now, so maybe we'll be ok for a while :)
[15:00] <seb128> mdeslaur, lol
[15:00] <larsu> Trevinho: hi
[15:00] <mdeslaur> ;)
[15:00] <Trevinho> larsu:  do you know what's causing some apps bg to be black (i..e dejadup) or transparent (gnome-tweak-tool)?
[15:01] <seb128> mdeslaur, I'm still annoyed on those gnome-keyring agent being unreliable, should I blame apparmor for it? ;-)
[15:01] <mdeslaur> seb128: nice try :)
[15:01] <larsu> Trevinho: yes, a combination of backgrounds not being set and overlay-scrollbars
[15:01] <larsu> Trevinho: patches welcome *cough*
[15:01] <mdeslaur> seb128: you haven't managed to get xnox to fix that yet?
[15:01] <seb128> mdeslaur, no :-(
[15:01] <seb128> Trevinho, I can't confirm for deja-dup, in what part of the UI?
[15:02] <larsu> ya, same here
[15:02] <Trevinho> larsu: ah.... I don't know what caused it but in previous version of themes it was working...
[15:02] <larsu> Trevinho: because we had a css rule "* { background-color: <something> }"
[15:02] <seb128> Trevinho, see https://code.launchpad.net/~larsu/ubuntu-themes/dont-set-all-bgs/+merge/197234 for details
[15:02] <larsu> Trevinho: setting a bg for all widgets causes other problems. For example, it's very slow
[15:03] <Trevinho> seb128: http://people.ubuntu.com/~3v1n0/shots/Schermata%20da%202014-03-26%2016:02:31.png
[15:03] <seb128> Trevinho, urg, I can't confirm that one ... do you have a locally hacked theme?
[15:03] <larsu> Trevinho: so I removed that rule and added backgrounds for widgets which were broken due to overlay-scrollbar doing crazy stuff
[15:03] <seb128> oh, I can
[15:03] <seb128> when showing the details
[15:04] <seb128> "fun"
[15:04] <Trevinho> seb128: I have but I'm using the default one I think
[15:05] <Trevinho> I mean, I'm not using the local one now
[15:05] <Trevinho> at least, settings wise
[15:05] <Trevinho> seb128: yaeh, that's on detail
[15:05] <Trevinho> seb128: maybe because it loads overlay scrollbars in that case?
[15:05] <Trevinho> larsu: ^
[15:06] <larsu> Trevinho: yep, it's very likely this is due to o-s
[15:06] <larsu> we've seen a lot of black bgs because of it
[15:07] <seb128> larsu, Trevinho: confirmed, it doesn't happen without those
[15:08] <seb128> bug #1295105 btw
[15:08] <ubot2> Launchpad bug 1295105 in OEM Priority Project trusty "Wrong background color in "Back Up" window" [Medium,New] https://launchpad.net/bugs/1295105
[15:08] <larsu> seb128: feel free to assign me to that bug while I'll go curl up into a corner and cry for a while
[15:08] <seb128> larsu, :-(
[15:08] <Trevinho> seb128: btw dejadup is never able to finish a backup without errors here.... but that's another story :(
[15:09] <seb128> Trevinho, talk to mterry!
[15:09]  * mterry hides
[15:09] <larsu> Trevinho: something about not being able to back up some files? I think it backs up anyway except for the files it mentions
[15:09]  * larsu had that one today
[15:09] <seb128> mterry, don't hide, larsu is fixed your dejadup bugs!
[15:09]  * mterry hugs larsu
[15:09] <Trevinho> larsu: no, it stops doing the backup giving me some python errror... But I never checked it in details
[15:09] <larsu> wait, what?!
[15:10] <seb128> well, he said he would look at the theme issue
[15:10] <seb128> larsu, ^
[15:10] <mterry> larsu, something for upstream/me?
[15:10] <Trevinho> it will be probably back in few time
[15:10] <seb128> mterry, https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1295105
[15:10] <ubot2> Launchpad bug 1295105 in deja-dup (Ubuntu) "Wrong background color in "Back Up" window" [High,Confirmed]
[15:10] <larsu> mterry: nah, it's a theming issue
[15:10] <Trevinho> not sure if that's because it back ups on u1?
[15:10] <larsu> Trevinho: ah okay. I'm backing up to an external hd
[15:10] <Trevinho> mterry: ah, is there a way to blacklist a file, inside a folder?
[15:11] <seb128> Trevinho, bug #1295357?
[15:11] <ubot2> Launchpad bug 1295357 in deja-dup (Ubuntu) "Backup to Ubuntu one failing code 502 upload will exceed quota" [Undecided,New] https://launchpad.net/bugs/1295357
[15:11] <mterry> Trevinho, not one single file, no
[15:11] <Trevinho> mterry: ok, np...
[15:11] <Trevinho> seb128: mh, no... it's not that... I've lot of space there
[15:11] <Trevinho> seb128: once i get the log i'll be back with details
[15:11] <seb128> k
[15:12] <jdstrand> mdeslaur: nice! I moved it over to xdg, logged out, back in, it autostarted, I triggered a denial and only one gnome-screensaver :)
[15:12] <jdstrand> \o/
[15:12] <jdstrand> seb128: ^
[15:13]  * jdstrand triages and assigns bug to himself
[15:13] <mdeslaur> jdstrand: cool!
[15:13] <seb128> jdstrand, mdeslaur: great, thanks
[15:13] <jdstrand> mdeslaur: so, I guess I've been seeing it a lot more lately since I've been profiling
[15:13] <seb128> jdstrand, don't forget to maintscript clean the conffile on upgrade
[15:13] <jdstrand> yeah
[15:13] <mdeslaur> yeah
[15:15] <seb128> desrt, hey, did you see bts like that before, https://errors.ubuntu.com/problem/f816c2a6a455ee7a2acd17284a395dee22bcc787
[15:19] <desrt> yes
[15:19] <desrt> this is the typical 'getenv is not threadsafe, gettext calls getenv, we call gettext from threads' issue
[15:19] <larsu> morning desrt :)
[15:19] <desrt> hi :)
[15:20] <desrt> seb128: we generally try to solve this issue by making sure nobody ever calls setenv()
[15:20] <desrt> so likely the program that is crashing is calling setenv() somewhere -- it needs to stop doing that
[15:20] <seb128> desrt, there is only on thread though here and the call is coming from dconf?
[15:21] <desrt> seb128: the call causing the crash is happening from the dconf worker thread...
[15:21] <desrt> #25 0xb6e11134 in dconf_context_thread (data=0x83555b8) at dconfcontext.c:11
[15:21] <didrocks> Trevinho: I guess no screen off after the timeout in the screenlock is a known issue?
[15:21] <desrt> the main() thread is missing from the trace for some reason
[15:21] <Trevinho> didrocks: yeah
[15:21] <Trevinho> didrocks: I need to fix it asap
[15:21] <didrocks> Trevinho: ok, I think you are already aware that the consequence it that you type your password, you see the screen, then it relocks… ;)
[15:22] <Trevinho> didrocks: yeah :)
[15:22] <Trevinho> didrocks: it's like: "are you really sure that you're the right guy"? :D
[15:22] <didrocks> ok, all good, leaving in your capable hands (just noticed that yesterday)
[15:22] <seb128> desrt, you are right, thanks
[15:22] <didrocks> Trevinho: yeah, with just a short, quick preview!
[15:23] <desrt> seb128: there are some setenv calls here
[15:23] <desrt> in g-k-d
[15:23] <seb128> right
[15:23] <seb128> desrt, want to open a bug upstream for us maybe?
[15:23] <desrt> but seem to be mostly in tests, though
[15:24] <seb128> desrt, daemon/control/gkd-control-server.c:					g_setenv (*e, x, FALSE);
[15:24] <seb128> daemon/ssh-agent/gkd-ssh-agent.c:	g_setenv ("SSH_AUTH_SOCK", socket_path, TRUE);
[15:25] <seb128> daemon/gpg-agent/gkd-gpg-agent.c:	g_setenv ("GPG_AGENT_INFO", agent_info, TRUE);
[15:25] <desrt> seb128: looks like you have an old version
[15:25] <seb128> desrt, that's 3.10.1
[15:25] <desrt> these calls are gone in the latest version
[15:25] <seb128> desrt, hum?
[15:25] <seb128> desrt, https://git.gnome.org/browse/gnome-keyring/tree/daemon/control/gkd-control-server.c#n152
[15:26] <seb128> desrt, they seem to still be there in trunk to me?
[15:27] <desrt> ah.. so you're right.
[15:27] <desrt> i didn't catch them because of the subdir
[15:38] <trem> didrocks: hello
[15:40] <seb128> trem, hey again
[15:40] <trem> seb128: \o/
[15:40] <seb128> trem, still not wanting to listen to my recommendation from the other day? ;-)
[15:40] <trem> seb128: ask on the chan ?
[15:40] <seb128> yes
[15:41] <trem> seb128: sorry, I still prefer to avoid it, because it's not a "public" question
[15:41] <seb128> trem, stop using the channel then, /query and ask it
[15:42] <trem> seb128: just want to say "hello" on the chan before a query
[15:42] <seb128> k
[15:42] <seb128> hey then ;-)
[15:46] <didrocks> hey trem
[16:14] <Trevinho> anyone using evolution here? As it seems that all the times I try to save attachments it hangs :o
[16:15] <Trevinho> and.... also file-roller does the same when i try to extract from a zip :/
[16:16] <Trevinho> well,  not only zips... any archive
[16:18] <seb128> Trevinho, gio issue? get a bt?
[16:18] <Trevinho> seb128: yeah it looks like that... I've to get it
[16:35] <Trevinho> seb128: I was just about to connect to the processes and n ow... no more hanging... :(
[16:35] <Trevinho> but it happened both yestedaay and today (after a reboot)
[16:35] <seb128> :-(
[16:36] <seb128> k, maybe next time you manage to get a bt
[16:36] <Trevinho> seb128: I hope no.. .I mean I don't want my apps to freeze  :D
[16:55] <ricotz> seb128, hi :), did you upload libreoffice 4.2.3~rc2 already?
[16:56] <Laney> ricotz: it's in the queue, see https://launchpad.net/ubuntu/trusty/+queue?queue_state=1
[16:57] <ricotz> Laney, ah, thanks
[16:58] <ricotz> Laney, syncing libosinfo would be nice too
[16:59] <seb128> ricotz, what Laney said, was there an issue with it?
[16:59] <Laney> ricotz: dunno what it is, please requestsync
[16:59] <ricotz> seb128, no issue, i just need to have the sources published to avoid a full-source upload for the backports
[17:00] <ricotz> Laney, it is used by e.g. gnome-boxes and debian contains a newer release with fixes
[17:01] <Laney> looking forward to the bug report then ;-)
[17:57] <mpt> cyphermox, mterry: If Ubuntu connected to a Wi-Fi network at the login screen, and that’s the same network that you use in your session, would it still have to disconnect and reconnect when you logged in?
[17:57] <mterry> mpt, no, connections are managed by a system daemon
[17:58] <mpt> Oh, of course, otherwise Remote Login would fail immediately after you logged in
[17:58] <mpt> thanks mterry :)
[18:01] <mpt> Hm, I guess that means you can’t disconnect from the current Internet connection while you are logged in remotely
[18:01] <mpt> Or at least, shouldn’t
[18:02] <mterry> mpt, :)  probs not -- maybe we were smart and disallowed permission to do so when in such a session?
[18:03] <mterry> but I bet not
[18:03] <mpt> I have no way of testing that, that I know of
[18:10] <mterry> Laney, thanks for updating that 2 year old patch for adding a position property  :)
[18:11] <cyphermox> mterry: I don't think it needed any being smart, as a guest user you may not have permission to do so in the first place
[18:11] <cyphermox> as for remote sessions, if there is a local user with sufficient permissions then yes they can disconnect you
[18:12] <mterry> cyphermox, I think you need admin privileges to create new connections, but I *thought* guests could switch to connections that have been used before.  Not sure
[21:15] <Laney> mterry: I saw it was linked to a bug that's tagged to be fixed for trusty :P
[21:15] <Laney> thought it was worth a go
[21:16] <mterry> Laney, maybe in two more years it'll be fixed
[21:16] <Laney> well, we have some people in the team who could maybe look at it if necessary
[21:24] <stgraber> hmm, so Edubuntu beta 2 gets me a black wallpaper rather than our usual one, any idea what's going on?
[21:24] <stgraber> (under uniyt)
[21:24] <stgraber> *unity
[21:25] <stgraber> we didn't change our artwork package since december so it seems like something desktopy changed
[21:27] <stgraber> hmm, not your fault apparently :)
[21:27] <stgraber> the wallpaper is 0 byte large in that image...
[21:40] <Laney> Oops