[00:29] knome, flocculant: This is what I've done locally with regards to the doc syntax errors Unit193 referred to, further formatting errors, the few typos I mentioned yesterday, as well as some wordings that I think could be improved - please review, before I do anything with it: http://paste.openstack.org/show/l8oDqhn3ZEl9yO5YKrGO/ [00:35] krytarik, lgtm [01:21] bluesabre: Granted, could FFe (or ask if needed) with notifyd. [01:22] has somebody taken care to reply to renan almeida, who contacted team through LP on PT-BR translation? [07:41] krytarik: typo > windowi [07:42] Ah nice! Didn't notice that. :P [07:44] otherwise I'm fine :) [07:44] re your pm ... [07:45] Alright, guess I'll push it right away then. [07:45] :) [07:46] only 'really' looked at what you said in pm - not sure how I noticed windowi :p [07:46] lol [07:46] as you've seen I have a love/hate relationship with punctuation :D [07:47] Yes yes! :P [07:47] sometimes I love to hate it and then don't bother [08:54] -SwissBot:#xubuntu-devel- ::xubuntu-docs:: [zesty] r629 Syntax, formatting, typo, and wording fixes. (by Krytarik Raido) [12:55] -SwissBot:#xubuntu-devel- ::xfce4-announce:: ANNOUNCE: xfce4-mount-plugin 1.1.1 released @ http://xfce.10915.n7.nabble.com/ANNOUNCE-xfce4-mount-plugin-1-1-1-released-tp48911.html (by Fabian Nowak) [19:22] xrandr [19:24] hey so gtk3 is completely broken under virtualbox now [19:26] not used vbox for ~3 cycles or so [19:27] if you install virtualbox-guest-x11 then gtk3 programs immediately exit at startup with no error [19:27] before they even open a window [19:27] ali1234: which one - repo or vbox( or both I guess) [19:27] note that virtualbox-guest-utils no longer installs -x11 [19:27] everything from 17.04 repos [19:28] never used to install that - used vbox version and their guest stuff [19:29] ali1234: is -x11 needed? [19:29] without it, the xfce4 display settings dialog segfaults at startup [19:30] * flocculant installs it [19:30] is there an lp bug? tried ubuntu at all? [19:31] there is an LP bug which i submitted [19:31] it was marked as a duplicate of a private bug, so you can't see it, and i can't make it public [19:31] vbox won't even start [19:31] oh probably need some services to start [19:32] bug 1665048 [19:32] bug 1665048 in xfce4-settings "xfce4-display-settings crashed with SIGSEGV in g_closure_invoke()" [High,Confirmed] https://launchpad.net/bugs/1665048 [19:32] oh yeah [19:32] i unlinked it from the duplicate [19:38] yea saw that one [19:39] ali1234: from the live session display settings is fine, and when you say gtk3 programs - do you mean any? [19:39] seems like pretty much any program at all [19:40] i'm doing a backtrace for dislay settings manually [19:40] since apport wont do it [19:41] well tried calc, archive, menulibre - all gtk3 afaik - all work [19:41] did you reboot? [19:41] installing now - see if there's a difference [19:41] are you in the live session? [19:41] yea [19:41] because live session works fine [19:41] ok - see ^^ :) [19:42] you have to install it, then fully update all packages, then install virtualbox-guest-x11, then reboot [19:42] you might also need to enable two monitors in the machine config [19:42] I'll see ig I can confirm - I'll also see if it all goes belly up in ubuntu [19:42] ack [19:46] rebooting with 2 monitors [19:47] or trying to reboot [19:48] the reboot dialog is one of the few things that doesn't get broken [19:48] the control panel stuff still works too [19:48] as does xterm [19:49] won't boot [19:49] nice :/ [19:49] tries to lightdm - vbox window itself resizes itself 4 or 5 times - then it just sits there [19:50] well i never saw that one [19:50] although - i set up my VM to auto login [19:50] so maybe it never even tries to show lightdm [19:51] press right-ctrl + f1 to get to a console [19:51] tried restarting lightdm [19:52] try removing virtualbox-guest-x11 and rebooting [19:52] if that was going to be next :) [19:53] yup - booted [19:53] nice [19:54] up arrow to move it to 2 displays, I stopped it when it had reached 38 [19:57] ok - so that's knackered ... trying to replicate that with Ubuntu now [19:58] ali1234: ok - so without the -x11 - got a boot, without it will let me set 2 displays but only see's one when booted (I assume expected given -x11 not installed) [19:59] it works fine if i install from the VBOXADDITIONS CD image [19:59] not sure about display settings though [20:00] I got some error trying to install that [20:00] yeah you will unless you purge the repo packages [20:00] -x11 pulls in -utils [20:00] not the other way around [20:00] aah ok [20:02] the display settings thing - there's reports of the same crash without virtualbox even involved [20:03] I'll dig out old monitor tomorrow and try on hardware [20:03] it seems quite hard to reproduce [20:05] oh yeah ubuntu removed droid fonts :( [20:05] yes, because droid isn't "supported" [20:06] evening knome [20:06] hello [20:08] what is the default font of gnome? [20:08] ali1234: with ubuntu - sometimes see the ubuntu splash screen when vbox window does it's bizarre thing [20:13] don't know about gnome, but if you haven't been following, "noto" is the "successor" for droid [20:13] ali1234, ^ [20:13] i know noto is the successor [20:13] and nice to see your nick around here again :) [20:13] gnome uses cantarell [20:14] right... why do i link that to apple? :P [20:14] trouble is that noto looks really awful on gtk because it is aligned differently [20:14] it takes getting used to [20:14] cantarell is aligned properly but it is really really thin like a MS font [20:14] i didn't want to use noto at first but now i'm fine with it [20:14] i had the exact same issue... [20:15] by "differently" i mean it's visibly misaligned [20:15] could a DPI change fix that? [20:16] and yes i guess it can be a bit misaligned at places too [20:16] all my systems are overridden to 96 DPI already [20:16] noto actually looks better in the "new" adwaita [20:16] the one that cuts the top and bottom off icons [20:16] right [20:22] ali1234: reinstalling xubuntu - tried the vbox version and that wouldn't install, some dep on libpng version [20:23] anyway - just want to be sure here - install -guest-utils in guest or host? [20:23] in guest [20:23] dont install anything in the host [20:23] except virtualbox [20:23] ;) [20:23] knome: long time since I vbox'd :) [20:23] it seems to be caused by version mismatch anyway [20:23] i have't noticed any problems yet [20:24] after installing the utils supplied by the host virtualbox [20:26] that might be why it was having a paddy then - had other stuff installed on host [20:31] ali1234: can't confirm that bug - tried a few times [20:33] installing -x11 and I get this odd window resizing issue [20:35] er... what the heck happened to font rendering in libvte?? [20:36] its like it is using a completely different font for bold text [20:37] oh right... that's because it is... [20:39] (yes, xfce terminal does the same thing) [20:43] i suppose this is why there is a "allow bold text" option [20:45] oh i see. it is hinting [20:49] greybird-accessibility decorations are nice... [20:50] its basically orion :) [20:53] ali1234: can't get it to crash with a second monitor on nvidia either [20:53] what? [20:53] which bug are you actually testing now? [20:53] the xfce-display-settings bug doesn't need dual monitors [20:53] well not the vbox thing - but you mentioned people seeing issue without vbox [20:54] i've seen it happen in virtualbox with just one monitor [20:54] ok [20:54] there are reports of it happening outside virtualbox with two monitors [20:54] yes - I read that - not seeing it [20:57] evening all [20:57] anyway - reported the issue I did see - and likely won't see anything added to that till someone marks it aas let's ignore it [20:58] ali1234: might be worth seeing if slickymaster can replicate your issue, pretty sure he uses vbox all the time [20:59] hi bluesabre [20:59] to be honest it was probably caused by the bad virtualbox guest utils as well [20:59] would be nice if it didn't crash on bad input though [21:00] it's not like xrandr was completely wrong or unavailable [21:00] i'll make yet another vm and try to repro it again [21:01] im sure i once managed to make it crash with no guest utils at all [21:01] :) [21:02] ali1234, there was an update to fontconfig last year that made everything worse, particularly vte [21:03] worse sounds negative [21:03] "different" [21:04] nothing wrong with worse, unless you're a snowflake :p [21:05] it does look a bit different [21:05] but all the problems i mentioned above i was able to recreate in 16.04 [21:05] flocculant, the pervasion of that word in the few months >.< [21:05] by changing the settings [21:05] bluesabre: yea I knome [21:05] sigh [21:05] I know ... [21:06] we all knome from time to time [21:06] ha ha [21:06] i think a few defaults have changed [21:06] plus its hard to tell when i can't use my regular font any more :( [21:07] bluesabre: assuming that we've still got broken lock this week - what do you think we should do on Thursday - b1 release day [21:08] :( [21:09] let's pull in robert this week and see whats up [21:11] flocculant, have we had any updates regarding that recently? [21:11] bluesabre: not since the one that you and ochosi were relaxed about [21:11] not so easy for me to catch him - timezones [21:13] hmm okay this is weird. i have a font installed called just "sans" [21:13] that's what i was using all along, because droid sans isn't even installed. when i changed fonts, droid sans disappeared from the list and i could not reselect it [21:22] http://askubuntu.com/questions/885122/what-is-the-font-in-ubuntu-which-is-just-called-sans [21:26] isn't that dejavu sans? [21:26] yes, sort of [21:26] https://ubuntuforums.org/showthread.php?t=1675235 [21:26] basically, "Sans" is a fallback which for me (and probably most people) ends up as dejavu sans [21:26] yep [21:27] dejavu sans is pretty extensive, so i don't think it needs many glyphs from other fonts [21:27] that also explains why i thought i was using droid, but really i was using dejavu [21:28] and also why noto looks completely different [21:28] because it really is [21:29] the droid/noto comparison is considerable too [21:30] dejavu is *much* wider than droid/noto [21:30] yep [21:30] for me that's the most noticable difference [21:31] there's also height difference with noto/droid [21:31] not sure how they compare to dejavu sans [21:31] yep, and with ubuntu as well [21:31] yep [21:31] youd think a 10 pt font would always be the same size [21:31] at least in one dimension [21:31] though you could kind of expect that noto/droid were closer... [21:31] fonts are weird === Justanick1 is now known as Justanick [21:51] okay i reproduced the display crash [21:55] got it nailed down this time [23:16] https://www.youtube.com/watch?v=Wg5WRaaHEXQ