[05:30] <Unit193> "yes, the i386 retracer crashed, I restarted it yesterday"
[10:50] <brainwash> ali1234: any idea what might be broken here? bug 1280641
[11:34] <slickymasterWork> brainwash: I can confirm that your patch for bug 1185396 works
[11:37] <slickymasterWork> brainwash: https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/1185396/comments/16
[12:06] <brainwash> slickymasterWork: thanks for testing, but I think that it could be fixed differently, in a clean way (approved by memory logs)
[12:07] <slickymasterWork> brainwash: tbh I didn't saw the code for your fix. I'm a bit overwhelmed with work 
[12:07] <slickymasterWork> I just add the PPA and tested it :P
[12:07] <brainwash> my other MP for gnome-system-tools got rejected, because I should report the patch upstream
[12:08] <brainwash> bug 586080
[12:09] <slickymasterWork> hmm, well, at least that shows that the package is not completely abandoned upstream
[12:09] <brainwash> it is actually
[12:09] <brainwash> upstream means debian in this case
[12:10] <slickymasterWork> Yeah, I was referring to debian
[12:10] <slickymasterWork> are you going to report this patch upstream?
[12:11] <slickymasterWork> aor are you going to fiddle it a bit more
[12:11] <slickymasterWork> s/aor/or
[12:11] <brainwash> was hoping that one of the ubuntu guys would do it, some of them create package for ubuntu and debian
[12:12] <brainwash> or simply just apply it for ubuntu only, it's dead software anyway
[12:13] <slickymasterWork> well, you're right, about being dead ;)~
[12:13] <knome> well, hoping for others to do things often doesn't help
[12:13] <knome> why not do it yourself?
[12:13] <brainwash> I was hoping that we could have switched to mate-system-tools
[12:14] <knome> don't think switching to otherDE-system-tools is cool
[12:14] <brainwash> I was not aware that I have to do it
[12:14] <knome> brainwash, don't think you "have to", but it doesn't hurt to do that, right? :)
[12:14] <brainwash> I fixed the bug in ubuntu
[12:14] <knome> there was that guy writing a new DE-agnostic user tool
[12:14] <knome> *user management tool
[12:15] <knome> that looks the most promising
[12:15] <brainwash> but mate-system-tools is a simple fork which still gets some love
[12:15] <brainwash> it works with Xfce
[12:15] <knome> i don't doubt that
[12:15] <knome> why wouldn't it? it's for user management
[12:16] <knome> but anyway, using mate-system-tools doesn't sound at all better than using gnome-system-tools
[12:16] <brainwash> one could think, that it builds around the MATE DE
[12:16] <knome> and if there is an alternative for those, why not?
[12:16] <brainwash> like the new gnome3 user management tool does
[12:17] <brainwash> right, so we need something new for 14.10 :)
[12:17] <knome> possibly
[12:17] <slickymasterWork> hey knome, good morning
[12:18] <knome> bbl, phone
[12:18] <slickymasterWork> I was away this weekend and was trying to know if the screenshots serve your purpose? 
[12:23] <knome> yep
[12:23] <knome> haven't been able to do anything with those yet
[12:23] <knome> could do next
[12:24] <knome> and will
[12:27] <knome> slickymasterWork, done, refresh font page and you'll see your shots there
[12:27] <knome> (some)
[12:27] <slickymasterWork> ok, if you need anything else, just ping me
[12:28] <knome> the next time we need to worry about those is some time before trusty release
[12:28] <slickymasterWork> oh, btw, don't forget also the three -docs MP's
[12:28] <knome> i know...
[12:28] <slickymasterWork> yeah, sorry for being such a pain in the neck :P
[12:28] <knome> nah
[12:28] <knome> life is that ;P
[12:28] <knome> and "real" work
[12:29] <knome> keeps me doing xubuntu stuff
[12:29] <slickymasterWork> again, when you're right... you're right
[12:31] <brainwash> the screenshots contain the word "Sex" (date)
[12:31] <brainwash> :-)
[12:32] <brainwash> really sexy screenshots
[12:34] <slickymasterWork> lol, that's the portuguese abbreviation for friday, brainwash  
[12:35] <slickymasterWork> in portuguese Sexta (friday) gets to be Sex (Fri) you dirty mind ;)
[12:36] <brainwash> oh, so it's not a subliminal message :P
[12:37] <slickymasterWork> who's to know, now :)
[13:02] <slickymasterWork> lunch time ->
[15:41] <ali1234> brainwash: i don't understand where to get that version. it isn't in the repositories
[15:47] <brainwash> ali1234: it's Thunar 1.6.3-1ubuntu3
[15:49] <brainwash> https://launchpad.net/ubuntu/+source/thunar
[15:51] <ali1234> yeah that is definitely broken
[15:52] <ali1234> oh, i know what it is, probably
[15:57] <ali1234> i can't actually reproduce it
[15:57] <ali1234> it's like the patch isn't applied at all
[15:58] <brainwash> I can't reproduce it either
[15:58] <ali1234> but the bookmarks aren't saved under gtk-3.0
[16:01] <brainwash> what keeps both bookmark files in sync? nothing, right?
[16:01] <ali1234> nothing
[16:01] <ali1234> ~/.gtk-bookmarks should be read only
[16:01] <ali1234> there is literally no way for the code to ever write to it when correctly patched
[16:01] <ali1234> yet it is writing to it
[16:02] <ali1234> my installed thunar does not even contain the string "bookmarks"
[16:02] <ali1234> which means it hasn't had this patch applied to it
[16:02] <brainwash> o.o
[16:02] <ali1234> Installed: 1.6.3-1ubuntu3
[16:03] <brainwash> so the package has not been properly built?
[16:04] <ali1234> it certainly looks that way
[16:04] <ali1234> does it even work at all for you?
[16:04] <ali1234> for me it behaves 100% like the old version
[16:07] <ali1234> the package will not buidl locally:
[16:07] <ali1234> dpkg-shlibdeps: error: no dependency information found for /usr/local/lib/libxfce4ui-1.so.0 (used by debian/thunar/usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libthunar-tpa.so)
[16:07] <ali1234> dh_shlibdeps: dpkg-shlibdeps -Tdebian/libthunarx-2-0.substvars -dRecommends debian/thunar/usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libthunar-tpa.so -dDepends debian/libthunarx-2-0/usr/lib/x86_64-linux-gnu/libthunarx-2.so.0.0.0 debian/libthunarx-2-0/usr/lib/x86_64-linux-gnu/thunarx-2/thunar-sbr.so debian/libthunarx-2-0/usr/lib/x86_64-linux-gnu/thunarx-2/thunar-apr.so debian/libthunarx-2-0/usr/lib/x86_64-linux-gnu/thunarx-2/thunar-wallpaper-plugi
[16:07] <brainwash> new bookmarks do get saved here
[16:08] <ali1234> yes but where do they get saved?
[16:08] <brainwash> gtk3
[16:08] <brainwash> don't have the gtk2 file
[16:08] <ali1234> try deleting both bookmarks files
[16:10] <brainwash> did that, then I added a new bookmark and it got saved in the gtk3 location
[16:11] <ali1234> ok, try deleting ~/.config/gtk-3.0 directory completely
[16:12] <brainwash> now it stopped working
[16:12] <ali1234> yeah i thought so
[16:12] <brainwash> the folder does not get recreated
[16:12] <ali1234> yes
[16:14] <ali1234> so it just needs to create the directory
[16:14] <ali1234> i will fix this and upload a new patch to bugzilla
[16:14] <ali1234> (which is currently broken)
[16:15] <brainwash> thanks :)
[16:48] <ochosi> ali1234: even if window-resizing could only solved within the compositor, that'd be nice actually
[17:23] <elfy> mp3 player working in thunar after upgrade of mount - so that's usb's working for me in thunar \o/
[18:28] <brainwash> anyone testing light-locker-settings?
[18:32] <brainwash> looks like it does not work 100% properly yet
[18:33] <brainwash> so we need some test results
[18:33] <brainwash> :)
[18:36] <schproodle> brainwash, I did a test. Is there an update?
[18:37] <brainwash> no, should be still the initial release of light-locker-settings
[18:37] <brainwash> it works fine for you?
[18:38] <schproodle> brainwash, odd. one still neesds to purge xscreensaver
[18:39] <brainwash> maybe some meta package still depends on it
[18:39] <schproodle> It passed the test:http://packages.qa.ubuntu.com/qatracker/milestones/306/builds/55995/testcases/1630/results
[18:40] <schproodle> I have since tested the settings and function several times.  All on a vm.
[18:41] <schproodle> brainwash, oops: this one: http://packages.qa.ubuntu.com/qatracker/milestones/306/builds/55995/testcases/1633/results
[18:41] <brainwash> but that's only the test case for light-locker (the actual screen locker)
[18:41] <brainwash> ah
[18:43] <elfy> brainwash - are you wkrekik or texadactyl on Launchpad?
[18:43] <brainwash> no
[18:43] <schproodle> elfy, appears that they are both from the testing
[18:43] <brainwash> <- https://launchpad.net/~thad-fisch
[18:43] <elfy> brainwash> so we need some test results
[18:44] <elfy> off you go then ;)
[18:44] <elfy> that'll be one more when you do it 
[18:44] <brainwash> just installed -settings to give it a go... and noticed some oddities
[18:45] <brainwash> but I'm glad that we already got a test case for -settings :)
[18:49] <elfy> yep
[18:49] <elfy> menulibre is the only one without one now
[18:50] <elfy> and there's only 2 mails to the -dev and -testers left on my list now
[19:01] <schproodle> elfy, I have a screen shot of the two-instances-of-lightdm-gtk-greeter in the taskbar.  Wanna see it?
[19:02] <elfy> I guess so
[19:02] <schproodle> or, I guess I could try ubuntu-bug lightdm-gtk-greeter.
[19:03] <schproodle> How would I show the screenshot to you -- if you have the time or you could see it later.
[19:03] <elfy> report it then - you can add screenshot as attachment
[19:04] <schproodle> ok
[19:04] <elfy> unless there is one - ochosi had it I thought 
[19:05] <schproodle> brainwash, I did the testcase for light-locker-setting again.  Seems fine here on vbox 4.3.8 64bit
[19:05] <elfy> might even have been fixed - just not seen it come through yet - in which case a bug report is pointless
[19:05] <brainwash> schproodle: thanks for testing again
[19:06] <brainwash> a screenshot is nice to have, but only log files will help in this case
[19:06] <elfy> schproodle: you can put the screenshot online for me to look at ;)
[19:07] <elfy> other than seeing what it looks like - I'm not bothered tbh
[19:07] <schproodle> OK, don't know how :(
[19:07] <Unit193> I'll do it.
[19:07] <elfy> schproodle: imagebin I use http://imagebin.org/index.php?page=add
[19:07] <Unit193> picpaste, imagebin, imgur, etc.
[19:08] <brainwash> ..or even launchpad :)
[19:08] <Unit193> (I have it from PPA, no bug report.)
[19:08] <Unit193> brainwash: It finally retraced the bug from Sat. :P
[19:08] <brainwash> what bug?
[19:09] <schproodle> http://imagebin.org/298340
[19:10] <ali1234> brainwash: ok, gtk does g_file_make_directory_with_parents() to make the bookmarks folder.... thunar needs to do it too when saving
[19:10] <elfy> schproodle: never seen it - never even seen one there, let alone 2 
[19:10] <Unit193> brainwash: xorg, crashes on the trusty kernels.
[19:10] <Unit193> schproodle: From repo or ppa?
[19:11] <ali1234> schproodle: what is that dark bar?
[19:11] <brainwash> ali1234: ok, should be easily fixable then
[19:11] <schproodle> maybe I need a fresh Rx for my spectacles eh :)
[19:12] <ali1234> schproodle: also what does ps waxf say?
[19:12] <ali1234> the only way i can imagine this happening is if lightdm-gtk-greeter got zombified... twice
[19:13] <elfy> image size is creeping up then - 945Mb
[19:13] <Unit193> Yeah. :/
[19:15] <schproodle> see wickz
[19:15] <schproodle> ali1234, don't know what the dark bar means eh
[19:16] <wickz> jack@jack-VirtualBox:~$ ps waxf | grep greet
[19:16] <wickz>  3283 pts/0    S+     0:00                  \_ grep --color=auto greet
[19:16] <wickz>  1939 ?        Sl     0:01 /usr/sbin/lightdm-gtk-greeter
[19:16] <wickz>  2775 ?        Sl     0:00 /usr/sbin/lightdm-gtk-greeter
[19:16] <ali1234> i need to see the whole thing
[19:16] <elfy> knome: new slideshow - where to report issues with it?
[19:17] <elfy> schproodle: please use a pastebin
[19:17] <schproodle> ali1234, where do I put that -- gotta a url for pastebin or somesuch
[19:17] <Unit193> schproodle: ps waxf | pastebinit
[19:18] <wickz> http://paste.ubuntu.com/7069422/
[19:19] <schproodle> wickz is on the vm with the issue
[19:19] <schproodle> ali1234, ^^
[19:28] <schproodle> ali1234, anything else I might do.  How about ubuntu-bug.  This happens intermittently here.
[19:28] <ali1234> yes, i don't know what yet though
[19:28] <ali1234> please don't reboot the vm
[19:29] <ali1234> from the pastebin i can see that both the greeters are zombies
[19:29] <schproodle> ali1234, I will keep it up if you want.  Please advise as you please.
[19:29] <ali1234> please pastebin /var/log/lightdm/*
[19:33] <wickz> http://paste.ubuntu.com/7069490/
[19:33] <wickz> http://paste.ubuntu.com/7069491/
[19:34] <wickz> http://paste.ubuntu.com/7069492/
[19:34] <wickz> http://paste.ubuntu.com/7069493/
[19:34] <wickz> http://paste.ubuntu.com/7069494/
[19:34] <wickz> http://paste.ubuntu.com/7069495/
[19:34] <wickz> http://paste.ubuntu.com/7069496/
[19:35] <wickz> http://paste.ubuntu.com/7069497/
[19:35] <wickz> http://paste.ubuntu.com/7069498/
[19:35] <wickz> http://paste.ubuntu.com/7069499/
[19:35] <schproodle> ali1234, ^^ wickz 
[19:36] <brainwash> and "apt-cache policy lightdm-gtk-greeter"?
[19:37] <wickz> http://paste.ubuntu.com/7069515/
[19:37] <schproodle> brainwash, ^^ wickz 
[19:37] <elfy> schproodle: they'll know who wickz is :)
[19:38] <schproodle> okeeleedokeelee, duh
[19:38] <ali1234> this might be related http://paste.ubuntu.com/7069492/
[19:39] <brainwash> strange
[19:39] <ali1234> that would make sense actually
[19:40] <ali1234> those might not be gtk-greeter processes
[19:40] <ali1234> does it run the indicators by forking?
[19:40] <wickz> yeah schproodle is kinda weird
[19:40] <ali1234> i bet it does
[19:40] <ali1234> yeah... so this is my theory
[19:40] <ali1234> the indicator watchers bug causes the indicators to respawn "too fast"
[19:41] <ali1234> so it something turns them into zombies
[19:41] <schproodle> ali1234, might this be vbox vm related?
[19:41] <ali1234> or the indicator is waiting for them to exit
[19:41] <ali1234> schproodle: no
[19:42] <ali1234> the problem here is that the process is turning to zombie instead of exiting clean
[19:42] <schproodle> intermittently
[19:42] <ali1234> yeah, it's a race condition
[19:43] <ali1234> if you look on the pswaxf there are more zombie processes
[19:43] <ali1234> lots of init --user --startup-event indicator-services-start
[19:43] <ali1234> so this is almost certainly related
[19:44] <ali1234> so, revised theory: gtk-greeter runs init to send the startup-event
[19:44] <ali1234> init goes zombie and that causes greeter to go zombie
[19:44] <ali1234> they both get reparented
[19:45] <ali1234> init still has indicator-sound-service as a child
[19:45] <ali1234> i know how to "fix" this
[19:45] <ali1234> it's a bug we've been waiting for unity to fix for months
[19:46] <ali1234> however, there might be secondary bug here
[19:46] <ali1234> ochosi: thoughts?
[19:47] <ali1234> if you run "top" on the vm, does it say you have zombies?
[19:48] <schproodle> ali1234, '0 zombie'
[19:48] <ali1234> hmm
[19:48] <ali1234> no convinced :)
[19:48] <ali1234> those processes may not technically be zombie but they sure act like they are
[19:49] <ali1234> it is probably part of the "spawning too fast" protection to make it go into a "dormant" state similar to zombie but not quite the same
[19:49] <schproodle> ali1234, if one right-clicks the taskbar entry, it says the program or window is not responding etc
[19:49] <ali1234> yes, because it's walking-dead :)
[19:49] <Unit193> I was able to right click > close.
[19:49] <ali1234> how easy can you guys reproduce this?
[19:49] <schproodle> scary and sordid, all that parenting eh
[19:50] <ali1234> try to reproduce after applying the no watchers workaround
[19:50] <ali1234> i bet you can't...
[19:50] <schproodle> intermittent here for about the last week
[19:50] <ali1234> put INDICATOR_ALLOW_NO_WATCHERS=1 in /etc/environment on a line on it's own and then reboot
[19:51] <schproodle> ok...
[19:53] <schproodle> ali1234, skip ubuntu-but, right?
[19:53] <schproodle> ^but^bug
[19:54] <schproodle> ready to reboot...
[19:55] <ali1234> well, you could open a bug, bug we've got all the logs now
[19:55] <schproodle> reboot then?
[19:55] <ali1234> sure
[19:57] <schproodle> up -- no taskbar lightdm* stuff
[19:57] <schproodle> what next?
[19:58] <ali1234> well, wait and see if it happens again
[19:59] <schproodle> that /etc/environment line is on a vm system that I am upgrading from the iso option, so, it should remain there.
[20:00] <ali1234> hmm... probably it will ask if you want to keep the changes
[20:01] <schproodle> Ok, I have no idea what it does.  If it happens again, I will report here.
[20:01] <Unit193> It'll ask for sure, but don't see it owned by any package.
[20:02] <ali1234> ochosi: how are you shutting down the indicators when exiting the greeter?
[20:02] <schproodle> Unit193, It might ask if I was upgrading with apt-get.  What is the difference from the iso upgrade option campared to apt-get upgrade or dist-upgrade.
[20:03] <ali1234> good question actually...
[20:04] <brainwash> ali1234: http://bazaar.launchpad.net/~lightdm-gtk-greeter-team/lightdm-gtk-greeter/trunk/view/head:/src/lightdm-gtk-greeter.c#L2800
[20:04] <ali1234> hmm... ok that seems wrong
[20:04] <ali1234> they are launched by sending an upstart event
[20:05] <ali1234> upstart is going to try to keep them alive until it gets the shutdown signal i assume
[20:05] <brainwash> already mentioned this
[20:05] <ali1234> so then gtk-greeter does waitpid
[20:05] <ali1234> that will never return
[20:05] <ali1234> or it will but by then there will be a new one
[20:05] <brainwash> but... unity-greeter does the same
[20:05] <ali1234> so that's keeping everything around
[20:05] <ali1234> well, maybe unity-greeter has the same bug, who knows?
[20:06] <brainwash> i cannot reproduce it
[20:06] <ali1234> maybe unity-greeter sets the hint to not show on the panel?
[20:06] <ali1234> this is certainly related to the upstart managed indicators though
[20:07] <brainwash> yeah, like you've said: race condition
[20:28] <elfy> Unit193: you got a clue as to where to push a slide for our ubiquity slideshow?
[20:29] <elfy> or of course anyone else that sees ... 
[20:31] <Unit193> elfy: lp:ubiquity-slideshow-ubuntu
[20:33] <elfy> knome: https://code.launchpad.net/~elfy/ubiquity-slideshow-ubuntu/slide1/+merge/210291
[20:33] <elfy> thanks Unit193 
[20:34] <Unit193> Sure.
[20:35] <schproodle> ali1234, looking at the image of the lightdm double entry, I noticed that the icons on the desktop are missing.
[20:35] <ali1234> probably an unrelated bug
[20:46] <knome> elfy, will look at that later
[20:46] <knome> i will try to take some time for tomorrow to go through all the pending merge proposals
[20:48] <elfy> :)
[20:48] <elfy> knome: I don't even know if there are others doing the same thing tbh - I just noticed it a short while ago
[20:54] <knome> elfy, not for that slide, no
[20:54] <knome> elfy, we did land the new slides for b1 for the reason of getting feedback
[20:54] <knome> so thanks ;)
[20:55] <elfy> :)
[21:18] <schproodle> ali1234, reproduced lightdm-gtk-greeter -- this time with the /etc/environment line 
[21:18] <schproodle> ali1234, desktop icons are also missing
[21:18] <ali1234> hmm... ok, thanks
[21:19] <schproodle> what next if anything?
[21:19] <brainwash> ubuntu-bug
[21:20] <brainwash> regarding the missing desktop icons, can you right-click the desktop to trigger the context menu?
[21:20] <schproodle> well, when I clicked on the desktop the icons appeared!
[21:20] <ali1234> that is probably the background of lightdm-gtk-greeter obscuring the desktop
[21:20] <schproodle> I left clicked inadvertently
[21:21] <schproodle> right click doe not work
[21:22] <brainwash> that's not normal
[21:23] <brainwash> does running "xfdesktop --reload" restore the desktop functionality?
[21:23] <schproodle> ubuntu-bug lightdm-gtk-greeter then?
[21:23] <brainwash> yes
[21:23] <schproodle> will do ...reload
[21:24] <schproodle> do the reload before bug?
[21:24] <brainwash> yeah
[21:25] <schproodle> ok, have not done this before -- advice welcome
[21:28] <Unit193> ali1234: I'd say so as well, when I closed the window the desktop came up.
[21:28] <brainwash> so, did the reload change anything?
[21:28] <Unit193> (IIRC)
[21:28] <wickz> still doing bug...
[21:29] <ali1234> wickz: attach all the logs please
[21:30] <wickz> reload did not correct right-click dysfuntion
[21:31] <ali1234> hmm
[21:31] <wickz> ali1234, what logs...appport had completed and browser is open 'report a bug'
[21:31] <ali1234> finish bug report first
[21:31] <wickz> OK
[21:31] <ali1234> hmm i actally have one of these zombies on my machine
[21:32] <wickz> gotta nice concise summary for me?
[21:32] <ali1234> anything you like. i'll edit it when i figure out what is going on
[21:33] <ali1234> "lightdm-gtk-greeter doesn't exit cleanly when logging in"
[21:33] <wickz> ali1234, ok
[21:33] <ali1234> although i don't have any greeter processes
[21:41] <ali1234> wickz: also please link to the bug here
[21:53] <schproodle> ali1234, what about the logs?
[21:59] <schproodle> ali1234, bug #1290575
[21:59] <ali1234> thanks. i'll fill in the rest
[21:59] <schproodle> ali1234, logs or anything else from me, please advise.
[22:00] <ali1234> not sure really
[22:03] <ali1234> you could try to attach gdb to the dead greeter process and then get a backtrace
[22:03] <ali1234> i get it's on waitpid()
[22:03] <ali1234> *bet
[22:06] <wickz> I put the logs ^^ in a comment: pastebin /var/log/lightdm
[22:06] <wickz> I put the logs ^^ in a comment: pastebin /var/log/lightdm/*
[22:07] <wickz> don't know about gdb debugger eh for a backtrace, please advise
[22:07] <ali1234> run pidof lightdm-gtk-greeter
[22:07] <ali1234> then run gdb -p <the first number>
[22:07] <ali1234> then press ctrl-c
[22:08] <ali1234> then type bt
[22:09] <wickz> no stack
[22:09] <ali1234> hmm
[22:09] <ali1234> so it really exited
[22:09] <ali1234> it's not waiting
[22:10] <ali1234> weird
[22:10] <ali1234> i'll need to make a vm and try to reproduce i suppose
[22:11] <wickz> someone has left a comment on the bug report
[22:12] <wickz> It appears that lightdm-gtk-greeter is waiting for init (upstart) to exit. upstart is in turn waiting on the indicator services to exit. From the log:
[22:12] <ali1234> that was me
[22:19] <wickz> ali1234, anything else from me at this time?
[22:19] <ali1234> i don't think so
[23:25] <Unit193> https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1289852 nice.