[01:31] <Unit193> cyphermox: Actually, here you go: https://sigma.unit193.net/source/plymouth_0.9.0-0ubuntu9_i386.build
[02:12] <Unit193> (All said and done, biggest problem was entering the password twice on an encrypted install.  Everything else worked.)
[04:53] <Logan> Unit193: what did I do
[04:54] <Logan> oh
[04:57] <Unit193> I use that, noticed that problem but requests in vivid is too old anyway.
[06:01] <Logan> Unit193: don't think so?
[06:02] <Logan> it just requires >= 2.2.0
[06:10] <Unit193> Dangit, confusing the two.  That's the dep missing, another one in vivid wasn't new enough.  python-natsort it was.
[06:11] <Unit193> natsort>=3.5.2; Candidate: 3.5.1-1
[06:11] <Unit193> Anywho, moot.
[07:04] <ochosi> good day everyone
[07:06]  * ochosi pokes bluesabre back
[07:06] <ochosi> bluesabre: hey dude, hi, what's up? :)
[07:10] <ochosi> Unit193: since you've been wily for a bit, how's it going so far?
[07:10] <ochosi> any roadblocks or glitches you've seen that we shoudl address?
[07:11] <Unit193> In case you haven't seen it, I seem to be trying to break it with crazy setups.  I'd say all the ones I've hit are != Xubuntu and can be considered fringe events.
[07:15] <ochosi> ok, good
[07:16] <ochosi> well if you notice anything odd, always be sure to mention it here
[07:16] <ochosi> i'm still only doing the occasional test in vbox, so far everything seems good
[07:16] <Unit193> Depends on what you consider odd. ;P
[07:33] <Unit193> Speaking of which, new cores coming soon™
[07:49] <ochosi> Unit193: new cores?
[08:10] <Noskcaj> ochosi, Only issue with wily i've noticed is that parole is near useless
[08:11] <ochosi> oh right, that one
[08:11] <ochosi> yeah, we definitely need to check out what's going on there...
[08:14] <ochosi> it actually seems totally useless, not "near"
[08:14] <ochosi> wonder what that is related to though, since no changes happened in parole
[08:14] <ochosi> guess clutter or gstreamer
[08:15] <ochosi> ok, it's clutter.
[08:15] <ochosi> Noskcaj: easy workaround for you to test: set the property /video/videosink in parole to "xv" instead of clutter
[08:16] <ochosi> then it should launch immediately and smoothly
[08:16] <Unit193> Ah, I don't use parole.
[08:18] <ochosi> bluesabre: so we have a clutter issue in parole in wily (see above)
[08:21] <Unit193> What happens?
[08:21] <Unit193> Crash?  Like https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789198?
[08:21] <ubottu> Debian bug 789198 in src:clutter-1.0 "src:clutter-1.0: Please update to 1.23 to fix #781121 / upstream bug 747489" [Important,Open]
[08:27] <Noskcaj> ochosi, how do i do that?
[08:27] <ochosi> Unit193: it just freezes up, i would have to compile with debug symbols to know what exactly is going on
[08:27] <ochosi> Noskcaj: open xfce4-settings-editor
[08:28] <Noskcaj> fixed
[08:29] <Noskcaj> i'll install clutter-1.0 and see if that works too
[08:30] <Unit193> ochosi: https://wiki.ubuntu.com/DebuggingProgramCrash#Non-built-in_debug_symbol_packages_.28.2A-dbgsym.29
[08:31] <Unit193> https://launchpad.net/ubuntu/+source/parole/0.8.0-2ubuntu1/+build/7464841/+files/parole-dbgsym_0.8.0-2ubuntu1_amd64.ddeb
[08:35] <ochosi> meh, bidirectional clipboard isn't working in the vbox and that link is definitely too long to type
[08:39] <Unit193> ochosi: http://u193.ga/y/prldbg
[08:39] <ochosi> Unit193: hm, i don't get any additional debug output
[08:40] <ochosi> just the usual gtk3 deprecation warnings
[08:40] <ochosi> which are harmless
[08:40] <Unit193> Oooh, I thought you meant debug symbols. :P
[08:40] <ochosi> yeah, sorry for mis-phrasing that ;)
[08:42] <Unit193> Those should be runtime. :P
[09:01] <ochosi> Unit193: anyway, that bugreport you linked to might well be related
[09:16] <ochosi> Unit193: especially since totem also freezes and then crashes at startup in wily....
[09:21] <Unit193> Try updating the package? :>
[09:33] <Unit193> Except, looks like that's talking about upgrading to the version it is at now, soo.
[09:39] <ochosi> Unit193: you mean upgrading clutter?
[10:30] <Noskcaj> Upgrading clutter-1.0 doesn't seem to do anything
[10:39] <ochosi> Noskcaj: always check whether totem starts and runs ok to be sure
[11:00] <bluesabre> hey all
[11:01] <bluesabre> ochosi: do you want me to package up an artwork update soon?
[11:03] <bluesabre> nice, since clutter seems to be the issue, I could swap us back to xv for the time being
[11:03] <bluesabre> the only issue I have with wily is overlay scrollbars
[11:04] <bluesabre> for some reason, adding this to my bashrc does not work
[11:04] <ochosi> overlay scrollbars because you don't like them?
[11:04] <bluesabre> export GTK_OVERLAY_SCROLLING=0
[11:04] <Unit193> The apport screen looks glitchy as heck with that.
[11:04] <ochosi> and yeah, let's switch back to xv to prevent tons of bugreports
[11:04] <bluesabre> ochosi: I don't like them and they cover up content that I try to use
[11:04] <ochosi> we just have to remember to switch back to clutter ;)
[11:05] <ochosi> bluesabre: don't they fade out again quickly enough? and if not, is that tweakable?
[11:05] <bluesabre> they appear every time you move
[11:05] <Unit193> export QT_STYLE_OVERRIDE=gtk
[11:05] <Unit193> export GTK_OVERLAY_SCROLLING=0
[11:05] <ochosi> right, i guess that makes sense though
[11:05] <bluesabre> so if there is a button under them, good luck
[11:05] <ochosi> hmm
[11:05] <ochosi> i see
[11:05] <ochosi> well i guess then they should only appear when you hover them
[11:05] <ochosi> or the area where they're supposed to appear
[11:05] <ochosi> but i guess we have no influence on that
[11:06] <ochosi> in terms of artwork, yes please! i pushed some more improvements to greybird today and may push one or two more soonish
[11:06] <bluesabre> ok
[11:06] <ochosi> if you want me to do a point release, that'd be fine by me
[11:06] <ochosi> same goes for LO
[11:07] <ochosi> and elementary-xfce
[11:07] <bluesabre> I might upload friday then if you're expecting anything before then
[11:07] <ochosi> not too much tbh
[11:07] <ochosi> maybe more minor improvements
[11:07] <bluesabre> ok
[11:07] <ochosi> but personally  i think it'd be good to have some updated artwork so we can check what's still missing in qiwily more reliably
[11:08] <bluesabre> I also wonder if LO integration will happen before LO 5.0
[11:14] <ochosi> i think we should upload our LO stuff and then we'll see what happens with LO 5.0
[11:15] <ochosi> last i heard it was still planned for wily, but i haven't talked to Sweet5hark in a while
[11:16] <ochosi> the LO icons will likely receive more updates during the wily cycle anyway, so it's ok to do another one after 5.0 lands
[11:17] <bluesabre> alrighty
[11:19] <ochosi> so greybird, elementary-xfce and the LO icons
[11:19] <bluesabre> ok
[11:20] <bluesabre> I might dump lo-icons into xubuntu-artwork for now
[11:20] <bluesabre> maybe
[11:20] <bluesabre> I'll work on that and other things tonight
[11:20] <bluesabre> also
[11:20] <bluesabre> "ooh, you fixed geary in greybird"
[11:21] <ochosi> yeah, i thought i'd do one for your motivation ;)
[11:21] <ochosi> had to add some custom theming though
[11:21] <ochosi> but that was expected
[11:21] <ochosi> and yeah, let's put the LO icons in -artwork for now
[11:23] <ochosi> there's that member of the LO community that wants the icons upstream, so i won't do anything there toin order to not duplicate the effort
[11:24] <bluesabre> yeah, makes sense
[11:24] <bluesabre> and makes it easier
[11:24] <ochosi> for us, anyway ;)
[11:25] <Unit193> xubuntu-artwork or src:xubuntu-artwork?
[11:25] <bluesabre> it will be stuck in -proposed for a few days, I'll have the style create its own package like xubuntu-icon-theme
[11:26] <bluesabre> lp:xubuntu-artwork will create libreoffice-style-elementary or xubuntu-libreoffice-theme or something
[11:27] <ochosi> i'd prefer the prior
[11:27] <bluesabre> same, just not sure if there'd be any complaints
[11:27] <ochosi> the latter obfuscates the project name too much imo
[11:27] <ochosi> well we can always point to that discussion on github if anybody complains that we're not upstreaming
[11:27] <bluesabre> mhm
[11:27] <Unit193> I'd highly prefer the former, considering that follows the package naming of the other themes.
[11:28] <bluesabre> ofc
[11:28] <bluesabre> I'd prefer the former too
[11:28] <bluesabre> :D
[11:28] <bluesabre> but yeah, I'll get the ball rolling on that tonight
[11:28] <Unit193> But then again I want burritos too.
[11:30] <bluesabre> oh yeah
[11:31] <bluesabre> https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1473952
[11:31] <ubottu> Launchpad bug 1473952 in xubuntu-meta (Ubuntu) "Choose preferred pinentry method" [Undecided,New]
[11:31] <bluesabre> I'm guessing gtk2 for us for now, right?
[11:33] <ochosi> humm
[11:33] <ochosi> dunno, what's the visual diff?
[11:33] <Unit193> bluesabre: Have to keep an eye on Debian 791441, but yes gtk2.
[11:33] <ubottu> Debian bug 791441 in gnupg-agent "Add more flexible mechanism to set the default pinentry per desktop environment" [Important,Open] http://bugs.debian.org/791441
[11:34] <bluesabre> dunno, don't have anything using pinentry
[11:34] <ochosi> i just wonder whether there are any downsides to using gnome3, even if just for the sake of not having to change the seed
[11:34] <ochosi> me neither
[11:35] <bluesabre> but if the gtk2 version is offered, it would likely be easier on us in the long run
[11:37] <ochosi> i guess
[11:37] <ochosi> hard to say when you've seen neither :)
[11:37] <bluesabre> :D
[12:04] <ochosi> bluesabre: hmm, any idea what the easiest way would be to test evince with headerbar?
[12:04] <ochosi> (in xubuntu, that is)
[12:10] <bluesabre> ochosi: virtualbox, install fedora
[12:10] <bluesabre> :D
[12:10] <bluesabre> no idea
[12:10] <ochosi> hah, meh
[12:10] <bluesabre> gotta run, bbl
[12:10] <ochosi> okeydokey
[12:10] <ochosi> just wanted to fix some small visual nuisances there
[12:11] <ochosi> but i guess that'll have to wait
[12:11] <ochosi> hf bluesabre 
[12:12] <Unit193> XDG_CURRENT_DESKTOP=GNOME evince
[12:12] <Unit193> ochosi: 
[12:12] <Unit193> o
[12:13] <ochosi> oh right
[12:13] <ochosi> that was easy
[12:13] <ochosi> thanks Uni
[12:13] <Unit193> Sure.
[12:13] <Unit193> Also, http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/wily/evince/wily/view/head:/debian/patches/traditional_menu_bar.patch#L91
[12:15] <ochosi> bluesabre: btw, i fixed my sort issue in the open file dialog with this gsetting: "gsettings set org.gtk.Settings.FileChooser sort-directories-first true"
[12:16] <ochosi> bluesabre: so in case anyone else encounters it, we might want to throw that into x-d-s
[12:17] <Unit193> Just like turning off the GTK animations! :P
[13:30] <cyphermox> Unit193: I see, lots of stuff... though also lots we really really don't care about and don't want to ship
=== davmor2_ is now known as davmor2
[19:24] <Noskcaj> pinentry-gnome3 just means it's the gtk3 version, there's no gnome specific stuff.
[19:24] <Noskcaj> -gtk2 is apparently missing some features, which is why debian only depends on -gnome3
[19:39] <Noskcaj> bluesabre, If you haven't already seen it, mugshot and menulibre are ftbfs with python3.5
[19:44] <ochosi> Noskcaj: any details as to what features? (and i still don't have a clue because i have no device to use this with)
[19:45] <Noskcaj> quoting debian's gnome team "No, we want pinentry-gnome3 for GNOME, since only that provides a proper UI/replacement for the builtin prompter."
[19:46] <ochosi> hm, still no clue, sorr
[19:46] <ochosi> y
[19:47] <Unit193> Because it is GTK3, thus the only one good enough for GNOME? :P
[19:48] <Noskcaj> Unit193, I think that's most of it
[19:48] <Noskcaj> But if we can use -gnome3 i'd prefer that, it seems to work fine locally
[19:48] <Unit193> cyphermox: Right, I agree.  I used https://bitbucket.org/snippets/unit193/agkpy
[19:49] <Unit193> I personally like gtk2 better, so if there's anything that it's an option on.. :P
[21:31] <ochosi> bluesabre: pushed more artwork updates over the course of today, might push one or two more tomorrow, if time permits. so friday is definitely a good date for up-ing that.
[21:40] <bluesabre> ochosi: nice
[21:40] <bluesabre> Noskcaj: good to know
[21:40] <bluesabre> yay more bugs
[21:40] <bluesabre> :D
[21:47] <ochosi> and evening bluesabre 
[21:49] <ochosi> what're you up to?
[21:49] <bluesabre> ochosi: not much, just got home
[21:49] <bluesabre> eating pizza rolls
[21:49] <ochosi> yummy
[21:49] <ochosi> bon appetit
[21:50] <bluesabre> :D
[21:50] <bluesabre> thanks for the geary fix
[21:50] <bluesabre> very nice at work
[21:50] <bluesabre> :D
[21:50] <bluesabre> aaaaand done
[21:51] <ochosi> heh
[21:54] <ochosi> yeah, i went through the issues list for greybird today and tried to cut it in half
[21:54] <bluesabre> nice work
[21:54] <ochosi> i'm sort of hesitant as to whether i should try plain gtk3 without any ubuntu mods
[21:54] <ochosi> i guess that would expose more issues
[21:55] <ochosi> but then again, i really don't want to have to rebase on adwaita
[21:55] <ochosi> so i might do a greybird 1.6 next
[21:55] <ochosi> since it does in fact provide basic gtk3.16 support
[21:55] <bluesabre> yeah
[21:55] <bluesabre> sounds reasonable
[22:00] <ochosi> anyway, if you get around to testing wily more and if you see more glitches there, please let me know
[22:00] <ochosi> would prefer to get in a few more fixes before 1.6, but i also want to release soon
[22:17] <bluesabre> np
[22:17] <bluesabre> I actually run wily as my main now
[22:23] <bluesabre> and that is to say that I don't really have any issues
[22:24] <bluesabre> other than my minor gripes about gtk 3.16 usability