[05:43] <pitti> Good morning
[08:44] <seb128> good morning desktopers!
[08:47] <didrocks> hey seb128!
[08:47] <didrocks> good week-end?
[08:47] <seb128> didrocks, hey! yes, you ?
[08:48] <didrocks> same here, quiet but nice :)
[08:51] <seb128> quiet is good ;-)
[09:00] <pitti> bonjour seb128, ça va /
[09:00] <pitti> ?
[09:02] <seb128> pitti, salut, ça va bien et toi ?
[09:03] <pitti> seb128: je vais bien aussi, merci ! nous avons eu un bon week-end
[09:03] <seb128> pitti, le Stollen est très bon, encore merci !
[09:04] <pitti> seb128: de rien ! nous avons mangé le premier stollen hier aussi *yummy*
[09:04] <Laney> hey ho
[09:04] <seb128> Laney, hey, how are you ?
[09:04] <pitti> hey Laney, how are you? nice we?
[09:04] <pitti> "weekend"
[09:04] <seb128> pitti, *yummy* indeed ;-)
[09:04] <Laney> hey seb128 pitti
[09:05] <pitti> seb128: il était très bien après 4 heures de travail dans le jardin :)
[09:05] <Laney> was nice thank you, played my new games a bit
[09:05] <Laney> also got a grand new christmas jumper
[09:06] <pitti> err, "jumper"? that must mean something different than what I think
[09:06] <Laney> pulli
[09:06] <pitti> oh
[09:06] <pitti> right on time for the frost and snow :0
[09:07] <Laney> not the electrical component :P
[09:34] <larsu> so I can't install updates through update-manager anymore
[09:35] <larsu> "You are not allowed to perform this action"
[09:35] <larsu> I'm still in the admin group
[09:35] <larsu> seb128 says it might be a problem with my polkit?!
[09:36] <seb128> larsu, pkcheck might help to see if things are alright there
[09:37] <larsu> hm, that string is nowhere to be found in update-manager :-/
[09:38] <seb128> pkcheck seems buggy, it always opens me the manpage
[09:38]  * seb128 tried pkcheck --action-id org.debian.apt.upgrade-packages
[09:38] <seb128> or --help
[09:39] <larsu> I tried with --process <PID>, but that makes it crash
[09:39] <seb128> larsu, do you have policykit-desktop-privileges installed?
[09:40] <larsu> seb128: yes: 0.16
[09:40] <pitti> seb128: FTR, running with gtk 3.10 here since Sat, and the only regression that I noticed is that the ssh/gpg password dialogs are now very wide (not word wrapped any more)
[09:40] <larsu> passing action id and pid make pkcheck return 0
[09:40] <seb128> pitti, thanks, that's a known issue/mclasen fixed it in git this w.e
[09:40] <larsu> pitti: solved last night ;)
[09:41] <pitti> nice
[09:41] <seb128> pitti, thanks for testing it ;-)
[09:41] <seb128> larsu, I tried
[09:41] <seb128> pkcheck --action-id org.debian.apt.upgrade-packages --process `pidof update-manager`
[09:41] <seb128> but that opens the manpage still
[09:41] <larsu> heh, not for me
[09:41] <larsu> with the reverse order of arguments
[09:41] <larsu> but that hopefully doesn't matter…
[09:41] <pitti> seb128: then pidof update-manager fails and returns nothing
[09:42] <pitti> seb128: try with $$
[09:42] <seb128> larsu,
[09:42] <seb128> $ pkaction --verbose --action-id org.debian.apt.upgrade-packages
[09:42] <larsu> ah right, I pasted the actual pid
[09:42] <larsu> seb128: that opens the man pagew
[09:42] <pitti> seb128: if it's running, use pidof -x update-manager
[09:43] <seb128> pitti, larsu: yeah, my fault, of course the process is python...
[09:43] <seb128> pitti, danke
[09:43] <seb128> larsu, what are you trying to do exactly in update-manager?
[09:43] <larsu> hm, update-manager also shows me packages to update that apt-get upgrade doesn't
[09:43] <larsu> seb128: update...
[09:43] <seb128> normal ones?
[09:43] <larsu> yep
[09:44] <larsu> just the window that pops up when updates are available
[09:44] <larsu> I didn't even start it manually
[09:44] <seb128> I wonder if the environment of that process is wrong
[09:45] <seb128> can you "strings /proc/`pidof -x update-manager`/environ" and pastebin that?
[09:45] <seb128> larsu, ^^
[09:45] <larsu> the packages it wants to install are "fakeroot" and "libfakeroot"
[09:45] <larsu> apt-get upgrade doesn't want to do that
[09:45] <pitti> seb128: oh, and telepathy-gabble is broken now (immediately crashes at startup), not sure whether that's GTK; filing/looking at trace now
[09:45] <seb128> pitti, I don't know about that one, I doubt it's gtk though, telepathy connectors are non UI bits
[09:45] <larsu> seb128: http://paste.debian.net/68834/
[09:46] <pitti> right
[09:46] <seb128> larsu, env seems alright :/
[09:46] <larsu> seb128: I think the problem is the packages it wants to install
[09:47] <pitti> seb128: control center seems to have a similar (no word wrap/too wide) issue, try security&privacy
[09:47] <seb128> larsu, what action does it try to do?
[09:47] <seb128> larsu, can you screenshot the error?
[09:47] <larsu> seb128: it's just a message dialog with the string I pasted earlier
[09:47] <seb128> pitti, yeah, that issue is all dialogs
[09:47] <seb128> larsu, seeing the dialog would help to say if it's polkit or update-manager
[09:47] <pitti> seb128: ah, mclasen fixed it in gtk git, not in the keyring dialog git?
[09:48] <larsu> seb128: ah okay
[09:48] <seb128> larsu, I wonder if you are simply seeing an update-manager error because e.g those packages are un-authentificated for some reason
[09:48] <larsu> pitti: yeah, there was a global "don't make windows wider than 640px" in there which Company removed
[09:48] <pitti> larsu: ack, thanks
[09:48] <seb128> pitti, right, https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-10&id=2436627eb4644234a9e577538ec334d224e3d2be
[09:49] <larsu> pitti: which is obviously a correct fix, but we should wait to fix all the things it breaks before applying it :)
[09:49] <larsu> seb128: http://imgur.com/CUuWFrv
[09:50] <seb128> larsu, good that I asked, that's not a polit dialog :p
[09:50] <pitti> larsu: right, like https://git.gnome.org/browse/gtk+/commit/?id=b53b5578f
[09:51] <larsu> seb128: really? I can't find this string in update-manager's source either
[09:51] <seb128> larsu, it's in aptdaemon
[09:51] <seb128> that's the backend update-manager is using
[09:52] <seb128>     ERROR_NOT_AUTHORIZED: _("You are not allowed to perform this action"),
[09:52] <larsu> ah!
[09:53] <larsu> does it have something to do with the fact that apt-get upgrade doesn't want to install the new fakeroot?
[09:53] <larsu> let me try installing that manually
[09:53] <larsu> ya, that totally worked
[09:53] <seb128> my bet is that it's going to come from an unauthentificated repository or something
[09:53] <seb128> weird
[09:53] <seb128> is aptd running?
[09:54] <larsu> yes
[09:55] <seb128> do you still have the issue now that you apt-get installed it?
[09:55] <larsu> no, there's nothing more to install
[09:55] <larsu> I'll have a look again later
[09:55] <larsu> seb128: thanks for your help so far!
[09:56] <seb128> larsu, yw
[09:57] <larsu> seb128: the commit pitti linked to doesn't fix the issue for everything. I'm running the same since Friday.
[09:57] <larsu> many apps have custom message dialogs, for example gedit
[09:57] <pitti> larsu: no, there's another one for a different standard dialog, and similar fixes need to be added to every dialog which has that issue
[09:57] <seb128> larsu, see the one I listed
[09:57] <pitti> that was just one example
[09:57] <seb128> just before pitti
[09:58] <larsu> ah got it
[09:58] <pitti> the commit seb128 pointed to fixes it for everything, but AFAIUI it's just a bandaid for the stable 3.10 branc
[09:58] <pitti> that isn't in 3.11.x
[09:58] <seb128> right
[09:58] <larsu> makes sense
[09:58] <seb128> 3.10 is what we target for the LTS though
[09:58] <seb128> so if that works that's going enough for now
[09:58] <seb128> we should still fix apps though
[09:58] <larsu> famous last words
[09:58] <seb128> lol
[09:59] <seb128> it's only code, what could go wrong
[09:59] <seb128> ;-)
[10:00] <larsu> haha
[10:47] <seb128> pitti, did you get the gabble bt?
[10:48] <pitti> seb128: I sent it to errors, but I don't see it on "my reports", werid
[10:48] <seb128> pitti, e.u.c/whoopsie seem buggy
[10:48] <pitti> ah, again missing .uploaded; go whoopsie
[10:48] <seb128> didrocks reported some rb issue on friday that never made it to e.u.c either
[10:49] <pitti> https://errors.ubuntu.com/oops/53d057e6-5b3f-11e3-91f0-2c768aafd08c
[10:49] <pitti> one needs to restart whoopsie, its inotify handling is broken
[10:49] <seb128> what do you mean "missing .uploaded"? is whoopsie failing to report issues when tell it to do so?
[10:49] <seb128> shrug
[10:49] <pitti> right
[10:49] <pitti> seb128: above is my report, it has the trace
[10:50] <seb128> yeah, looking at that
[10:50] <pitti> "Source ID 4 was not found when attempting to remove it"
[10:50] <pitti> seb128: so, certainly not GTK related, more likely the new glib becoming stricter
[10:51] <seb128> pitti, do you make glib abort on errors?
[10:52] <pitti> seb128: not that I know of; it's a CRITICAL
[10:52] <pitti> so far we didn't abort on those, but maybe telepathy sets that
[10:53] <seb128> pitti, seems like https://git.gnome.org/browse/glib/commit/?id=a919be3d39150328874ff647fb2c2be7af3df996
[10:53] <seb128> that shouldn't sigabrt though
[10:53] <seb128> (doesn't for me)
[10:53] <seb128> (or maybe I just didn't run into that error with gabble)
[10:54] <pitti> #ifdef ENABLE_FATAL_CRITICALS
[10:54] <pitti>   /* make critical warnings fatal */
[10:54] <pitti>   fatal_mask = g_log_set_always_fatal (G_LOG_FATAL_MASK);
[10:54] <pitti>   fatal_mask |= G_LOG_LEVEL_CRITICAL;
[10:54] <pitti>   g_log_set_always_fatal (fatal_mask);
[10:54] <pitti> #endif
[10:54] <pitti> seb128: ah, so gabble at least supports that mode
[10:55] <pitti> seb128: and according to configure.ac it defaults to yes
[10:55] <seb128> hum, k
[10:56] <seb128> pitti, can you report the gabble issue to https://bugs.freedesktop.org/enter_bug.cgi?product=Telepathy ?
[10:56] <pitti> seb128: yes, will do
[10:56] <seb128> pitti, danke
[10:56] <seb128> we should probably turn that flag off in the package as well
[10:56] <seb128> larsu, oh, found an issue with your theme change
[10:57] <seb128> larsu, if you search in nautilus, the default/first returned item is wrongly colored
[10:58] <larsu> seb128: ah, also when the window is unfocussed
[10:58] <seb128> right
[10:58] <seb128> I noticed alt-tabbing
[10:58] <larsu> are you sure this is an issue with my change? It seems unrelated to backgrounds
[10:58] <desrt> pitti: so... how's them suspends?
[10:59] <seb128> desrt, good early morning!
[10:59] <desrt> seb128: good .. afternoon yet?
[10:59] <desrt> 1 more minute? :)
[10:59] <seb128> desrt, not sure I would describe 12 as "afternoon"
[10:59] <seb128> the afternoon is after lunch :p
[11:00] <larsu> seb128: it is indeed. I just tested.
[11:00]  * larsu hates css
[11:00] <seb128> larsu, :-(
[11:00] <larsu> this seems totally unrelated
[11:00] <desrt> seb128: time for an english lesson... ;)
[11:00] <seb128> haha
[11:00] <desrt> the etymology of the word afternoon is "after noon".
[11:01] <desrt> woh
[11:01] <desrt> TIL: forenoon is a thing
[11:01] <larsu> s/is/was?
[11:02] <desrt> it has a wikipedia page, so is...?
[11:02] <larsu> sounds like something Queen Vicoria would have said when she was a child
[11:02] <larsu> *Victoria
[11:02] <seb128> ;-)
[11:02] <desrt> and... "forenoon" != "fore noon" and "afternoon" != "after noon" as wikipedia is happy to point out
[11:02] <desrt> if you put the space in there then it goes all the way to midnight (either side)
[11:02] <desrt> without the space it typically refers only to daylight hours
[11:03] <larsu> so the afternoon is shorter in the winter?
[11:04] <larsu> and the evening starts at 4?
[11:04] <desrt> it also notes that the term has no precise definition :p
[12:38] <ogra_> seb128, Laney ... is that known ? http://people.canonical.com/~ogra/evo-theme.png ... got it with msy latest trusty upgrade last week
[12:38] <seb128> ogra_, seems like a theme issue, I think Laney mentioned it before uploading evo 3.10
[12:39] <ogra_> k
[12:53] <larsu> this looks like the issue I had in gedit
[12:53] <larsu> seb128: are my theme changes already uploaded?
[12:53] <seb128> larsu, no, neither is gtk 3.10
[12:54] <larsu> ah
[12:54] <larsu> so that's not it then :)
[12:54] <seb128> not likely no ;-)
[12:55] <seb128> larsu, do we still need gtk patches for o-s btw? (#gtk+)
[12:56] <larsu> seb128: thanks
[12:56] <seb128> larsu, thank you ;-)
[13:02] <larsu> seb128: are you okay if I put the nautilus fix on the same MR?
[13:02] <seb128> larsu, nautilus fix for?
[13:02] <seb128> oh, the icon color
[13:02] <larsu> seb128: the black icon when unfocussed
[13:02] <seb128> no problem
[13:03] <Laney> mmm, I see a suspicious change in evo
[13:03] <seb128> Laney, one that requires to adapt themes
[13:03] <seb128> ?
[13:11]  * mterry stares at seb128 to review welcome-wizard
[13:11] <mterry> seb128, I'm in (near?) your timezone!
[13:11] <seb128> mterry, hey, how is London ?
[13:11] <mterry> seb128, grey
[13:12] <seb128> stating the obvious there...
[13:12] <larsu> seb128: it's up if you want to have a look. https://code.launchpad.net/~larsu/ubuntu-themes/dont-set-all-bgs/+merge/197234
[13:12] <seb128> larsu, danke
[13:18]  * seb128 stares at mterry
[13:19]  * mterry goes back to fighting Mir
[13:19] <seb128> mterry, you are speaking about https://code.launchpad.net/~unity-team/ubuntu-system-settings/welcome-wizard/+merge/186862 ?
[13:19] <mterry> seb128, yeah
[13:19] <seb128> mterry, I reviewed that a week ago, it's Needs fixing
[13:19] <mterry> seb128, ?
[13:19] <seb128> mterry, I don't see anything happening since?
[13:19] <mterry> seb128, huh!  I didn't get an email for that
[13:20] <seb128> mterry, well, basically I'm waiting on your guys to reply to my question/address my first review comments...
[13:20] <mterry> seb128, makes sesne
[13:20] <seb128> mterry, that's probably because you down own the branch, it's a team one
[13:20] <seb128> down->don't
[13:20] <mterry> seb128, fair
[13:21] <mterry> I can't seem to subscribe to just one merge request
[13:21] <mterry> :(
[13:21] <seb128> mterry, you can add you to the reviewers list as workaround I think
[13:21] <mterry> ah, I go to the branch itself
[13:26] <cyphermox> good morning!
[13:27] <seb128> cyphermox, hey, how are you?
[13:30] <cyphermox> seb128: fabulous, and you?
[13:31] <cyphermox> it's going to be even more of an awesome day if I receive my SensorTag today, so I can start to work on 4.0/LE bluetooth
[13:34] <seb128> cyphermox, I'm good thanks ;-)
[14:07] <larsu> seb128: can I keep pushing stuff into my gtk 3.10 repo or did you make any further changes?
[14:07] <larsu> I've finally fixed the settings install thing
[14:08] <seb128> larsu, I did tweaks for the ppa upload
[14:08] <larsu> seb128: did you upload them into a bzr repo?
[14:09] <sil2100> kenvandine: hello :)
[14:09] <seb128> larsu, same lp:~ubuntu-desktop/gtk/ubuntugtk310
[14:11] <larsu> seb128: so can I consider my repo as merged and do new MRs on top of that one?
[14:11] <seb128> larsu, yes
[14:11] <larsu> s/repo/branch
[14:13] <kenvandine> good morning sil2100
[14:13] <seb128> hey kenvandine, how are you? had a good w.e?
[14:13] <kenvandine> yup
[14:13] <kenvandine> and you?
[14:14] <seb128> same ;-)
[14:20] <larsu> seb128: https://code.launchpad.net/~larsu/gtk/properly-fix-settings-hacks/+merge/197379
[14:21] <larsu> that should fix the problem :)
[14:23] <seb128> grrrrrrr
[14:23] <seb128> grrrrr
[14:24] <seb128> I can't even commit changes today, gedit keeps hitting those gdk_window_has_native assert errors
[14:24] <seb128> larsu, ok, merged, thanks!
[14:25] <larsu> seb128: that only happens with overlay-scrollbars, right?
[14:25]  * larsu can't reproduce it
[14:25] <seb128> larsu, I guess, I didn't try disabling those
[14:25] <larsu> if you have steps to reproduce, please let me know
[14:26] <seb128> larsu, EDITOR=gedit bzr commit is doing it half of the time here
[14:26] <seb128> like it took me 4 tries to be able to commit your gtk merge
[14:27] <Sweetshark> .oO(obvious fix: EDITOR=gvim)
[14:27] <seb128> Sweetshark, you don't edit with writer? ;-)
[14:27] <larsu> seb128: doesn't happen for me, but I do see warnings
[14:27] <larsu>  GtkScrolledWindow 0xc67880 is mapped but visible child GtkScrollbar 0xc62ed0 is not mapped
[14:27] <seb128> larsu, right, those are not new, they are there half of the time since saucy
[14:28] <Sweetshark> seb128: only when I have a table of contents in my commit message.
[14:28] <seb128> larsu, the assert is happening when I close gedit btw
[14:28] <seb128> Sweetshark, so... never? ;-)
[14:28] <larsu> seb128: ah, before it saves I assume
[14:28] <larsu> I'm trying for the 20th time or so, works
[14:28] <seb128> :-(
[14:29] <seb128> I'm back on gtk 3.8 from trusty though, I wonder if that makes a difference
[14:29] <seb128> let me try with 3.10.5
[14:29] <Sweetshark> seb128: Indeed I cant remember having the need for that.
[14:30] <larsu> seb128: can you try that and also with GTK_MODULES= to disable o-s
[14:30] <larsu> just to check if that'S the problerm
[14:30] <larsu> *problem
[14:31] <seb128> larsu, sure can try, but knowing it started the day you made the o-s native, it's too much of a coincidence to be something else
[14:31] <larsu> ah okay
[14:31] <larsu> sigh
[14:32] <seb128> larsu, shrug, can't reproduce, let me try with gtk 3.8.7 again to see
[14:32] <seb128> larsu, got it on the second try with 3.8
[14:32] <seb128> didn't get it with 10 tries with 3.10
[14:32] <seb128> so maybe it's fixed in 3.10
[14:34] <seb128> larsu, it seems to have something to do with the warnings you see
[14:34] <seb128> larsu, with 3.8 if I get the warning I get the segfault on closing
[14:34] <seb128> I never got it without having the warning before
[14:34] <seb128> with gtk 3.10 I get the warnings but no segfault
[14:35] <larsu> seb128: okay, I'll investigate the warning.
[14:35] <larsu> not having it is better anyway :)
[14:35] <seb128> thanks
[14:35] <seb128> right, those are annoying me for a while
[14:35] <seb128> they flood my stdout
[14:35] <larsu> also, warnings usually warn about something that might be a problem :)
[14:35] <seb128> right
[14:36] <seb128> larsu, so I'm not able to reproduce with GTK 3.10 either, which is good
[14:44] <seb128> Laney, not sure I found your translations more intuitive :p
[15:00] <Laney> seb128: I didn't know how to do the scaling without it
[15:00] <seb128> Laney, I'm trying to understand what you are doing/learning the canvas rotations and scaling stuff :p
[15:00] <Laney> you don't have to invert the y coordinate now!
[15:03] <sil2100> kenvandine: could you sponsor a package for meee?
[15:03] <sil2100> :)
[15:04] <kenvandine> sil2100, sure
[15:05] <sil2100> kenvandine: https://code.launchpad.net/~ubuntu-unity/zmqpp/ubuntu <- there's a new version here (new ubuntu one)
[15:05] <sil2100> kenvandine: would be cool if you could take a look and sponsor if ok :)
[15:11] <larsu> pitti: I don't have apport installed and want to get a core dump of a program. So I set ulimit -c unlimited, right? That results in a very weird issue: the command never returns after crashing, I can't ^C it, and I can't do anything in the directory I did this in (no ls, no rm)
[15:11] <larsu> pitti: any idea what might be the cause of this? Kernel holding a lock?
[15:11]  * larsu must reboot to make this go away
[15:11] <pitti> larsu: is it actually writing the file?
[15:12] <pitti> it might just be very big
[15:12] <larsu> pitti: I don't see the file after a reboot, so I guess not
[15:12] <larsu> when I set it to 10M I have the same problem...
[15:12] <larsu> argh, now did it in my home dir
[15:13] <larsu> and can't tab-complete anymore without the terminal locking up
[15:13] <pitti> $ cat /proc/sys/kernel/core_pattern
[15:13] <pitti> larsu: ^ what does that say?
[15:14] <larsu> core
[15:14] <pitti> that sounds fine
[15:14] <larsu> I saw a kernel core dump when rebooting just now
[15:15] <pitti> larsu: I got several kernel crashes recently too
[15:15] <pitti> go 3.12
[15:15] <larsu> sigh
[15:15] <pitti> larsu: did anything make it to /var/log/kern.log before you rebooted?
[15:16] <pitti> larsu: did you reboot with sysrq, or just powercycle?
[15:16] <larsu> pitti: I didn't check. Is kern.log.1 the one from the previous boot?
[15:16] <pitti> larsu: no, should be in kern.log; .1 is from yesterday (logrotate)
[15:16] <larsu> pitti: sysrq?
[15:16] <larsu> kern.log seems clean
[15:17] <pitti> larsu: Alt+SysRq (usually on PrintScreen) plus "s"ync, "u"nmount, "b"oot
[15:17] <pitti> the direct keyboard → kernel link if everything in userspace is FUBAR
[15:17] <larsu> pitti: my system was usable, I restarted normally
[15:17] <pitti> that'll sync() and remount everything r/o, so that your disk stays clean
[15:17] <pitti> larsu: ah -- then you *can* check in another terminal what happens to "core"?
[15:18] <pitti> larsu: I thought you said even your terminal froze
[15:18] <larsu> pitti: any terminal in which I try to do anything to that directory freezes
[15:18] <larsu> like, ls
[15:18] <larsu> so I can't have a look whether core gets created
[15:19] <pitti> ouch
[15:19] <larsu> ah, found the kernel's bt further up in kern.log
[15:19] <pitti> larsu: I'd say, high time to reboot with a live CD and run fsck
[15:19] <pitti> if you care about your $HOME
[15:19]  * larsu cares about his $HOME
[15:19] <pitti> or init=/bin/bash and do it from there
[15:19] <pitti> (with unmounted or readonly /home)
[15:20] <pitti> ah, I think we even have this nice rescue mode in grub
[15:20] <larsu> okay thanks. I'll do that
[15:20] <larsu> we do?
[15:20] <pitti> that'll throw you into some curses dialog which has fsck, apt repair, and other goodies
[15:21] <larsu> ah nice
[15:22] <larsu> pitti: http://paste.debian.net/68870/
[15:22] <larsu> gedit was the program I tried to get the core from
[15:22] <pitti> not that I understand much kernel stuff, but if I see BUG and ext4 in a kernel core I get the shivers..
[15:23] <pitti> larsu: fsck o'clock!
[15:23] <kenvandine> sil2100,  sponsored
[15:23] <sil2100> kenvandine: thanks!
[15:30] <mitya57> seb128: Do you have one of my poppler debdiffs locally? Looks like I deleted it from both my pc & LP :(
[15:31] <seb128> mitya57, http://people.canonical.com/~seb128/ubuntu-ubuntu.debdiff
[15:31] <mitya57> seb128: merci!
[15:31] <seb128> mitya57, btw I just commented back on the bug
[15:31] <seb128> mitya57, de rien ;-)
[15:32] <seb128> mitya57, we have the usual "need to rebuild libreoffice, and for that needs to deal with the new toolchain and the issues it creates"
[15:32] <seb128> I would suggest waiting until Sweetshark is ready to upload 4.2 to trusty
[15:32] <seb128> there is nothing that looks like it's important in that poppler 0.24.3 -> 0.24.4
[15:33] <seb128> tsdgeos, not nice of you of changing sonames in a stable update :-(
[15:33] <mitya57> seb128: I'm fine with doing it later, but I'll upload updated diffs anyway
[15:33] <tsdgeos> seb128: you know
[15:33] <tsdgeos> when i write an email warning about it
[15:33] <tsdgeos> i don't expect people to be surprised about it
[15:33] <seb128> tsdgeos, the issue is not being surprised, it's being able to roll out the update
[15:34] <tsdgeos> well, i prefer the arch users getting the bugfix tha noone getting the bugfix
[15:34] <tsdgeos> which is what would happen, no?
[15:34] <seb128> right
[15:34] <larsu> pitti: thanks for your help. fsck says everything's alright
[15:34] <seb128> except that now we get none of the other fixes either
[15:35] <seb128> or we need to revert that api change
[15:36] <tsdgeos> i'm sorry, it's how we manage the project
[15:36] <tsdgeos> we can argue again about it
[15:36] <tsdgeos> but it is how it is
[15:37] <seb128> right, it's just an unfortunate situation
[15:37] <seb128> the Ubuntu archive rules mean that to be able to roll out that update with the new soname we need to rebuild everything with the new version, which includes libreoffice
[15:37] <seb128> which is not an easy thing to rebuild
[15:37] <seb128> oh well
[15:38] <seb128> no point arguing about it, we can delay until the day we are ready to rebuild the rdepends in trusty
[15:39] <pitti> larsu: does that dir with the core file work again?
[15:40] <larsu> pitti: yes, but the core file it not in it...
[15:41] <pitti> larsu: right, it already crashed in open(), not surprising
[15:42]  * larsu nods
[15:42] <larsu> if only this crash also happened in gdb, then I wouldn't have to deal with this problem :)
[15:42] <larsu> I blame seb128!
[15:42] <pitti> err, it doesn't happen in gdb? strange
[15:43] <pitti> larsu: apport doesn't catch it either? (i. e. with a core pipe)
[15:47] <larsu> pitti: "start: unknown job: apport"
[15:47] <larsu> 'apport' is installed
[15:47] <pitti> larsu: you have /etc/init/apport.conf ?
[15:48] <larsu> yes
[15:48] <pitti> larsu: your system sucks!
[15:48] <larsu> haha
[15:48]  * larsu hides
[15:48] <pitti> larsu: err, apport wouldn't catch it if this is some binary from your $HOME (but that's not related to upstart being AWOL, of course)
[15:49] <pitti> larsu: oh wait, did you sudo it?
[15:49] <larsu> pitti: no, do I need to?
[15:49] <larsu> ah, I do
[15:49] <pitti> yes
[15:49] <larsu> "Job is already running"
[15:50] <seb128> larsu, copy over the /usr/bin gedit
[15:50] <larsu> do I need to set core_pattern manually?
[15:50] <larsu> seb128: this is the gedit from my system
[15:50] <seb128> oh
[15:50] <pitti> larsu: what I said, apport ignores stuff from your $HOME, as these aren't packaged
[15:50] <seb128> larsu, what do you have in /var/log/apport.log?
[15:50] <pitti> larsu: ok, then apport ought to catch it; check /var/log/apport.log ?
[15:51] <larsu> pitti: no. core_pattern is set to core... do I need to change that to |apport manually?
[15:51] <larsu> seb128: nothing
[15:51] <pitti> larsu: "sudo stop apport; sudo start apport" should do that
[15:51] <pitti> $ cat /proc/sys/kernel/core_pattern
[15:51] <pitti> |/usr/share/apport/apport %p %s %c
[15:53] <seb128> pitti, btw, https://errors.ubuntu.com/problem/00594d5c83cc8b30ba8dc5fcea3ae1a37392fb19 you are not alone hitting that one
[15:54] <seb128> it's ranked 3rd on the daily trusty report
[15:54] <pitti> oh, good
[15:54] <pitti> seb128: sorry, didn't manage to report it yet (still have it open)
[15:54] <seb128> pitti, no worry
[15:55] <pitti> how would I get from my https://errors.ubuntu.com/oops/53d057e6-5b3f-11e3-91f0-2c768aafd08c to the error page?
[15:55] <pitti> I mean /problem/
[15:55] <seb128> you can't afaik :/
[15:55] <larsu> pitti: thanks. Piping to apport works indeed
[16:00] <seb128> desrt, I read the #gtk+ backlog, seems like that's going to be resolved this week, good ;-)
[16:01] <larsu> meh, this stacktrace doesn't help nme at all. Everything is ??
[16:01] <seb128> larsu, install dbg packages
[16:01] <desrt> seb128: ya... looks like we will semi-revert the change
[16:01] <larsu> seb128: I have them installed
[16:01] <seb128> larsu, what segfault are you getting?
[16:01] <larsu> seb128: the warning we were talking about earlier (I have fatal-warnings)
[16:02] <larsu> I guess today is just one of those days :(
[16:13] <seb128> larsu, you can just "b gtkwidget.c:9488" in gdb (being in the gtk+ source, gtk/) and "r gtkwidget.c")
[16:13] <seb128> larsu, that seems to do the trick here
[16:14] <larsu> seb128: thanks! I just did something similar and have a usable backtrace now. The problem is that o-s calls unrealize() on all scrollbars whenever com.canonical.desktop.interface scrollbar-mode is changed
[16:15] <larsu> and calling unrealize() on a visible widget is not the smartest thing to do...
[16:15] <larsu> is anybody even using that key?
[16:15] <seb128> yes
[16:15] <seb128> that's the recommended way to turn off o-s by user
[16:16] <seb128> we also change it from g-c-c when you select an a11y theme
[16:16] <larsu> ah got it
[16:32] <larsu> seb128: hiding the scrollars before unmapping them fixes the warning. I hope it also fixes you crash! https://code.launchpad.net/~larsu/overlay-scrollbar/hide-scrollbars-before-unmapping/+merge/197415
[16:36] <Laney> oho, found the bad evolution commit
[16:37] <Laney> https://bugzilla.gnome.org/show_bug.cgi?id=699576
[16:37] <ubot2> Gnome bug 699576 in general "Mail reader frame is black (in the mail view)" [Normal,Resolved: fixed]
[16:37] <Laney> anyone on shell here? darkxst?
[16:40] <Laney> nm, I'll just test it myself
[16:41] <seb128> pitti, ok, just got your gabble issue, it happens when you turn off wifi (did that by error while playing with settings)
[16:43] <seb128> Laney, I did some extra minor nitpick on your axis work, sorry about that :p
[16:43] <Laney> hrhr
[16:44] <seb128> Laney, also that seems a lot of efforts for a graph (well, adding the legend, if we start considering the labels/shifting of ticks), not sure if we should delay that
[16:44] <Laney> gosh I can't see that one pixel
[16:44] <Laney> did you zoom a screenshot?
[16:44] <seb128> no, but I can if you want
[16:44] <Laney> yeah the api makes working on it quite difficult
[16:44] <Laney> no it's ok
[16:44] <Laney> just wondering how you saw it :P
[16:45] <seb128> well, they look off on my external monitor
[16:45] <pitti> seb128: it happens every time I try to go online with empathy (i. e. when jabber wants to start); but I guess there are different conditions when it can happen
[16:45] <seb128> pitti, I guess so
[16:45] <Laney> btw I was thinking you'd only do 15 minute increments
[16:45] <Laney> err, 10 minute
[16:46] <Laney> so 9:03 would show the 9:10 tick and there would be a 7 minute gap
[16:46] <Laney> maybe that would look weird
[16:46] <seb128> that would yes
[16:46] <seb128> I would prefer cut 3 minutes then
[16:46] <seb128> and show 9
[16:46] <Laney> mmm
[16:46] <seb128> or I would prefer just keep what you did
[16:46] <seb128> have the 6 hours markers
[16:47] <seb128> and put no text
[16:47] <seb128> and not have to deal with those details :p
[16:47] <Laney> I guess so
[16:47] <Laney> now they mean "now", "1 hour ago", etc
[16:47] <Laney> which is probably ok for now
[16:47] <seb128> right
[16:47] <Laney> ok /me takes a screenshot to zoom in
[16:48] <seb128> we need more design input on the behaviour if we add the labels
[16:48] <Laney> miss that compiz feature
[16:48] <seb128> lol
[16:48] <seb128> it's still there
[16:48]  * Laney draws some fire on the screen
[16:48] <seb128> you need to enable it in ccsm
[16:48] <Laney> that program scares me
[16:48] <seb128> ;-)
[16:49] <Laney> YOU LIE!
[16:49] <seb128> ?
[16:50] <Laney> http://ubuntuone.com/28TITpVmhSchI01kvxnMXs
[16:50] <seb128> are you calling me a liar?
[16:50] <seb128> right, that screenshot confirms what I was saying :p
[16:50] <seb128> maybe we are speaking about different thing
[16:50] <Laney> yeah
[16:51] <seb128> I should perhaps say (0,0) should be painted
[16:51] <Laney> you want that one pixel filled in?
[16:51] <seb128> yes
[16:51] <Laney> I see
[16:51] <seb128> it looks weird like that
[16:51] <seb128> at least to me
[16:51] <seb128> if you disagree, we might want to ask a designer what they think, or do a pool there
[16:51] <seb128> I've no taste for pixel precision stuff, so maybe I'm just the one being weird there ;-)
[16:52]  * Laney wonders how you do that
[16:52] <seb128> paint a point?
[16:53] <Laney> yeah
[16:53] <Laney> I only know how to do lines :(
[16:53] <seb128> ctx.fillRect(x,x,y,y)
[16:53] <seb128> sorry
[16:53] <Laney> ah
[16:53] <seb128> (x,y,1,1)
[16:53] <Laney> I got it
[16:56] <Laney> wtf
[16:56] <Laney> now it randomly draws two sets of axes
[17:01] <Laney> ok there
[17:02] <seb128> Laney, you didn't like the fillRect suggestion? (I don't care much, it's just what internet results suggested doing)
[17:03] <Laney> it uses a different style
[17:03] <Laney> so I just used the one we already had
[17:03] <seb128> oh, right, makes sense
[17:04] <Laney> this api seems really buggy on nouveau
[17:04] <Laney> keep getting glitches
[17:04] <seb128> thanks for the fix, that looks good (though I'm unsure if the lines are not a bit long, the 0,0 look a bit "strong", I'm not going to nitpick on that one anymore though ;-)
[17:04] <Laney> like how it breaks if you rotate on the device
[17:04] <Laney> that doesn't even get fixed if you force a repaint
[17:05] <Laney> length> should be easy to tweak
[17:05] <seb128> :-(
[17:05] <seb128> speaking of refresh, at some point I want to make the graph dynamic
[17:05] <seb128> like refresh/translate if you keep the panel open
[17:05] <seb128> it doesn't do that atm
[17:05] <Laney> yeah
[17:05] <Laney> that would be good
[17:05] <seb128> Laney, do you want to tweak the length or just get that in?
[17:06] <Laney> you try some different values and see what you like :P
[17:06] <Laney> or follow up with it later
[17:06] <seb128> Laney, well, I tested on my desktop, you tested on the device, let's optimize for the device ;-)
[17:16] <sil2100> seb128: hello! Did you have a moment to re-review the unity-voice after our fixes? Since we might have missed the notice
[17:16] <seb128> sil2100, hey, sure
[17:29] <ogra_> seb128, Laney, any idea why locale disagrees about the locale setting on my phone ? http://paste.ubuntu.com/6510308/
[17:29] <Laney> hmm, not having much fun trying to use user switching
[17:30] <seb128> Laney, getting blank screen, xorg sigabrt, etc?
[17:30] <Laney> just blank
[17:30] <ali1234> Laney: bug 1256150
[17:30] <ubot2> Launchpad bug 1256150 in lightdm (Ubuntu) "Xorg guest session fails to start if the user has logged out and logged in again" [High,Confirmed] https://launchpad.net/bugs/1256150
[17:30] <seb128> Laney, likely fixed by https://code.launchpad.net/~a-j-buxton/lightdm/vt-double-unref-fix/+merge/197247
[17:30] <Laney> seems to have lost my main session
[17:30] <seb128> if you want to try it
[17:30] <seb128> right
[17:30] <seb128> you got a vt on top of it
[17:30] <seb128> that's this bug
[17:30] <Laney> could be
[17:30] <Laney> ta
[17:30] <seb128> thanks ali1234 for tracking it and fixing it
[17:31] <seb128> we just need to nag robert_ancell to get the fix merged/uploaded
[17:31] <Laney> ogra_: interesting
[17:32] <seb128> ogra_, is logging done through pam?
[17:32] <ogra_> logging ?
[17:32] <seb128> maybe you have a .profile or something that overwrite those?
[17:32] <ogra_> you mean login ?
[17:32] <seb128> login
[17:32] <seb128> sorry
[17:32] <seb128> yeah :p
[17:32] <ogra_> it is done by lightdm in an autologin setup
[17:32] <seb128> ok
[17:32] <seb128> weird
[17:33] <ogra_> i have the default .profile file in the phablet homedir
[17:33] <seb128> is the issue new?
[17:33] <Laney> for me adb shell locale shows that but locale from the terminal is right
[17:33] <ogra_> seb128, no idea i just tried running locale for the first time ever on a phone i thinnk
[17:34] <seb128> is adb shell going through our stack/pam for auth?
[17:34] <ogra_> seb128, sudo is
[17:34] <ogra_> root@ubuntu-phablet:/# sudo -u phablet -i locale
[17:34] <ogra_> LANG=
[17:34] <ogra_> LANGUAGE=
[17:34] <ogra_> LC_CTYPE="POSIX"
[17:34] <ogra_> ...
[17:35] <ogra_> and sudo -u phablet -i is what all our tools use when they run any cmdline commands via adb
[17:35]  * ogra_ would try the terminal app, but bug 1255999 doesnt allow me to
[17:35] <ubot2> Launchpad bug 1255999 in ubuntu-keyboard (Ubuntu) "[regression] if switched to non english local, the keyboard does not come up when an input field is focused" [High,Confirmed] https://launchpad.net/bugs/1255999
[17:41] <seb128> ogra_, can you strings /proc/`pidof unity8`/environ to see if that happens for the system jobs
[17:41] <ogra_> will check ...
[17:42] <seb128> ok, I need to go
[17:42] <seb128> bbl
[17:45] <ogra_> http://paste.ubuntu.com/6510375/
[17:45] <ogra_> ah, he is gone
[18:15]  * ogra_ hugs Laney for fixing his mail 
[21:19] <ochosi> robert_ancell: ping
[21:19] <robert_ancell> ochosi, hello
[21:20] <ochosi> robert_ancell: we talked about an issue with the guest session in ubuntu and it also affected xubuntu with light-locker obviously
[21:20] <ochosi> robert_ancell: we reported a bug as you suggested, and ali1234 was even able to track down the issue and write a patch for it, but then it was marked "invalid" today without explanation: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1256150
[21:20] <ubot2> Launchpad bug 1256150 in lightdm (Ubuntu) "Xorg guest session fails to start if the user has logged out and logged in again" [High,Confirmed]
[21:20] <ochosi> any clue what that is about?
[21:21] <robert_ancell> the xorg component was marked invalid, as it's a bug in lightdm
[21:21] <ochosi> oh right, i didn't look closely enough... sry :/
[21:21] <ochosi> well anyway, the other thing was i wanted to make you aware of it, so one fail, one win
[21:21] <robert_ancell> np
[21:22] <robert_ancell> yeah, will try and get that fix out today
[21:22] <ochosi> it has been tested also (as the comment suggests)
[21:22] <ochosi> nice
[21:22] <ochosi> thanks a lot!
[21:22] <ochosi> will you backport it for saucy too?
[21:25] <ochosi> robert_ancell: ^
[21:32] <robert_ancell> ochosi, yes