[16:32] <dkessel> so thunar still randomly crashes on file renames.... meh
[16:32] <dkessel> i thought that might have been fixed in the meantime
[17:24] <bluesabre> dkessel: yeah, its better than it was, but still often enough to be a headache
[17:25] <dkessel> bluesabre: would it not be possible to install some kind of error handler to help pin down the cause of this?
[17:26] <bluesabre> dkessel: potentially one could run thunar with valgrind to try to find it, but since it doesn't happen everytime, could be a pain to figure it out
[17:27] <dkessel> bluesabre: oh, i can reproduce it fairly often
[17:27] <dkessel> it is just that i haven't been renaming folders often lately, which is why it hasn't happened during the last weeks
[17:29] <bluesabre> gotcha
[17:30] <bluesabre> install valgrind and run thunar with it.  Get it to crash and save the output to a file with the bug report, might help
[17:31] <dkessel> ok, will try
[17:45] <Unit193> bluesabre: Maybe more gdb?
[17:45] <Unit193> Or install -dbg and let apport do it?
[17:45] <bluesabre> Unit193: potentially
[17:45] <bluesabre> gdb is a pain for all though
[17:46] <bluesabre> :D
[17:49] <dkessel> Unit193: i got the -dbg package, but apport doesn't detect the end of the child process as crash
[17:49] <dkessel> mhh i am getting this while copying/files sometimes: http://paste.ubuntu.com/13071572/
[17:51] <dkessel> also, something seems to be with thumbnailing: http://paste.ubuntu.com/13071670/
[17:52] <dkessel> i don't know if any of these could sometimes cause the child process to crash/end
[17:55] <dkessel> oh, now i got it
[18:01] <dkessel> i got a trace in the moment of the crash. created bug 1512120
[18:02] <knome> dkessel, fwiw, duplicating the app name in the bug title isn't unwelcome
[18:03] <dkessel> knome: oh, ok in fact i believed it might be. np, fixing that
[18:03] <knome> it helps when it's there when linking to it externally (package/app name isn't always visible)
[18:03] <dkessel> ok i see.
[18:03] <knome> (including the status tracker... :P)
[18:04] <knome> np, continue
[18:04] <knome> :)
[18:18] <bluesabre> dkessel: cool, that looks like a good indicator of where the issue might be starting :)
[18:18] <bluesabre> suppose I'll start learning thunar's codebase now
[18:18] <bluesabre> :)
[18:19]  * bluesabre sets up xenial dev env and goes shopping
[18:19] <bluesabre> bbabl
[18:20] <dkessel> bluesabre: note that i my stack traces are from wily though. but it guess there should be no difference yet
[18:21] <bluesabre> dkessel: np, its been crashing since at least vivid
[18:22] <dkessel> alright. happy shopping
[20:46] <flocculant> oh boo - hating bzr
[20:46] <Unit193> That's usual, anything specific?
[20:47] <flocculant> merged the xubuntu-docs stuff cos of the changes there
[20:47] <flocculant> now got a bzr conflict with desktop-guide/libs/xubuntu.ent
[20:47] <knome> :Ð
[20:48] <knome> flocculant, sorry, i needed to poke it..
[20:48] <flocculant> yep 
[20:48] <flocculant> knome: so how can I deal with this then? 
[20:48] <knome> Unit193, krytarik: there's some work for you in the docs branch, the translation process isn't completely supporting two docbook sets yet
[20:49] <knome> xubuntu.ent should not exist any more...
[20:49] <knome> enduser doc related stuff should be in xubuntu-docs.ent
[20:49] <knome> in the same directory
[20:50] <knome> basically bzr expects you to get rid of all the .THIS .THAT .OTHER and whatever files
[20:51] <flocculant> still conflicts apparently
[20:51] <flocculant> can't be bothered to fight this 
[20:51] <krytarik> knome: Is this the proper time for me to refer to '- contributor-docs/Makefile: "ln -s ../libs-common ../build/contributor-docs/libs-common" seems unnecessary', first? :P
[20:52] <Unit193> http://xkcd.org/1597/ mostly applies here.
[20:52] <flocculant> funnily enough ... 
[20:54] <knome> krytarik, how is it?
[20:54] <knome> flocculant, if it's just about getting your MP rebased with the new stuff, don't bother
[20:54] <knome> flocculant, we'll handle that
[20:54] <flocculant> oh my lord
[20:54] <flocculant> still got problems :|
[20:55] <knome> flocculant, did you run "bzr resolve" ?
[20:55] <flocculant> why would I do that? 
[20:55] <knome> flocculant, that checks if you have resolved the stuff in question
[20:55] <flocculant> you might know all these commands - but I don't ;)
[20:55] <knome> heh, sure
[20:55] <knome> that's why i ask
[20:55] <flocculant> knome: I grabbed anew - then copied my local stuff in to the new copy 
[20:56] <knome> flocculant, mhm
[20:56] <flocculant> bzr resolve
[20:56] <flocculant> All conflicts resolved.
[20:56] <flocculant> bzr: ERROR: These branches have diverged.
[20:56] <flocculant> how can that be - if I *just* grabbed it 
[20:57] <knome> flocculant, if you grabbed the new stuff, and then applied yours, they can be diverged because you have files that the new branch doesn't
[20:58] <flocculant> knome: I copied my changes into the new branch - not added anything that's not there, unless you removed doc pages
[20:59] <flocculant> knome: any reason not to delete branch lp:~flocculant/xubuntu-... 
[20:59] <flocculant> and push it again? 
[21:00] <flocculant> drc> [14:37:50] All I really care about is "what do they want me to put in the "hardware profile" of the test cases"  If Dell 1420n is enough, I'm good. 
[21:00] <flocculant> I'm happy with whatever you want to put there - I'm not bothered about all that gist stuff at all 
[21:04] <knome> flocculant, you can just push it again :)
[21:04] <flocculant> no I can't 
[21:04] <flocculant> I get errors
[21:05] <Unit193> --overwrite
[21:06] <flocculant> Unit193: thanks - hopefully that got it :D
[21:06] <Unit193> That or it broke everything. :D
[21:06] <knome> flocculant, so was this about the changes you did?
[21:06] <knome> flocculant, or something new?
[21:07] <flocculant> knome: I appear to have pushed something now ;)
[21:08] <knome> ;)
[21:08] <flocculant> all manner of things happening in https://code.launchpad.net/~flocculant/xubuntu-docs/xubuntu-docs/+merge/274703
[21:08] <flocculant> none of which I actually did :D
[21:10] <flocculant> Diff against target: 	182719 lines (+33977/-27848) (has conflicts) 
[21:10] <Unit193> :D
[21:11] <flocculant> I give up - losing interest with this rapidly :p
[21:11] <knome> rrright...
[21:11] <knome> i'll figure it out
[21:11] <knome> just don't touch it again
[21:11] <knome> :P
[21:12] <flocculant> knome: all that I have done is bzr branch lp:xubuntu-docs, changed the dozen or so files I changed before, commited it, tried to push it - and it threw a fit then --overwrite appeared to push it ok
[21:12] <knome> yeah
[21:12] <flocculant> no wonder people start to get involved and then give up 
[21:13] <knome> the reason why you see the huge diff is that you have now merged main into your branch
[21:13] <knome> (main did have a lot of changes)
[21:13] <flocculant> right
[21:13] <knome> so you are seeing both your changes, and mine
[21:14] <flocculant> should have just deleted my branch and started again
[21:14] <knome> which i guess i could have committed slightly more cleanly
[21:14] <knome> (but only slightly)
[21:14] <knome> i'll take a spot on the dining table and figure it out
[21:16] <flocculant> mmm 
[21:16] <flocculant> so if you did stuff with the .ent file(s) and I had added something to one here I guess that's all gone now
[21:17] <knome> i'll make sure it gets all in.
[21:17] <knome> don't worry
[21:17] <flocculant> anyway - I'm off, I only turned the machine to check a few things, saw slickymaster's comments fixed those and commented where I didn't 
[21:18] <flocculant> then it all went wrong ... 
[21:18] <knome> np
[21:18] <flocculant> cya tomorrow :)
[21:18] <knome> hf
[21:18] <flocculant> sleep I want - 3 nights of 3 or 4 am's 
[21:18] <flocculant> :D
[21:18] <knome> huh
[21:18] <knome> good nighty then ;)
[21:18] <SwissBot> feed xubuntu-docs had 13 updates, showing the latest 3
[21:30] <knome> flocculant, ok done; see https://code.launchpad.net/~flocculant/xubuntu-docs/xubuntu-docs/+merge/276351 for the "actual" diff against the xenial branch
[21:45] <knome> wut?
[21:49] <knome> what was my quit message?
[21:50] <knome> because i think i just chrashed irssi...
[21:55] <krytarik> knome: "* knome has quit (Remote host closed the connection)"
[21:55]  * knome facepalms
[21:55] <knome> totally inaccurate
[21:56] <knome> i typed a /command and BOOM
[21:57] <krytarik> knome: Also, please refer to  http://paste.openstack.org/show/YAxHwIMt52LGwcrFVmoP/  reg. the changes to 'desktop-guide/libs/xubuntu.ent' previously made by flocculant.
[21:58] <knome> hmm
[21:58] <knome> i wonder why launchpad totally forgot about that
[21:58] <knome> i tried to find the previous commit by him, but no
[21:59] <knome> maybe it was the --overwrite...
[21:59] <krytarik> Yep.
[21:59] <krytarik> Like he said, that killed it.
[21:59] <knome> mhm
[21:59] <knome> stupid.
[22:00] <knome> ok, pushed
[22:00] <knome> well, pushing
[22:00] <knome> done
[22:19] <knome> krytarik, so... as i said before
[22:19] <knome> there is some work with the docs scripts
[22:19] <knome> i can help with that too
[22:19] <knome> one thing we should probably reconsider is the structure on how the docs are built
[22:19] <knome> now the startpage is on the root directory, language directories for docs directly below it
[22:20] <knome> if we get new contributor docs, wouldn't it make sense to put each of them under their own subdir
[22:21] <knome> that would help with some of the linking stuff too
[22:27] <krytarik> knome: Yeah, I guess that'd be a workable solution.
[22:31] <krytarik> knome: Btw, these are the other ones :P -
[22:31] <krytarik> - Release notes on website and wiki: "LibreOffice Calc and Writer and [→are] now included."
[22:31] <krytarik> - http://xubuntu.org/news/building-xubuntu-documentation-package-locally/:
[22:31] <krytarik>   'fonts-droid' added in Wily too, but installed in Xubuntu by default
[22:31] <krytarik> - http://xubuntu.org/help/: "Wily Werewolf 15.10" is split in two links
[22:33] <knome> heh
[22:33] <knome> this is why you shouldn't let others update the website ;)
[22:34] <krytarik> :D
[22:36] <knome> say
[22:37] <knome> should the scripts always require a template
[22:37] <knome> or should we fall back to desktop-guide?
[22:38] <krytarik> For clarity, I guess I'd prefer specifying it.
[22:38] <knome> yep