=== Zren_ is now known as Zren [07:32] flocculant: Do you use any Qt5 applications in Zesty? [07:33] Unit193: not that I'm aware of - if you're seeing something odd I can install something to see here :) [07:35] flocculant: Looks like the old "no style" theme, QT_STYLE_OVERRIDE=gtk isn't cutting it for me anymore. In theory qt5-style-plugins should help, but that makes it unreadable for me. [07:46] right = well not got any (or if I have) they're not behaving oddly [12:01] flocculant: bug 1660159 is also affecting ISO installs.. doesn't discover existing installs .. [12:01] bug 1660159 in os-prober (Ubuntu Zesty) "os-prober fails to see other installed systems" [Critical,Confirmed] https://launchpad.net/bugs/1660159 [12:02] akxwi-dave: yea - that's why I said about keeping qa status as fail for the time being [12:02] that bug will affect any system that has zesty running grub, other os installed, other os not mounted when os-prober runs [12:06] ochosi Unit193 bluesabre - some more testing with thunar - removed the built from git and patches, installed from Unit193's ppa [12:06] done what I did yesterday 4 times - no crashing [12:07] also noticed that thunar is more responsive with the ppa package - yesterday while it was copying or moving opening folders was quite slow - significant enough for me to notice [12:07] flocculant, sounds promising :) [12:07] that said it is definitely better than the previous version [12:07] also [12:08] the test ffrom the thunar bug - 1.txt etc - I had that running for 3 hours or so while away - that didn't crash either [12:08] bluesabre: yup [12:09] bluesabre: also did you see my question the other day re sru for the xfce/tv dying bug - possibility of? [12:10] bug 1308105 [12:10] bug 1308105 in Mythbuntu "Xfce resets TV mode to NULL when power cycled" [Medium,Confirmed] https://launchpad.net/bugs/1308105 [12:13] flocculant, I did, and that may indeed be SRU-worthy, haven't seen any significant regressions from that version [12:14] ok thanks :) [12:14] I also assume we'll be sru'ing thunar [12:15] ugh, i should run tests on the thunar PPA [12:16] knome: that would be nice ;) [12:21] indeed [12:22] now where was the ppa again... [12:23] there. [12:23] wait, what, did the PPA page in launchpad change recently? [12:24] oh nope [12:25] aaand dist-upgrading [12:47] well... i could still crash thunar [12:48] or maybe that was still the old instance running [12:48] can't reproduce easily after new launch - yay [12:49] and now i can't reproduce the other bug at all [12:49] this feels/looks good to me [12:49] and yes, this is definitely SRU material [14:29] I'll just run up a vm that should be big enough to check disk size requirement [14:31] knome: ^^ [14:31] yup [14:31] ta [14:33] akxwi-dave: thanks for commenting :) [14:34] :-) [14:50] knome: ok so this isn't quite as easy as it should be [14:51] installer currently not seeing existing install hence can't see the minimum - we can either wait to confirm 6.1 or see what yak says [14:51] we have the time to wait if you are willing to do it :) [14:52] well - that means wiating till the bug isn't a bug :p [14:52] sure [14:52] though obviously yak gives a decent idea what it is [14:52] which might be something to do with this os-prober business or not *shrug* [14:52] and this isn't "do it once, then need to run all over the place and handle bureucracy to change again", this is "we can update it later on need" [14:52] knome: yea - I can run a yak up nowish [15:04] got waylaid making sure the zesty thing is real :p [15:05] :P [15:08] knome: installing 16.10 alongside 17.04 allows me to make zesty 5.3 but only allows me to make 16.10 7 when resizing [15:09] so I would say just change the 6.1 to 7 for now - we can as you say revisit [15:09] right... [15:09] sigh, relogin [15:10] there [15:10] knome: maybe currently? [15:10] no, proposed :P [15:10] current is "old" [15:10] ho ho ho [15:10] proposed is "to be current" [15:10] oh [15:10] nah [15:11] i think that's implied [15:11] well [15:11] you currently need 512MB ram too [15:11] lets not imply something then :p [15:11] you might need 2gb if you run firefox :P [15:11] and you currently need to support PAE [15:11] might? [15:11] ha [15:11] you migh need to support something else [15:11] you get where i'm going [15:11] so it's implied that you *currently* need that space :P [15:12] we'll update as we go [15:12] if somebody installs, say, 14.04, and the free space requirement is 6GB there, well... too bad [15:12] :P [15:12] i mean it's not like somebody goes to the hardware store and buys a HDD that barely fits the operating system anyway [15:13] of course not - anyway - 7Gb for now :p [15:13] :P [15:13] * flocculant goes back to installing vm's [15:14] hf [15:24] right - all done :) [15:32] ochosi: I forgot about this issue - can't remember if you said what to report upstream against now ... bug 1658772 [15:32] bug 1658772 in thunar (Ubuntu) "xubuntu, thunar, desktop background" [Undecided,Confirmed] https://launchpad.net/bugs/1658772 [15:32] got all tied up with notify and taskman and stuff [15:47] knome: \o/ [15:47] zest resizing shows 7.2 so updated pad to 7.5 [15:53] anyone seen the changes to libreoffice which are posited ? notebookbar layout [15:55] flocculant: zesty from Jan 26 uses an os prober that works fine.. [15:57] http://imgur.com/a/45JEV [15:57] akxwi-dave: ack - it all went a bit pete tong around there [15:59] yea - 26th is when 1.73ubuntu1 landed - so we would likely still have had previous version when iso built [15:59] well did as the update landed 7 hours later :p [16:04] bbl [16:05] i have the 386 iso and teh 64 from 25th [16:05] 386 from 25th [16:06] 26th sorry [16:06] for the 386 [16:15] akxwi-dave: 25th should work [16:16] our iso's should start to not work on the 27th [16:16] that would be the first build with os-prober not working [16:17] and s/25th/26th [16:17] if you check out os-prober's changelog you can see date and time [16:18] http://changelogs.ubuntu.com/changelogs/pool/main/o/os-prober/os-prober_1.73ubuntu3/changelog [16:29] akxwi-dave: might be worth dropping a line to xub-dev re os-pober - hopefully we have more testers than we think we do :p [20:11] flocculant: what's the latest status ofyour thunar testing? [20:24] ochosi: https://irclogs.ubuntu.com/2017/02/02/%23xubuntu-devel.html#t12:06 [20:25] also comments from knoem re thunar [20:26] since then I've done a bit more heavy shifting about of media files [20:26] I've had no crashes from thunar today using unit's ppa [20:27] pretty sure that is the same as the git version so not sure why crashes yesterday but not today [20:27] on the whole this is a whole lot better than it was last week :) [21:12] Unit193: so what's really in your PPA? :) [21:12] ha ha [21:12] I think it has added oomph [21:13] A virus. [21:13] ochosi: It's the packaged version, plus the two upstream git commits (that we've been shipping), plus now these two patches. [21:14] flocculant: what about this one? https://bugzilla.xfce.org/show_bug.cgi?id=12264#c173 [21:14] bugzilla.xfce.org bug 12264 in core "Crash when renaming single file in folder" [Major,New] [21:14] also Unit193 ^ [21:14] (he updated the patch again for you) [21:15] Unit193: or did you already include this version of the patch? [21:16] * flocculant realises he'd set that bug report to not annoy him ... [21:16] ochosi: Nope. [21:17] ochosi: if ppa didn't include that patch I guess I can redo the thing I did which crashed it [21:17] k, please do so [21:17] or maybe Unit193 can update the PPA [21:17] i'd really love to push those patches to master... [21:17] which patch is that replacing though? [21:18] the one from bugzilla [21:18] (in your instructions) [21:19] this one: https://bugzilla.xfce.org/attachment.cgi?id=6976 [21:20] it just adds a single line as far as i can see [21:20] uhm, a little more than that [21:20] diff tricked me [21:20] ochosi: except change 6976 to 6978? [21:21] Or just wait a couple minutes for mine to build... [21:21] awesome, thanks Unit193 [21:21] Also, since it seems to be done correctly, I could actually put it in xubuntu-staging... [21:21] Unit193: I'll wait a few minutes then :) [21:23] * flocculant wanders away to find the kettle [21:29] maybe knome can also re-test [21:29] genii: btw - the os-prober thing is only an issue if you've more than one install on a machine - it fails to see them [21:29] re-test for what specifically? [21:29] seems to have been a busy couple of weeks in here :) [21:30] knome: I guess that the *new* patch doesn't regress somehow [21:30] like new new? [21:31] i tested one today, is there a newer one around? [21:31] yup [21:31] yea [21:31] oh, ok [21:31] do we get it in xubuntu-staging ppa? [21:31] one after I reported yesterday's crashing [21:31] well ideally it also fixes flocculant's crash [21:31] '1.6.10-2ubuntu3~16.10.0 ' [21:31] nothing fixes flocculant crashing, but ok [21:31] ;) [21:31] knome: And yeah, just pushed it there now. [21:31] great [21:31] that I couldn't replicate today [21:31] do we need a test *today*? [21:32] i mean i'll have some slack time tomorrow for sure [21:32] and could do somewhat more extensive testing [21:32] I can run what I've done lately to test when I see the updates [21:33] i mean i can probably get a quick one in today [21:34] well apparently no upgrade of thunar for me [21:35] oh great [21:35] now I've got broken packages [21:35] heh. [21:36] PPA built them a bit ago, but still hasn't published.. [21:37] Nearly 10 minutes. [21:37] oh oops, i'm a bit behind updates on the laptop... [21:38] https://launchpad.net/~xubuntu-dev/+archive/ubuntu/xubuntu-staging/+packages wait for the green checkmark. [21:39] flocculant: Should be good now. [21:41] Depends: thunar-data (= 1.6.10-2ubuntu2) but 1.6.10-2ubuntu3~17.04 [21:44] not sure what's going on with ppa's atm - think I'll be purging and re-adding tomorrow [21:44] building thunar locally for now [21:45] and that's bizarre - don't get the gitversion in thunar about [21:55] redid it [21:56] Unit193: still got issues with upgrading after adding staging ppa - update says there's something to upgrade, but upgrade doesn't :) [21:59] ochosi: ok - currently moving these iso's back and forth and at the same time it's doing the 1.txt to 1.txt.txt thing [21:59] :) [22:07] ochosi: I crashed it [22:07] it had moved them 3 times back and forth - 4th time it crashed [22:08] it alsop lost track (unsurprisingly) of whether 1.txt was 1.txt.txt or not [22:10] so it's large files being moved back and forth that crashes it currently [22:10] can you try whether that also crashes nautilus? :> [22:10] largeish I guess [22:10] what's the frequency of the moving btw? [22:10] how do you mean? [22:11] how quickly do you move those isos around? [22:11] i presume it's a terminal loop [22:11] for the test? [22:11] yeah [22:11] no - manually in thunar with menus [22:12] the txt to txt.txt was obviously - had sleep at 0.25 [22:13] so this is where I am [22:13] with yesterdays building it - I crashed it [22:13] with yesterdays Unit193 ppa version - it didn't crash [22:13] with todays building it - it crashed [22:14] and I had time to do more moving about with the ppa version [22:15] subjectively I would say that any of the 2 are better than before [22:16] ok, good to know [22:16] but still a little odd [22:16] yea [22:16] how the previous patch didn't crash and now it did [22:16] a little too erratic [22:16] no [22:17] building it from git - with either set of patches - crashed [22:17] installing from ppa (with the patches) didn't [22:17] unless that's your meaning :) [22:17] but i thought with the latest patch it crashed from the PPA as well [22:18] I can't install from there - dependency issues [22:18] oh :/ [22:18] wonder why [22:18] *shrug* [22:18] it's just the thunar package itself [22:19] And I didn't change anything else. [22:19] Depends: thunar-data (= 1.6.10-2ubuntu2) but 1.6.10-2ubuntu3~17.04 [22:19] Unit193's fauly. [22:19] fault too [22:19] anyway, please test the package again tomorrow or whenever you can to see whether thtat fixes the iso moving [22:19] and then comment in the upstream bugreport [22:19] the ppa package? [22:20] I pulled it from the x-stag one. [22:20] we are talking about xubuntu-dev/xubuntu-staging here I assume [22:21] Unit193: ^^ [22:21] Ayup. [22:21] ok - just thought best to double check on that :) [22:22] yeah, please test again with the ppa package whenever you can [22:22] mmk [22:23] thanks a bunch! [22:23] I'm going to crash now though :) [22:23] night all [22:23] nighty flocculant [22:23] ochosi: whatever I manage to do tomorrow - I'll comment on upstream bug [22:24] meant to ping r_a about lock tonight too - that'll have to wait :) [22:25] okeydokey, night flocculant! [22:45] ochosi: So to sum up: The package has: 029012f4c39d9d3d9ae617491a69f76f54a4192f, 77cf6ec3a3969589a4e9a8beea6a122b7dbcc2a0, 9c6dbb1dae7074e7713f43438f471d75c823a0db, f9e054872c7ddc065cd4008bb9e8ce1d364aeeed but does not have cb3a2343128d6eacf6338d485b7d671f291071e6, febb41736615d76d73bf8156290296e3de49349b, 9578e0dec5cee473222cb813b43de31067c604e2, 79fdf25f4200015c1808f7bbdfa3b3985381eb40. [22:54] o.o [22:54] * Unit193 dots both eyes. [22:54] ouch [22:56] http://piratepad.be/p/thunar-bugs [23:19] Status update given to Corsac. [23:58] Unit193, can you remind me what we're pending on again with core/base? [23:59] I don't even know at this point. cdimage/the ubuntu live-config fork/something else? [23:59] me neither... [23:59] There's the simple one, the python one, and the bash one. [23:59] i could look at the logs