[04:08] <Unit193> xfce4-smartbookmark-plugin, xfce4-verve-plugin, and xfce4-whiskermenu-plugin uploaded too.
[11:28] <bluesabre> we'll probably need to fix this pre-release or with an SRU, https://bugs.launchpad.net/fedora/+source/catfish/+bug/1501565
[11:29] <bluesabre> If we can test this easily (create a test user, make sure they are not in sudoers), that'd be cool
[12:00] <slickymasterWork> bluesabre, checked and confirmed on RC image
[12:00] <slickymasterWork> do you want to add anything to that report?
[12:00] <slickymasterWork> + me
[12:05] <bluesabre> slickymasterWork: just that it also affects ubuntu
[12:05] <bluesabre> gotta run, bbl
[12:41] <flocculant> slickymasterWork bluesabre - commented in that report
[12:47] <flocculant> sent the users and invite to testing :p
[13:06] <tracker9> flashing green bar to tell you where to type then
[13:09] <flocculant> installing to ssd is so quick that the enter for the next comment from tracker9 became the restart after install :p
[13:10] <flocculant> jjfrv8: I tried to make that affect catfish(ubuntu) but it wouldn't find it :(
[13:32] <slickymasterWork> flocculant, bluesabre, added my to the bug. It's now confirmed
[13:36] <flocculant> ta
[15:18] <flocculant> knome: yep - I'll probably just do new ones - easier than fiddling with the old ones
[15:42] <flocculant> knome: also - if we want to take the contribute/qa page back to something more basic - I've transferred it to wiki and we could have wiki/Xubuntu/Testing/page there 
[16:39] <flocculant> dkessel: if you get time - can you check the iso you have and that failed install - cheers
[16:53] <dkessel> flocculant: currently running another installation with the same medium. checked the iso MD5, ran the image selftest...
[16:57] <dkessel> btw: should there be a battery status icon (from xfpm or something) during the install?
[17:02] <flocculant> not sure tbh - only thing I have with a battery *needs* to be connected to mains ... 
[17:03] <flocculant> !team
[17:04] <flocculant> can anyone confirm an issue with catfish - unlock database - hangs updating 
[17:04] <flocculant> didn't ask password either 
[17:05] <dkessel> flocculant: nope, asks for password
[17:05] <dkessel> and updates
[17:05] <dkessel> not a clean install though
[17:05] <flocculant> ok cool :)
[17:06] <flocculant> just checked with live too 
[17:06] <slickymasterWork> give me sec flocculant 
[17:06] <dkessel> yeah, live works here, too.
[17:07] <dkessel> mhhh i guess i will close that kernel bug if another install goes through without kernel panic
[17:08] <flocculant> dkessel: ack - I installed that to hardware a few hours ago - infinity was a tad perturbed I guess 
[17:09] <slickymasterWork> flocculant: no seeing it either
[17:09] <slickymasterWork> RC image 
[17:09] <slickymasterWork> it did ask for the password and finished the database update
[17:13] <flocculant> k - thanks both :)
[17:13] <flocculant> obviously broken it here :p
[17:20] <slickymasterWork> that's because you're the QA lead :P
[17:21] <flocculant> hah
[17:32] <flocculant> ochosi: mousepad view - I see where that's set y default settings - but where does the 'colour' for the highlight when you search come from? 
[17:33] <flocculant> slightly older people might welcome a change - hard to see what you've Ctrl+F'd as it it 
[17:33] <drc> As one of those...+2 :)
[17:34] <flocculant> blame bluesabre for "Usability bug reports are fair game" ... ;)
[17:34] <flocculant> hi drc :)
[17:34] <drc> Hey flocculant 
[17:35] <drc> Yeah, He appears to have developed pronounced sado-machocistic tendencies :)
[17:35] <flocculant> :D
[17:39] <drc> ochosi: re: mousepad highlight color...just a tad darker, just enough to see it more distinctly.
[17:41] <dkessel> hah! now after installing, i have that exact same catfish freeze, flocculant
[17:43] <dkessel> flocculant: if you run "catfish -v" in a terminal, you will likely see an "UnboundLocalError: local variable 'password' referenced before assignment
[17:43] <dkessel> also, bluesabre ^
[17:49] <slickymasterWork> let me check that dkessel 
[17:52] <slickymasterWork> nopes, dkessel 
[17:52] <slickymasterWork> still working as expected
[17:52] <drc> Doesn't the user have to be non-sudoer?
[17:53] <drc> IIRC from the log.
[17:54] <dkessel> slickymasterWork: well flocculant and me can reproduce it :p i couldn't reproduce it on this old installation here, either, or on the live image. but on the fresh installation, it happened two times now
[17:55] <flocculant> bluesabre: http://pastebin.com/YLwjtn5D
[17:56] <flocculant> first run with -v it asked for password and ran, second run without the -v it hangs unlocking
[17:56] <flocculant> dkessel: well that's odd - with verbose it worked 
[17:56] <slickymasterWork> drc, that one is bug 1501565
[17:56] <slickymasterWork> a different
[17:56] <slickymasterWork> one
[17:57] <dkessel> i understand that it might be timing related from the log
[17:57] <dkessel> well, i have DE locale
[17:58] <dkessel> yeah, but that's a different one
[17:58] <slickymasterWork> what I find odd is the fact that I'm not getting it
[17:59] <flocculant> yea
[18:00] <slickymasterWork> do you want any special info on my box setup, flocculant?
[18:00] <slickymasterWork> it's a clean RC image though
[18:20] <flocculant> slickymaster: no - unless we ask 
[18:40] <slickymaster> oki doke
[18:41] <flocculant> by we *we* :p
[18:41] <flocculant> I mean 
[18:42] <slickymaster> ... mean...
[18:42] <slickymaster> ?!
[18:42] <flocculant> by we I mean *we* :p
[18:43]  * slickymaster is lost re who the hell we might be :P
[18:43] <flocculant> well we doesn't include me :p
[18:43] <slickymaster> heh
[18:44] <flocculant> but bluesabre most likely or someone more codelike in the team 
[18:44]  * slickymaster is at their service
[18:45] <flocculant> :)
[19:11] <Unit193> Ahh, got my coffee.  Nice warm beverage, though does taste a tad off.
[19:13] <flocculant> try milk instead of youghurt
[19:14] <Unit193> Nooo, black.
[19:17] <flocculant> slickymaster: so in a vm installed from RC then updated - catfish crunches, running with -v in a vm - no different at all
[19:18] <flocculant> so that's odd 
[19:19] <slickymaster> yeas
[19:19] <slickymaster> I won't touch the installation I have in case bluesabre will want any info/data out of it
[19:20] <flocculant> well it fails here too
[19:27] <flocculant> sigh - this is why I'm right to bring package testing back 
[19:28] <slickymaster> well dinner time for me
[19:29] <flocculant> k 
[19:29] <flocculant> gonna do a clean hardware install 
[19:30] <Unit193> Open Catfish → Gear Icon → Update index  ?
[19:30] <flocculant> Unit193: failing for you? 
[19:31] <Unit193> Works fine™
[19:31] <flocculant> and all updated 
[19:31] <Unit193> Well, not technically, didn't run it today yet but yesterday was.
[19:31] <Unit193> Installed: 1.3.3-0ubuntu1
[19:32] <Unit193> This is a system upgrade, amd64.
[19:32] <flocculant> yea - just wonder if this is caused by other recent updates
[19:33] <Unit193> Oh hah, nevermind.  It is broken, yes.
[19:33] <flocculant> ok cool
[19:33] <flocculant> in a manner of speaking 
[19:33] <Unit193> unit193    2688  0.0  0.1  12464  2684 pts/10   S+   15:29   0:00          |   |   \_ bash /usr/bin/catfish
[19:34] <Unit193> unit193    2689  0.7  2.7 864992 53148 pts/10   Sl+  15:29   0:02          |   |       \_ python3 /usr/share/catfish/bin/catfish.py
[19:34] <Unit193> root      2718  0.0  0.1  58796  3636 pts/14   Ss+  15:29   0:00          |   |           \_ /usr/bin/sudo updatedb
[19:34] <flocculant> Unit193: but running catfish -v works?
[19:36] <Unit193> Still  UnboundLocalError: local variable 'password' referenced before assignment
[19:37] <flocculant> aah, now that's failing here
[19:38] <flocculant> which is now weirder 
[19:38] <flocculant> how does something that was working 10 minutes ago - not work now
[19:39] <dkessel> well that's typical for a timing related bug :)
[19:40] <flocculant> dkessel: awesome timing - waits till Unit193 starts talking and suddenly fails :p
[19:40] <dkessel> he must be pushing the button right over there
[19:40] <flocculant> heh
[19:41] <flocculant> dkessel: did that install work btw?
[19:41] <knome> flocculant, re: website, i think it's better to have the new stuff there until we have a sensible and sustainable place for the developer documentation...
[19:41] <knome> flocculant, and now as you have poked docbook a little - let me remind you that one option is to create another set of documentation in docbook for contributors
[19:41] <flocculant> okey doke - just thought I would mention that
[19:41] <knome> flocculant, with all kinds of silly pdf output formats
[19:42] <dkessel> flocculant: oh yeah it did. invalidated that bug. i guess the sd card broke somehow. i can't write anything anymore to it now. so maybe the sd card was the cause
[19:42] <flocculant> knome: ok - and put it where? 
[19:42] <flocculant> dkessel: ok - thanks :)
[19:42] <knome> flocculant, can be on the website, on a subdomain, can be shipped with the system -
[19:42] <knome> flocculant, no limits there, whatever we feel is the best place for it
[19:43] <flocculant> knome: so what we've got in docbook? 
[19:43] <knome> flocculant, our documentation
[19:43] <knome> flocculant, which you have just recently poked...
[19:43] <flocculant> sorry - lack of punctuation didn't help then at all :p
[19:43] <knome> ahah
[19:44] <flocculant> I meant - what we've got on website - but in docbook :)
[19:44] <knome> flocculant, well, yes and no - the website should still probably have the very basics
[19:44] <knome> flocculant, but the docbook stuff could be a full guide to silly things
[19:44] <flocculant> right 
[19:45] <knome> flocculant, and one good thing about it would be that we could write an appendix about using bzr and launchpad
[19:45] <knome> flocculant, and then simply cross-reference to it whenever we need to
[19:45] <flocculant> ack
[19:45] <flocculant> happy to start looking at that 
[19:45] <knome> flocculant, not that we can't do that with the website or wiki, but you know how messy it gets
[19:45] <flocculant> yea
[19:45] <knome> flocculant, so - that's just one option - and the argument that "docbook is hard BOOHOO" stays :P
[19:46] <flocculant> ha ha 
[19:46] <knome> (it isn't, but it's of course more than editing a wiki)
[19:46] <flocculant> well 
[19:46] <flocculant> these things are generally pita to start - person coming along after has it easyish
[19:47] <knome> we have the process ready in docs
[19:47] <flocculant> do we? 
[19:47] <knome> yeah, of course :D
[19:47] <flocculant> never seen it 
[19:47] <knome> we *are* exporting to html and pdf from docbook
[19:48] <knome> i mean the technical process :P
[19:48] <knome> so there's not too much to do when starting
[19:48] <knome> except a lot of writing...
[19:48] <flocculant> oic - thought you meant Processes :D
[19:48] <knome> nnnoope :D
[19:48] <knome> should try to be less ambiguous
[19:49] <flocculant> join the club ... 
[19:49] <flocculant> well I can start writing the QA stuff for sure
[19:49] <knome> mh
[19:50] <flocculant> if doing that makes sense for later - then *shrug* 
[19:51] <knome> well, good documentation *always* makes sense
[19:51] <knome> maybe no reason to convert it to docbook markup yet
[19:51] <flocculant> not quite what I meant :)
[19:51] <knome> lol
[19:51]  * knome reads ambiguously too
[19:51] <flocculant> ha ha 
[19:52] <flocculant> I'll do this anyway, practice
[19:52] <knome> yep, i won't mind
[20:02] <Unit193> flocculant: Yeah this doesn't make sense at all.
[20:03] <flocculant> well I stand no chance at all if you say that :p
[20:04] <Unit193> passwordless_sudo is returning 1, which in theory should make it try to attempt a password dialog box, but alas it doesn't.
[20:12] <Unit193> Logic here doesn't seem to be quite right...
[20:12] <Unit193> Anywho, not my problem, right? :D
[20:14] <knome> totally your problem
[20:14] <knome> at least you seem to be bothered by it much more than i am...
[20:14] <knome> :P
[20:15] <flocculant> :d
[20:15] <flocculant> I'll report this now that it's confirmed
[20:15] <flocculant> just to make bluesabre's evening 
[20:16] <Unit193> knome: I was surprised to see catfish even installed. :P
[20:16] <Unit193> apport (2.19.1-0ubuntu3) wily; urgency=medium
[20:16] <Unit193> * Disable Launchpad crash upload for final Ubuntu 15.10.
[20:16] <Unit193> Hmm.
[20:17] <Unit193> flocculant: But, did you run  catfish -v  soon after using `sudo`?
[20:17] <flocculant> Unit193: mmm
[20:17] <Unit193> The exit status of `sudo -n true` is always returning 1, but return p.exitstatus == 1 isn't right. :D
[20:18] <flocculant> possible
[20:19] <flocculant> given where we are - wonder if we'll get this in
[20:19] <flocculant> there is at least a workround - either use sudo somewhere or sudo updatedb 
[20:21] <flocculant> oh - perhaps as drc said this is the same bug 
[20:21] <knome> flocculant, this time is totally designed for getting bug fixes like this in :)
[20:22] <flocculant> Unit193: are you saying it crashes if sudo used recently or it works if sudo used recently? 
[20:22] <flocculant> knome: if it gets fixed in the next day
[20:23] <flocculant> I'd rather release with it than spend hours smoketesting isos on my own on Thursday again 
[20:24] <flocculant> currently both catfish and -v are wanting password
[20:24] <flocculant> Unit193: nvm - answered myself :)
[20:25] <flocculant> brb
[20:26] <flocculant> back
[20:28] <knome> yyep
[20:29] <flocculant> confusing myself now 
[20:29] <knome> :D
[20:30] <flocculant> so it seems that if catfish is the first thing to want sudo it works
[20:30] <flocculant> but if you've used it prior to catfish it fails
[20:31] <flocculant> Unit193: does that sum up what you've seen? 
[20:37] <flocculant> bug 1507765
[20:38] <flocculant> Unit193: if you've data to add to the bug description from what you found above - that'd be good :)
[20:47] <Unit193> "Exit status of 'true' was '1'"  do you see a problem here? :P
[20:47] <flocculant> nope
[20:48] <Unit193> 'true' returning '1', means the program that always exits without any errors exited "with an error"
[20:48] <flocculant> so add it to the bug then 
[20:54] <flocculant> night all 
[20:58] <Unit193> Anywho, yeah I'm done playing around in the souce there.
[20:58] <knome> souce? sauce?
[21:05] <Unit193> knome: Why aren't you off pinging the right people already!? :P
[23:57] <bluesabre> hey all
[23:57] <knome> hey sean
[23:58]  * bluesabre needs to check the sudo/true/catfish output again it seems
[23:59] <Unit193> Very.