[04:57] <hyperair> hyperair@ipwn:~$ ps -C notify-osd -o rsz=,command=
[04:57] <hyperair> 194248 /usr/lib/notify-osd/notify-osd
[04:57] <hyperair> win!
[04:57] <hyperair> 194M of memory for a notification daemon that shows pretty notifications.
[04:58] <hyperair> someone please tell me what about this is not right?
[04:58]  * hyperair kills notify-osd
[04:59] <lamalex> hyperair: 16m here
[04:59] <hyperair> well yeah. that's how it is when it starts
[05:00] <hyperair> leave it a while and you get something like this
[05:01] <lamalex> oh 194. I saw 19.
[05:01] <lamalex> I was like "what's the big deal"
[07:06] <mac_v> notify-osd uses 3m here ;)
[08:24] <mac_v> DanRabbit: ping
[09:23] <MacSlow> DBO, trying your branch now
[09:24] <MacSlow> DBO, the conditional cairo_destroy()s are embarrassing
[09:25] <MacSlow> DBO, no idea under by which drugs I was influenced there
[13:35]  * MacSlow -> lunch
[14:29] <qense> I can't find any documentation for python-indicate or information on the API changes between 0.1 and 0.2. Do they exist at all?
[14:31] <tedg> qense: There isn't a migration guide or anything.
[14:31] <qense> ok
[14:31] <tedg> qense: The big thing that isn't is that there isn't an IndicateIndicatorMessage
[14:31] <tedg> object
[14:31] <qense> ok
[14:32] <tedg> There are some new properties that are recognized, and they're all listed in the spec: https://wiki.ubuntu.com/MessagingMenu
[14:33] <qense> That page will be a tremendous help. Thanks!
[14:40] <DBO> MacSlow, got me emails?
[14:41] <MacSlow> DBO, yes
[14:41] <DBO> did you check out me findings about the stack
[14:41] <MacSlow> did some tests
[14:42] <MacSlow> there's no difference between your branch and trunk yet
[14:43] <MacSlow> did two type of test
[14:43] <DBO> no the changes I made are correctness
[14:43] <DBO> you are supposed to free those windwos, and the conditional freeing was odd but not freeing a nil i snot required
[14:43] <MacSlow> 100 notifications with a pause of 12 secs
[14:44] <DBO> yeah?
[14:45] <MacSlow> and 50 notifications without pause... wait 600 secs to let queue empty and another 50
[14:45] <DBO> yeah?
[14:46] <MacSlow> leak-footprint is nearly identical
[14:46] <DBO> are you using valgrind?
[14:46] <MacSlow> 3.0 MBytes with 12 secs pauses
[14:46] <MacSlow> 26 MBytes with the 50 & 50 test
[14:46] <MacSlow> not yet
[14:46] <MacSlow> under valgrind
[14:47] <DBO> i am not seeing any leaks when I just run the damn thing and send notifications
[14:47] <MacSlow> I ran into a nasty unrelated bug on my nvidia-box with notify-osd and dual-LCD
[14:47] <MacSlow> but seen these leaks in e.g. pango_cairo_show_layout()
[14:48] <DBO> i dont believe those to be the leaks...
[14:48] <DBO> it just doesn't seem to add up
[14:48] <DBO> and I know valgrind to be imperfect
[14:49] <MacSlow> I think those were listed as "still reachable"
[14:49] <MacSlow> nasty nevertheless
[14:50] <DBO> yeah
[15:02] <DBO> MacSlow, for whatever reason I still only get the memory leak when I hit the stack
[15:04] <DBO> MacSlow, I dont think 12 seconds is enough maybe
[15:04] <DBO> I am going every 30 seconds
[15:05] <MacSlow> 12 shoudlbe enough... an async. bubble is on-screen for 10 sec + 700ms (fade-in and out)
[15:06] <MacSlow> DBO, so the queue should always carry one notification max at any time
[15:06] <MacSlow> DBO, use...
[15:07] <MacSlow> index=1; while (($index<=100)); do notify-send "The Band" "Some Song ($index)" -i totem; echo Spawned bubble $index; sleep 30; index=$((index+1)); done
[15:07] <DBO> i am just trying to watch memory usage with some break points added in "Press enter to continue" kind of breakpoints to bisect down when the memory leak comes in
[15:08] <DBO> im seriously still seeing that memory leak only hits hard once we get queued up
[15:08] <DBO> there is a minor leak for every new icon displayed
[15:08] <DBO> but its like 12 bytes
[15:08] <MacSlow> there are a lot of small leaks like that in glib/gtk+
[15:09] <MacSlow> DBO, I'm on a conf-call atm... so I'm not really fully following here
[15:09] <DBO> oh okay
[15:13] <DBO> MacSlow, when you can, walk me through how the queuing is done
[15:13] <DBO> its a bit dense
[15:14] <MacSlow> after the call
[15:14] <MacSlow> sure
[15:54]  * DBO looks at MacSlow
[15:55] <DBO> still on the call :(
[15:55] <MacSlow> DBO, just closed
[15:55] <MacSlow> DBO, ok... let's turn to class Stack
[15:55] <DBO> okay so lets talk the queue, which looks to be stack.c no
[15:55] <DBO> oh first let me say this
[15:55] <DBO> I just confirmed with another dev, the leak does not happen for them lest they let the notifications stack up
[15:56] <MacSlow> DBO, yeah... the "queue/list" lives in class Stack
[15:56] <DBO> so Im not nuts :P
[15:56] <MacSlow> lest?
[15:56] <DBO> lest == unless
[15:57] <MacSlow> DBO, that's what I also verified with my tests
[15:57] <DBO> sweet
[15:57] <DBO> so we are all on the same page
[15:57] <DBO> so now we gotta smack up this stack
[15:57] <DBO> and make it stop leaking
[15:57] <MacSlow> DBO, I once mined stack.c/display.c and bubble.c with printf()s showing me the ref-counts of all use objects
[15:58] <MacSlow> from that I'm cretain that everything is properly *_dispose()ed
[15:59] <MacSlow> I'll go also your branch so were talking about the same sources
[16:00] <DBO> well lets just work from the observation that someone getting multiple notifications queued up results in memory issues
[16:00] <MacSlow> DBO, did you valgrind a single notification "against" multiple yet?
[16:01] <DBO> nope, why?
[16:01] <MacSlow> valgrind is likely to point "closer to the culprint" than gdb can
[16:01] <MacSlow> DBO, or do you want go "line-by-line"?
[16:01] <MacSlow> just asking
[16:02] <DBO> I want to go functionally
[16:02] <MacSlow> ok
[16:02] <DBO> so when a notification is sent by notify-send
[16:02] <DBO> it goes through libnotify -> notify-osd -> dbus.c?
[16:03] <MacSlow> it comes via dbus and first lands in stack_notify_handler() stack.c
[16:04] <DBO> okay
[16:04] <MacSlow> DBO, see stack-glue.h where the handlers from stack.c get hooked up to dbus
[16:04] <DBO> ok see it
[16:04] <MacSlow> DBO, I don't think we need to touch that
[16:04] <DBO> nope
[16:06] <DBO> okay
[16:06] <DBO> so we are in stack_notify_handler
[16:06] <DBO> we have items in our queue
[16:06] <MacSlow> not yet
[16:06] <MacSlow> I assume a fresh start
[16:07] <MacSlow> so stack.c:584 gets skiped
[16:08] <MacSlow> stack.c:601 also gets skipped (as we assume we get a action-less notification)
[16:08] <MacSlow> DBO, or do you want to lead through stack_notify_handler() asking as question arise?
[16:08] <MacSlow> DBO, what ever you prefer
[16:09] <DBO> I am interested int stack_layout now
[16:10] <MacSlow> ok...
[16:10] <MacSlow> stack_layout() if called walks the queue for the next notification to show
[16:11] <MacSlow> checking if e.g. notifications should be suppressed
[16:11] <DBO> there is a method to my madness, if we were sitting next to each other this would be much easier
[16:11] <MacSlow> and then sees where to place a bubble
[16:11] <MacSlow> DBO, I second that
[16:11] <DBO> stack_layout gets called if only one bubble has been sent, correct?
[16:11] <MacSlow> yes
[16:12] <MacSlow> a timed out bubble "triggers" it or a new notification coming in
[16:12] <DBO> stack_next_to_display
[16:12] <DBO> stack_select_next_to_display
[16:12] <DBO> lets look there
[16:13] <DBO> how do I send a syncronous notification?
[16:13] <MacSlow> that grabs anything from the top of the queue
[16:13] <MacSlow> via a string-hint
[16:14] <MacSlow> e.g. notify-send "Volume" -i notification-audio-volume-medium -h int:value:75 -h string:x-canonical-private-synchronous:
[16:14] <DBO> ah
[16:14] <MacSlow> -h introduces a hint
[16:15] <DBO> how does a bubble get removed from this list?
[16:15] <MacSlow> then a "triplet" tells what type of hint, name and value
[16:15] <DBO> i see the ability to select the bubble, but where does it get removed from the list
[16:16] <MacSlow> DBO, ocne it times out (fade-out animation finishes) it gets unref'ed
[16:16] <DBO> that doesn't remove it from the list...
[16:16] <MacSlow> stack.c:251
[16:16] <MacSlow> it's a GWeakNotify callback
[16:16] <DBO> oh there
[16:16] <MacSlow> that kicks it from the list
[16:16] <DBO> okay
[16:21] <DBO> MacSlow, is my cursory glance that there isn't really much code that doesn't get executed when there is only one bubble somewhat accurate?
[16:22] <MacSlow> double negation?! :)
[16:23] <DBO> there isn't much code that gets executed only when there are multiple items in the queue
[16:23] <MacSlow> yeah
[16:24] <MacSlow> the queue is filled up until 50 notifications are in queue
[16:24] <MacSlow> and one at a time is displayed
[16:25] <MacSlow> as one notification fades out it gets removed from the queue
[16:25]  * DBO wonders why getting more than depth == 1 has such hard fail
[16:25]  * MacSlow does too
[16:25] <DBO> the logic seems sound...
[16:25] <MacSlow> otherwise we'd be jumping at the bug right away :)
[16:26] <MacSlow> gee I've this bug again
[16:26] <MacSlow> F**K!
[16:28] <DBO> ?
[16:29] <MacSlow> icons missing... leading to "no layout"-errors... causing failing rendering
[16:30] <MacSlow> that stated with the extraction of the notify-osd icons from the themes into a separate package
[16:30] <MacSlow> brb
[16:30] <DBO> speaking of line 256 of stack.c
[16:30] <DBO> damnit!
[16:30] <DBO> get back here!
[16:30] <mac_v> tedg: do you also think the indicator messages icon should have something extra? to denote new?
[16:31] <tedg> mac_v: Yeah, I do...
[16:31] <mac_v> hehe ;p
[16:32] <mac_v> hmm, i think djsiegel or DanRabbit decided not to have an icon change
[16:33] <mac_v> but just to make it highlight
[16:33] <djsiegel> mac_v: the envelope gets bolder
[16:33] <djsiegel> but the panel icons for humanity are going to be changed abit
[16:33] <djsiegel> they are too light
[16:34] <mac_v> djsiegel: yeah, i know but > bug #392265 , do you want an extra emblem of sot?
[16:34] <ubot4> Launchpad bug 392265 in humanity-icon-theme "Indicator-applet icon for "new message" is too visually similar too the default icon" [Undecided,Confirmed] https://launchpad.net/bugs/392265
[16:35] <djsiegel> mac_v: I do think they are too similar
[16:35] <djsiegel> but I don't know if an emblem is a good way to go
[16:35] <djsiegel> maybe a the envelope could fill, become solid white
[16:35] <djsiegel> err, solid gray/black
[16:35] <mac_v> hmm , yeah something of the sort
[16:35] <mac_v> i'm working on that atm
[16:36] <mac_v> djsiegel: there is a problem , if we make it darker then the icons will not be visible in dark panels i.e.>UNR  , so what we can do is , split *only* the panel icons into a separate theme , which will be a very small package and name it Humanity_dark or whatever ,
[16:37] <mac_v> make it inherit the rest of the humanity icons and all will be happy
[16:37] <njpatel> humanity needs a dim bluetooth panel icon too, fwiw
[16:38] <mac_v> njpatel: the bluetooth icon will be used in the panel :(
[16:38] <MacSlow> DBO, still messed up here
[16:38] <MacSlow> god I hate that
[16:38] <DBO> MacSlow, whats messed up?
[16:38] <mac_v> oops menu*
[16:38] <MacSlow> DBO, starting notify-osd from the shell
[16:38] <njpatel> mac_v: Oh I see
[16:38] <njpatel> mac_v: that sucks
[16:38] <MacSlow> "(notify-osd:15598): Wnck-CRITICAL **: wnck_window_get_window_type: assertion `WNCK_IS_WINDOW (window)' failed"
[16:38] <MacSlow> at least the icon shows again
[16:38] <mac_v> njpatel: DBO says he can hack the notification area to desaturate the icons similar to the UNR inactive window list
[16:39] <mac_v> that will solve all the inconsistency problems
[16:39] <DBO> MacSlow, oh yeah, I saw that...
[16:39] <njpatel> mac_v: that would be a most useful trick
[16:39] <DBO> I was wondering what causes those errors
[16:39] <MacSlow> DBO, I'm not getting them on intel
[16:39] <mac_v> njpatel: you guys need to assign it => DBO
[16:39] <DBO> njpatel, common you were the guy who wrote AWN, remember all those swanky effects you did to xembed things. This is just desat :P
[16:40] <DBO> MacSlow, get them here
[16:40] <njpatel> mac_v: it may be a bit late for karmic, but it's worth investigating
[16:40] <MacSlow> nevermind... just got them on intel too
[16:40] <njpatel> DBO: those days are long gone, I'm in awe of you kids now...with your client side windows
[16:40] <MacSlow> it's from that dnd.c code
[16:41] <MacSlow> njpatel, you've them too
[16:41] <DBO> njpatel, notification area is all xembed still isn't it?
[16:41] <MacSlow> "xembed" *spew³*
[16:41] <MacSlow> :)
[16:41] <mac_v> njpatel: there are complaints about the inconsistencies , this should fix it , we could do a FFE
[16:41] <njpatel> DBO: lol, yes. was just saying :)
[16:42]  * MacSlow want to have FFE as his second forename
[16:42] <DBO> yeah, my logic to "yes this is possible" was largely "I have a slight idea how to do it and have seen AWN do much more impressive things to an xembed"
[16:42] <njpatel> mac_v: it would be good, make a bug against gnome-panel + post to ayatana? Would give the weekend for people to consider it...
[16:43] <mac_v> njpatel: lool already has asked the UX team , they just havent responded yet :(
[16:43] <MacSlow> mac_v, it "just" a few grey lines... how hard can it be
[16:43] <lool> I pinged them again today
[16:43] <njpatel> mac_v: hence I'm thinking ayatana-list....make a little noise if you know what I mean ;-)
[16:43]  * MacSlow crouches from the DUX-crowd
[16:44] <DBO> MacSlow, want help with them wnck errors?
[16:44] <MacSlow> DBO, I'd prefer bullet ;)
[16:44]  * mac_v thinks njpatel / lool making the noise would be better heard ;)
[16:44] <DBO> bang
[16:44] <MacSlow> mac_v, you're probably right
[16:44] <njpatel> mac_v: I would back up your initial noise, don't have time to make noise myself at the moment :D
[16:45]  * mac_v ok , going to yell at the list right -> now
[16:45] <MacSlow> DBO, now... I also get the "no icon/no layout defined"-error with your branch on intel
[16:46] <MacSlow> make that two or thirty bullets
[16:46] <DBO> not my fault
[16:46] <DBO> i didn't touch the wnck codies
[16:46] <njpatel> err, why is there a heart icon inside my nm-applet
[16:46] <DBO> it loves you
[16:46] <MacSlow> DBO, nothing in your patches looks like it indeed
[16:47] <MacSlow> and all worked yesterday with 0.9.22 / trunk
[16:47] <DBO> well the word also tells me you get this on your branch?
[16:47] <njpatel> my ethernet connection loves me...
[16:47] <MacSlow> DBO, I need to go to the capoeira-classes... back in about 2 hours
[16:47] <DBO> njpatel, just make sure to keep your love secret from your switch. It's a bit of a whore
[16:48] <MacSlow> DBO, any questions you have until them... stuff 'em in an email and send it over
[16:48] <DBO> MacSlow, answer my question first damnit :P
[16:48] <DBO> do the issues happen in your branch too?
[16:48] <MacSlow> DBO, regarding the libwnk assertion... sure... go for it
[16:48]  * DBO murders MacSlow
[16:48] <MacSlow> DBO, yes in your branch and in trunk
[16:48] <DBO> okay :)
[16:48] <DBO> thats what I needed to know
[16:48] <DBO> it I will work on it
[16:49]  * MacSlow rejoins the fun in ~2h
[16:49]  * DBO has a math test in ~1h
[16:49] <DBO> I really shouldn't go because I have the flu
[16:49] <DBO> yet oddly I place my grade above the wellbeing of my classmates
[16:50] <MacSlow|capoeira> hehe
[16:50] <njpatel> http://people.canonical.com/~njpatel/network-love.png
[16:52]  * DBO notes there has not been a code commit to trunk since the 0.9.22 release
[16:52] <DBO> njpatel, thats badass
[17:05] <lool> mac_v: around now
[17:06] <mac_v> yup
[17:06] <lool> mac_v: We're speaking of the ubuntuone icon is colourful bug, right?
[17:06] <lool> mac_v: So we discussed in the release meeting and considered that the safest to implement is the icon theme change to use colour icons
[17:06] <mac_v> lool: that one and all icons in general which use the notification area
[17:07] <lool> mac_v: We're still blocked on UX response; I mailed ivanka
[17:07] <lool> mac_v: Yes, but the icons in other packages are historically with colours
[17:07] <mac_v> lool: why revert when a fix is available?
[17:07] <lool> mac_v: What's the fix?
[17:08] <mac_v> lool: DBO says we can tweak out the notification area similar to the window list to desaturate the icons
[17:08] <lool> mac_v: It's a proposed change
[17:08] <lool> mac_v: But it's not developed
[17:08] <lool> mac_v: People had concerns that it was too late for code changes like these
[17:09] <mac_v> we already do it in the window list :(   why not give it a try first
[17:09] <lool> mac_v: My only _personal_ concern for doing that is that it's unlikely that we can distinguish all icons very well if they are desaturated; think of red / orange / green warnings etc.
[17:09] <DBO> its not developed because nobody asked me to develop it :P
[17:09] <lool> mac_v: Because we dont have the time, artwork deadline was yesterday
[17:09] <lool> mac_v: It's not impossible to implement, it's just a) not decided we want that (design team) b) late and risky
[17:09] <mac_v> lool: DBO has been willing to fix it , only no one has asked him to
[17:10] <lool> mac_v: I know
[17:10] <mac_v> oh... ok
[17:10] <lool> mac_v: It might be that the design team says we should do it
[17:10] <lool> mac_v: So what I'd like to ask you folks is to prepare a branch of humanity where we revert to colour icons
[17:11] <mac_v> djsiegel: ^ ?
[17:11] <lool> DBO: If you'd like to propose a patch to implement that feature, that's welcome; we should spend our development resources on fixing crashers at this point though
[17:11] <lool> DBO: (Not my call ultimately of course)
[17:11] <DBO> or mine
[17:12] <DBO> it makes little difference to when it gets done now
[17:12] <DBO> we cant possible ship it with karmic
[17:12] <lool> DBO: Well it's not impossible; there were reactions against following this track, but the design team wasn't there to comment
[17:13] <lool> DBO: I hope the design team will agree with release team / desktop manager / others saying that it's too late to push more code changes now
[17:13]  * DBO wishes he could be involved with these discussions
[17:13] <lool> DBO: The conclusion of the release meeting is the status quo except that we want to prepare the colour icons just in case
[17:13] <lool> DBO: Anybody is welcome as long as the meeting remains productive
[17:13] <djsiegel> lool DBO mac_v, if we just pull humanity's panel icons, it will fall back on GNOME, etc.
[17:14] <djsiegel> or we can just put human panel icons back in
[17:14] <DBO> aaaaaaaaaanyhow
[17:14] <DBO> I am going to get ready for class
[17:14] <DBO> math test
[17:14] <DBO> spreading disease
[17:14] <DBO> its going to be a blast
[17:14] <lool> mac_v: I'll keep you updated on the answer of design team
[17:15] <mac_v> lool: ok
[17:15] <lool> mac_v: Would you ming preparing that humanity branch for me in case we go that route?  This is to speedup merging the change when that's decided
[17:15] <lool> (and if that's decided of course)
[17:16] <mac_v> lool: its no a big deal , once the decision is made we could just yank the icons and be done in 15mins ;)
[17:19] <lool> mac_v: I thought you had a colourful version of these icons as well
[17:20] <lool> mac_v: Or was this only for the categories?
[17:21] <mac_v> lool: we dont have a color version of these *exact* icons , but had color version in a different style , that the deisgn team did not like *at all* , hence these icons... we might as well remove the panel icons and let the gnome icons be used
[17:21] <lool> mac_v: Okay
[17:21] <lool> mac_v: Or the human ones?
[17:22] <mac_v> either way :)
[17:56] <DanRabbit> lool: ping
[17:57] <natewiebe13> being that the artwork deadline has passed.. does that mean gdm is going to stay as-is?
[17:58] <natewiebe13> anyone?
[18:04] <lool> DanRabbit: pong
[18:05] <djsiegel> mac_v, DanRabbit, lool
[18:05] <djsiegel> can we talk here?
[18:05] <djsiegel> I am having three separate PMs
[18:05] <DanRabbit> okay okay
[18:05] <DanRabbit> So
[18:06] <DanRabbit> Here's the exact root of the problem we are facing
[18:06] <natewiebe13> you guys have any ideas about my question?
[18:06] <DanRabbit> The panel uses the same icons as the rest of the UI
[18:06] <mac_v> djsiegel: as i said , this is a patch which dbo has already done for UNR
[18:06] <DanRabbit> And no matter how we draw the icons in the panel, light or dark or purple or whatever
[18:06] <DanRabbit> we can never do a monochrome icon without affecting the rest of the UI
[18:07] <mac_v> but he had written it for the window list , all that needs to be done is assign it to him and he can come up with the patch
[18:07] <DanRabbit> So, what we need is to tell the panel to use different icons than the rest of the UI
[18:07] <lool> Are we speaking of the notification area or the panel?
[18:07] <mac_v> lool yes
[18:07] <djsiegel> The only thing I am in a position to nod at is changes to art files
[18:07] <mac_v> notification area
[18:07] <lool> Q: foo or bar?  A: yes
[18:08] <DanRabbit> and applets
[18:08] <lool> Ok thanks   :)
[18:08] <DanRabbit> if need be
[18:08] <djsiegel> patching applet sounds like a really bad idea
[18:08] <djsiegel> it's just too late
[18:08] <DanRabbit> we're not changing any functionality
[18:08] <mac_v> djsiegel: it is already done for the window list , and it was done by DBO
[18:08] <djsiegel> you guys aren't hearing me
[18:08] <DanRabbit> it'll literally be this much change:
[18:09] <djsiegel> if gcc has to run again, I think it is too late
[18:09] <DanRabbit> "I get my icon from network-stuff.svg" "Now I get my icon from network-stuff-panel.svg"
[18:09] <mac_v> djsiegel: we had been mentioning this since sunday! the UX hasnt responded
[18:09] <djsiegel> mac_v: this is the first I have heard about it
[18:09] <mac_v> lool: has been pinging ivanka and hasnt ot a response :(
[18:09] <DanRabbit> I myself have been saying it since before we switched to monochrome icons
[18:09] <lool> DanRabbit: That would break other themes
[18:10] <DanRabbit> no, because of icon fallback
[18:10] <mac_v> djsiegel:  lool has been pinging ivanka and hasnt a response :(
[18:10] <DanRabbit> ;)
[18:10] <djsiegel> I love the idea, but it's too late
[18:10] <lool> mac_v: It's ok, we will get a reply at some point
[18:10] <djsiegel> too many changes to too many different code bases
[18:10] <djsiegel> let's do it for lucid
[18:10] <djsiegel> but, we have problems to solve in karmic
[18:10] <DanRabbit> then, we must remove monochrome icons in Karmic
[18:10] <DanRabbit> or it'll be broken
[18:10] <djsiegel> yeah
[18:10] <mac_v> lool: but now you guys are saying its frozen :(
[18:10] <djsiegel> ok, lool, what do you suggest?
[18:11] <djsiegel> lool: we need to drop humanity panel icons
[18:11] <djsiegel> what is the branch you were proposing?
[18:11] <lool> DanRabbit, mac_v: We're not going to do anything complex; I'm willing to consider the option of desaturaing notification area at runtime even if it's not my preferred one, but that will only get applied if design team wants it this way and desktop team is confortable with adding the patch that late
[18:11] <lool> The current preferred change if any is to drop the B&W icons
[18:11] <natewiebe13> mac_v, djsiegel, DanRabbit, lool: any ideas regarding if the gdm will be updated.. or if it is staying the same as now.. also i agree with going back to colored panel icons, they look better
[18:11] <lool> The only other option is to keep what we have now
[18:12] <DanRabbit> We don't even have to make a crazy patch like desaturating it!
[18:12] <mac_v> djsiegel: pls read lool's response above , it can be done only if UX insists
[18:12] <djsiegel> lool: please check with desktop team if they are comfortable with the change this late
[18:12] <lool> djsiegel: I'm asking to prepare the humanity changes to revert to the human or gnome icons for notification-area stuff
[18:12] <djsiegel> tell them UX is interested only if it looks like it isn't disruptive
[18:12] <DanRabbit> Gnome would be best
[18:12] <DanRabbit> Human icons are pretty unreadable on the UNR panel
[18:12] <lool> djsiegel: Are you speaking for UX?  I'd rather hear it from ivanka to whom I escalated
[18:13] <djsiegel> lool, I need a description of the problem still
[18:13] <djsiegel> who is worried about Humanity panel icons?
[18:13] <djsiegel> and why?
[18:13] <djsiegel> they icons look too light? That is what I heard
[18:13] <lool> djsiegel: So you're picking this up from ivanka?
[18:13] <djsiegel> lool, yes
[18:13] <lool> djsiegel: I'll forward you the emails then
[18:13] <djsiegel> ok, good
[18:14] <lool> djsiegel: sent
[18:15] <mac_v> djsiegel: the problem is : the panels use greyscale icons for the system icons , but the app icons are in color ... so lool and a few others feel that this is inconsistent behavior... IMO the system icons are greyscale and the rest are color[this is how win 7 does it too only the system icons are white , rest are color]...
[18:15] <lool> djsiegel: We want to know whether the mix of black and white and coloured icons is acceptable for karmic, and what's the design team's preferred solution between all black and white, all colour, and mix of the two
[18:16] <mac_v> djsiegel: if this is acceptable to keep using only the grey *system* icons for the panel , there is no problem *at all* ... its just that they are questioning the inconsistency
[18:16] <lool> mac_v: It doens't compare
[18:16] <djsiegel> ok, I se
[18:16] <mac_v> nothing needs to be done
[18:17] <lool> mac_v: For instance rhythmox is shipped with Ubuntu desktop and UNR; should it be black and white?
[18:17] <lool> mac_v: What about bluetooth?  tomboy notes?
[18:17] <mac_v> lool: as i said app icons are not allowed in the default icon theme
[18:17] <mac_v> only generic icons
[18:18] <mac_v> bluetooth is not a problem
[18:18] <djsiegel> no, we will never get all panel icons uniform as long as apps can put their own icons there
[18:18] <djsiegel> even if we monochrome them forcefully
[18:18] <mac_v> djsiegel: i would say, we just draw a line and say , only system icons are greyscale .... and there is no confusion at all
[18:19] <mac_v> no panel icon change
[18:19] <mac_v> no code break
[18:19] <mac_v> nothing needs to be done
[18:21] <natewiebe13> my opinion on the matter.. is that eventually we will be going to gnome-shell.. ive run gnome-shell with both monochrome icons, and colored icons.. and i find that the colored ones look a whole lot better
[18:22] <mac_v> lool: the bluetooth icon wasnt done , just because we were waiting for the decision... but either way... something needs to be decide
[18:22] <mac_v> decided*
[18:23] <lool> I'm happy I dont have to raise a lot of design or icon questions   :-)
[18:25] <djsiegel> alright
[18:25] <mac_v> djsiegel: lool: seriously... is there a problem if only the system icons are in greyscale? bluetooth will be done... and let the apps have color i dont see why this is considered inconsistent!
[18:25] <djsiegel> the thing I am concerned with is the humanity-style icons appearing in other interfaces
[18:25] <djsiegel> Ok, here is what I would like us to do.
[18:27]  * DanRabbit ---> bathroom
[18:29] <natewiebe13> sjsiegel: if you guys decide to go with the monochrome icons.. itd be awesome if you included an alternate icon theme, either in the repos, or a tar.gz somewhere.. i really like the humanity theme, but if the monochrome icons stay, i think i'll have to switch back to gnome-colors [thumbs down]
[18:30] <natewiebe13> [hate to sound like a broken record]
[18:30] <djsiegel> ok, that decides it, we are doing what natewiebe13 wants :~
[18:30] <djsiegel> :)
[18:30] <mac_v> djsiegel: as of now there is not much problem , of the humanity style icons appearing in the interfaces if we do only the system icons
[18:30] <djsiegel> mac_v: I just need to know of where this is happening
[18:31] <djsiegel> mac_v: if humanity panel icons are not appearing in other interfaces, I would like to keep humanity panel icons, but darken them a tad for the desktop
[18:31] <djsiegel> lool: ^
[18:31] <mac_v> djsiegel: they can be darkened for ubuntu
[18:32] <mac_v> and lightened for UNR
[18:32] <mac_v> thats not a problem
[18:32] <mac_v> djsiegel: check the networking menu
[18:32] <djsiegel> mac_v: please give me a screenshot
[18:32] <djsiegel> mac_v: I am not on ubuntu right now
[18:32] <lool> djsiegel: I dont know
[18:32] <djsiegel> sorry
[18:33]  * mac_v system is too tweaked out
[18:33] <mac_v> give me a couple of mins
[18:33] <djsiegel> ok, I am downloading a karmic daily
[18:35] <natewiebe13> one last question.. then i'll leave you guys to work.. if you go through with monochrome icons.. will you include an alt. colored theme?
[18:35] <djsiegel> natewiebe13: no
[18:35] <djsiegel> natewiebe13: no time for that atm
[18:35] <djsiegel> sorry
[18:35] <djsiegel> mac_v lool DanRabbit, I think we will keep everything as is, but just darken the humanity panel icons for Ubuntu
[18:35] <djsiegel> but I will inspect this problem with the nm-applet in a bit
[18:35] <djsiegel> as soon as karmic downloads
[18:36] <djsiegel> mac_v: if you can get me a screenshot that would be great
[18:36] <natewiebe13> no probs.. if every panel icon was monochrome, i would keep them but.. good work on the theme though
[18:37] <lool> djsiegel: What do you mean "just darken the humanity panel icons for Ubuntu"
[18:37] <lool> djsiegel: It's the same package in Ubuntu Netbook Remix and in Ubuntu Desktop Edition
[18:37] <djsiegel> lool: the humanity panel icons are considered too light, because they were made to look good on UNR
[18:37] <djsiegel> I was told we could do lighter on just the desktop
[18:37] <lool> Who told you that?
[18:37] <djsiegel> I don't remember, mac_v?
[18:38] <lool> Unless we patch the panel to know that it's running on one or the other and to runtime change the icons, no we cant
[18:38] <djsiegel> we can't have humanity-icon-theme-unr ?
[18:39] <lool> Not easily
[18:39] <djsiegel> ok
[18:40] <djsiegel> so, we cannot make humanity panel icons darker in karmic because they will be too hard to see in UNR
[18:40] <lool> (We would have to change a bunch of deps in many packages, add a new package with changed filepathes, change the seeds etc.)
[18:40] <djsiegel> I think we need to pull humanity panel icons for karmic, and do fixes for lucid
[18:40] <mac_v> djsiegel: lool > http://imagebin.ca/view/oFRenHr.html
[18:40] <mac_v> IMO ,its not light for ubuntu
[18:40] <djsiegel> even with the fix that DBO could do, we still would have the dark/light conflict with UNR/desktop
[18:40] <lool> djsiegel: So removing them will fallback on gnome-icon-theme (not human-i-t), ok with that?
[18:40] <mac_v> but we can make it darker ;)
[18:41] <djsiegel> lool: hold on
[18:41] <lool> djsiegel: Can you either send me an email Cc:ing ivanka and pitti on that decision or comment on the bug that this is the decision of the representant of the design team?
[18:41] <djsiegel> mac_v: can you give me another screenshot with those icons removed, falling back on gnome-ico-theme pleae
[18:41] <lool> Cant afford back and forth changes on this issue at this time
[18:41] <djsiegel> lool: yes, please give me the bug
[18:41] <lool> 430277
[18:41] <djsiegel> right
[18:41] <mac_v> djsiegel: argh! give me a sec ;p
[18:42] <djsiegel> bug #430277
[18:42] <ubot4> Launchpad bug 430277 in unr-meta "ubuntuone icon is colorful while the other panel icons are dark" [High,Invalid] https://launchpad.net/bugs/430277
[18:42] <lool> It's notification-area not panel, will update bug title to make it clear
[18:42] <djsiegel> lool: that bug is not a problem because DanRabbit did a humanity style icon for U1
[18:43] <lool> djsiegel: That bug is where we discuss the general issue
[18:43] <djsiegel> ok
[18:43] <lool> updated title to drop ubuntuone part
[18:44] <lool> djsiegel: Ok, it's end of day here; will act on your email or comment when I process emails/bugs next
[18:44] <lool> bye all
[18:45] <natewiebe13> i do have to say.. that im using dust as a theme.. the humanity icons do not work under network-manager in terms of color
[18:47] <mac_v> natewiebe13: as always you can change the theme if you dont like ;p
[18:47] <natewiebe13> just saying they should be darker
[18:47] <mac_v> djsiegel: gnome > http://imagebin.ca/view/JKbE34Bw.html
[18:47] <natewiebe13> http://imagebin.ca/view/PEsIv31.html
[18:48] <mac_v> djsiegel: human > http://imagebin.ca/view/NYTmyv.html
[18:48] <mac_v> natewiebe13:  file a bug
[18:49] <natewiebe13> im using gnome-colors.. i just thought id agree with you that they should be darker
[18:49]  * mac_v makes note... will have to mention to djsiegel's boss that he doesnt use Ubuntu ;0
[18:50] <natewiebe13> anyways.. see you guys later
[18:50] <djsiegel> mac_v: thank you very much for that, I think we should go back to human for those icons
[18:51]  * mac_v realizes djsiegel has poor taste ;p
[18:51] <djsiegel> mac_v: it's not about taste
[18:51] <mac_v> hehe ;)
[18:51] <djsiegel> if this were about the manifestation of my taste, the result would really be great! :)
[18:52] <mac_v> djsiegel:  as i'v mentioned we can make it darker , if thats the problem
[18:52] <DanRabbit> djsiegel: Human icons (particularly the volume) is impossible to read on a dark panel
[18:52] <DanRabbit> it's not going to be good for UNR
[18:52] <mac_v> lool: just do a test and swith unr to human ,you will *not* be able to see the volume level!
[18:52] <mac_v> djsiegel: ^
[18:54] <djsiegel> DanRabbit: what did UNR use in Jaunty?
[18:55] <DanRabbit> I believe Human
[18:55] <DanRabbit> was that rhetorical?
[18:55] <mac_v> djsiegel: the used a different gtk theme , now with dust theme the icons are invocisble
[18:55] <djsiegel> no
[18:55] <djsiegel> unfortunately, in the interest in not breaking too much, I think we should keep jaunty icons in the panel
[18:55] <mac_v> they*
[18:55] <djsiegel> even with their old flaws
[18:55] <djsiegel> mac_v, let those other themes use different icons then
[18:56] <djsiegel> I am concerned with the default theme, with 99% of ubuntu users keep
[18:56] <mac_v> djsiegel: UNR uses dust by default
[18:56] <djsiegel> mac_v, right, so, which icons are invisible in dust?
[18:56] <mac_v> human
[18:56] <djsiegel> so, UNR had invisible panel icons in Jaunty?
[18:57] <djsiegel> and up until a few weeks ago, we were fine with that/
[18:57] <mac_v> djsiegel: UNR used human theme instead of dust in jaunty [AFAIK]
[18:57] <djsiegel> ok
[18:57] <mac_v> djsiegel: could pls remind me , what the breakage is with humanity and these panel icons?
[18:57] <mac_v> coudl you*
[18:58] <djsiegel> (1) the messaging indicator is not differentiated enough
[18:58] <djsiegel> (2) others are claiming these icons are leaking out into other interfaces
[18:58] <djsiegel> (1) is clear, and we can fix it
[18:58] <mac_v> 1> is fixed in latest
[18:58] <djsiegel> really?
[18:58] <mac_v> yes , i just now fixed 1
[18:59] <mac_v> djsiegel: for 2, the screenshots i showed are the only 2 places where the *leak*
[18:59] <mac_v> they*
[18:59] <djsiegel> mac_v, what is the fix for #1?
[19:00] <mac_v> djsiegel: i have changed the icon to fill
[19:00] <djsiegel> ok
[19:01] <djsiegel> mac_v: can you please show me?
[19:04] <djsiegel> mac_v: I think I want the human status icons to be used in humanity, can you expand the session menu and give me a screenshot comparing status icons in human and humanity please?
[19:04] <mac_v> djsiegel: http://imagebin.ca/view/7g8WEw.html
[19:04] <djsiegel> ok, how does that look on a dark panel?
[19:04] <djsiegel> I imagine the "no fill" one is louder, and would connote message available?
[19:04] <mac_v> djsiegel:  i thought we were worried about ubuntu for now
[19:04] <mac_v> yup
[19:05] <djsiegel> mac_v: apparently, that change will trickle into UNR as well
[19:05] <mac_v> djsiegel: UNR we can fix , by making it light ;)
[19:05] <djsiegel> we can't just make UNR light right now
[19:05] <DanRabbit> mac_v: i don't think we're allowed to have separate packages ATM
[19:06] <mac_v> djsiegel: i meant light icons for UNR
[19:16] <djsiegel> So I need to see Human panel icons on UNR
[19:18] <djsiegel> mac_v: can you please prepare a humanity branch that uses Human panel icons?
[19:18] <mac_v> djsiegel: kenneth told we are not allowed to copy human's icons... you need to ask him... either way , the packaging can be done any way ubuntu wants ;)
[19:19] <djsiegel> mac_v: I am talking to him now, he says it's fine
[19:20] <mac_v> djsiegel: DanRabbit is the main owner of the Humanity branch , branching it has to be done by him
[19:20] <djsiegel> yes, I am saying that kwwii says we can copy human icons
[19:20] <DanRabbit>  I'll do it in a bit
[19:20] <DanRabbit> I have to go get some dry ice because my gf's car has a dent
[19:20] <DanRabbit> brb
[19:22] <djsiegel> lool: you here?
[19:47]  * DBO looks for a MacSlow|capoeira
[20:04] <MacSlow> DBO, re
[20:10] <MacSlow> DBO, I need to hit the bed... I'm exhausted.
[20:17] <mrooney|w> Whoever has made Humanity the default icon set in 9.10 is a very good person.
[21:44] <natewiebe13> mac_v: did you say that ubuntuone had a monochrome icon?
[21:45] <mac_v> nope
[21:45] <mac_v> djsiegel: ^ mrooney|w's comment ;p
[21:45] <mrooney|w> ah I figured he might be the one!
[21:46] <djsiegel> mac_v: ?
[21:46] <djsiegel> what did mrooney|w say?
[21:46] <mac_v> djsiegel: [00:47] <mrooney|w> Whoever has made Humanity the default icon set in 9.10 is a very good person.
[21:47] <DanRabbit> :D
[21:47] <DanRabbit> That's awesome
[21:47] <DanRabbit> that almost brings a tear to my eye
[21:47] <djsiegel> don't praise me, praise DanRabbit and mac_v for working so hard, and kwwii for saving us all in the end, and ivanka for pestering mark :)
[21:47] <djsiegel> omg I am going to cry
[21:48] <djsiegel> we are such a good team
[21:48] <djsiegel> even if the last couple days have been a nightmare
[21:48] <DanRabbit> haha
[21:48] <DanRabbit> group hug!
[21:53] <mrooney|w> and more than 2 backgrounds, this is glorious
[21:54] <natewiebe13> so is there going to be a new icon made for ubuntuone?
[21:54] <lamalex> wow, and good ones
[21:56] <djsiegel> lamalex: :)
[21:56] <djsiegel> natewiebe13: yes, DanRabbit made it and I just sent it to the U1 guys
[21:56] <djsiegel> lamalex: those are from the contest
[21:57] <lamalex> the problem with the matching notification area icons is that basically every app needs one made now for that to stay uniform
[21:57] <djsiegel> lamalex: or apps need to stay out of the panel
[21:58] <lamalex> oh yah, or that :)
[21:58] <natewiebe13> djsiegel: how about the actual ubuntu logo for the menu, and weather icons? if those get made.. i'll keep humanity
[21:58] <djsiegel> natewiebe13: we aren't doing this just for you, you know :)
[21:58] <djsiegel> so don't try to negotiate with what you want :)
[21:58] <natewiebe13> i know.. im just asking
[21:59] <djsiegel> isn't the actual ubuntu logo uses?
[21:59] <djsiegel> used
[22:00] <DanRabbit> Can't do the ubuntu logo because it shows up in other places
[22:00] <DanRabbit> it's a leaker
[22:00] <djsiegel> oh, I see, he wants that monochrome too
[22:00] <lamalex> DanRabbit: unless that gnome-applet was patched to use a different icon
[22:01] <natewiebe13> okay.. how about the weather icons?
[22:01] <lamalex> ubuntu-monochrome or something
[22:01] <mac_v> djsiegel: DanRabbit: i think we need a blueprint for lucid , for the notification area
[22:01] <DanRabbit> lamalex: that's what I keep saying, but not until Lucid
[22:01] <lamalex> DanRabbit: ah
[22:01] <lamalex> well I agree with you :)
[22:02] <natewiebe13> DanRabbit: how about weather icons?
[22:02] <DanRabbit> same
[22:02] <natewiebe13> okay
[22:03] <mac_v> natewiebe13: do you like the greyscale icons or you hate them... ;p ... a few mins back you said you didnt like now you want all in greyscale ;)
[22:04] <natewiebe13> DanRabbit: dont get me wrong.. i really like the theme.. itd just be nice to be uniform..
[22:04] <natewiebe13> i would like them if they were all greyscale.. but if some are and some arent.. id rather have them all color
[22:04] <mac_v> DanRabbit: back up the icons ... heavy edits on the way ;0
[22:04] <mac_v> oops wrong channel!
[22:05] <DanRabbit> I understand how you feel, I would like them all in monochrome as well
[22:05] <natewiebe13> mac_v: ^
[22:05] <DanRabbit> unfortunately, we can't make those changes until Lucid
[22:05] <natewiebe13> DanRabbit: awesome.. thats what i wanted to know
[22:05] <mac_v> natewiebe13: we too , but the code doesnt allow atm
[22:05] <lamalex> DanRabbit: are you going to be at UDS-L?
[22:06] <DanRabbit> I applied ;)
[22:06] <lamalex> cool
[22:15] <mrooney|w> yes I have to apply
[22:16] <mrooney|w> it is actually pseudo-close to me this time!
[22:16] <lamalex> at least closer than Barcelona
[22:30] <mrooney|w> well when it was in CA I was in PA on the other side of the US
[22:30] <mrooney|w> now that I am in CA, it is in TX, not tooo bad
[23:18]  * DanRabbit ---> work


[07:13] <dholbach> good morning
[07:46] <davidcalle> good morning o/
[15:55] <dholbach> all right my friends - I call it a day - see you all tomorrow!


[10:44] <Saviq> karni, hey, around?
[10:53] <karni> Saviq: boarding in 20 minutes in Frankfurt. wasup?
[10:53] <Saviq> karni, man, you're connecting to London? /me flies Ryanair there ;)
[10:54] <Saviq> karni, just replied to your email
[10:54] <Saviq> karni, unmap summary and cards will be fine again
[10:54] <karni> yaaaay
[10:54] <karni> nope, Orlando
[10:54] <Saviq> karni, ah, right
[10:54] <karni> :)
[10:54] <karni> Thats awesome man!
[10:54] <karni> great news
[10:55] <Saviq> karni, well, not tested 'cause you only sent armhf scopes, but that's the explanation I can come up with
[10:55] <Saviq> karni, 'cause CardTool has to take the "potential" summary into account when calculating the card size for grid
[10:57] <Saviq> karni, safe flights!
[10:57] <karni> Yes, makes sense
[10:57] <karni> Im prettysire empty summary was mapped!
[10:57] <karni> Thanks, Saviq!
[10:57] <Saviq> karni, yup, I expect so
[10:57] <Saviq> o/
[10:57] <karni> \o
[10:57] <Saviq> karni, just replied re: dash background, too
[10:58] <karni> ack
[10:58]  * karni nods
[10:59] <karni> Gotcha,thank you.
[10:59]  * karni disappears
[18:08] <Saviq> sampth, hey
[18:13] <sampth> hi.. i have a few questions regarding unity 8
[18:14] <sampth> i already asked this on the phone mailing list.. so pardon me for boring you :P
[18:15] <sampth> i run ubuntu touch on nexus 4 through dual boot with android 4.3 eadio.. and i'm getting frequent unity 8 crashes
[18:16] <sampth> and the phone heats up like crazy sometimes after the crashes
[18:17] <sampth> what could possibly be the problem?
[18:18] <Saviq> sampth, I was replying to your questions on the mailing list
[18:19] <Saviq> sampth, does it get permanently hot or only while unity8 is hanging?
[18:19] <sampth> oooh.. sorry.. didn't recognise you.. got confused
[18:20] <Saviq> sampth, no worries
[18:20] <Saviq> sampth, after it crashes, apport collects all the needed data into the .crash file, and that might cause it to go hot, but should only be a few seconds, maybe half a minute
[18:20] <sampth> its generally warmer when i'm using ubuntu touch
[18:20] <Saviq> sampth, well, that's possible, we haven't optimized a lot of things yet
[18:20] <sampth> which i'm addicted to 99.9% of the time :)
[18:21] <Saviq> sampth, but if it gets really hot, most probably something's wrong - it's useful to then adb into the phone and use 'top' to see which process is spinning
[18:21] <sampth> i do understand it being in development.. u guys have done an awesome job really
[18:22] <sampth> i'll do that first thing tomorroow morning.. running on a perenially slow internet
[18:29] <sampth>  i just ran top and pulseaudio seems to use 1.0% of cpu.. is it 1% or 100%?
[18:29] <sampth> ok stupid question that was
[18:30] <sampth> top itself uses 2.3%
[18:30] <sampth> no process seems to be eating into my memory.. the phone is a little lukewarm now however..not really burning hot
[18:32] <sampth> and the crash file generated and uploaded successfully btw
[18:33] <sampth> i experience crashes mainly when searching for content online
[18:33] <sampth> local searches are no problem


  Sunday built some more of my millenium falcon as you do
[09:13] <seb128> desrt, went to the spa, did some shopping, played tennis and spent sunday relaxing with familly ... you?
[09:15] <davmor2> seb128: https://goo.gl/photos/pu1KrLrPwMVDB8YG6
[09:15] <desrt> on saturday had a visitor from a neighbouring country, spent a day in the city.  on sunday went for a nice hike in the woods around a lake near the refugee shelter where mascha first stayed in germany
[09:16] <desrt> also sunday: spent a lot of time dealing with mascha having had her cellphone/wallet/etc. stolen on saturday night :(
[09:16] <seb128> nice, did you have good weather?
[09:16] <flexiondotorg> I slept this weekend. Lots of sleeping.
[09:16] <seb128> it has been mostly raining here yesterday
[09:16] <seb128> flexiondotorg, that's a good w.e activity :-)
[09:16] <desrt> yes.  awesome weather all the time.  it rained for like 1 hour on sunday and it corresponded almost perfectly to the time we went into a cafe to get a tea
[09:16] <seb128> desrt, oh, things stollen, that's less nice :-(
[09:16] <TheMuso> Hey folks.
[09:16] <flexiondotorg> seb128 Was required because there was very little sleeping during MWC.
[09:16] <seb128> oh, right mwc
[09:16] <flexiondotorg> TheMuso o/
[09:17] <seb128> did you enjoy it?
[09:17] <seb128> hey TheMuso
[09:17] <desrt> ya.  it really did a number on her, i think.  there was a lot of work-related stuff in there that is extremely difficult to replace/fix... plus all the usual photos/contacts/etc. problems
[09:17] <desrt> in the phone, i mean
[09:17] <flexiondotorg> seb128 Yes, MWC was great fun and completely exhausting in equal measure.
[09:17] <flexiondotorg> Lots of very good conversations.
[09:17] <seb128> nice
[09:17] <seb128> desrt, :-(
[09:17] <TheMuso> Anybody here have enough of an understanding of systemd user session stuff to help me work out why systemctl --user status at-spi-dbus-bus shows an inactive/dead service? I'm trying to work out why at-spi doesn't load for unity-panel-service, and also similar problem with the MATE panel.
[09:18] <TheMuso> Everything else is accessible by the time the session loads, but for whatever reason that user systemd service is inactive/dead.
[09:18] <seb128> TheMuso, can you pastebin the status output?
[09:18] <seb128> is there any log with it?
[09:18] <TheMuso> Sec.
[09:19] <TheMuso> http://paste.ubuntu.com/24123768/
[09:19] <seb128> davmor2, just looked at the phone, nice work!
[09:21] <TheMuso> I also have this in syslog: Mar  6 12:40:02 buffalo unity-panel-ser[3436]: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-6n1bOochIC: Connection refused
[09:22] <seb128> TheMuso, if you "systemctl start at-spi-dbus-bus.service" does it work?
[09:23] <TheMuso> seb128: Will try it, but at-spi is running, because everything else in my session, with the exception of the panel-service is accessible with Orca.
[09:23] <seb128> TheMuso, it could be dbus activated?
[09:23] <seb128> or spawned by something else?
[09:24] <TheMuso> seb128: Now I get this: http://paste.ubuntu.com/24123782/
[09:24] <TheMuso> Well the service file in the usr/lib/systemd/user directory shows that it is for dbus activation.
[09:24] <TheMuso> http://paste.ubuntu.com/24123784/
[09:24] <TheMuso> Is the service file.
[09:26] <TheMuso> So starting the service works, but there is no point, because not everything is accessible in the first place, unless I kill it.
[09:26] <TheMuso> And at-spi still gets started up.
[09:26] <TheMuso> It shoudl also be worth noting that the way debian/ubuntu package at-spi2-core is no different from other distros re the service file, and this seems to work fine on other distros, baring in mind that I get the same problem with MATE panel when running a MATE session.
[09:30] <seb128> TheMuso, do you have a corresponding .service in /usr/share/dbus-1/services ?
[09:31] <seb128> TheMuso, you can also look in the ps output what started your unit
[09:35] <TheMuso> seb128: Yes, /usr/share/dbus-1/services/org.a11y.Bus.service
[09:35] <TheMuso> What argument to ps to look up what executed a process?
[09:35] <TheMuso> Urm, oh the unit
[09:35] <TheMuso> Well the unit doesn't get started by default.
[09:35] <TheMuso> As shown earlier, its inactive/dead.
[09:36] <seb128> TheMuso, you can "ps aufx" and see what at-spi is a subprocess of in the list
[09:38] <TheMuso> seb128: Seems gnome-session... /usr/share/dbus-1/services/org.a11y.Bus.service
[09:39] <TheMuso> Whoops wrong line.
[09:39] <TheMuso> /usr/lib/gnome-session/gnome-session-binary --session=ubuntu
[09:39] <TheMuso> Which starts it via xdg-autostart
[09:39] <TheMuso> /etc/xdg/autostart/at-/etc/xdg/autostart/at-spi-dbus-bus.desktop
[09:43] <Laney> hey TheMuso - you just reminded me that I've not replied to you yet - sorry, will do that soon
[09:44] <Laney> and yeah, if there's nothing to bus activate because the thing is already running then that would explain why the unit didn't get started
[09:50] <seb128> TheMuso, there you go
[09:50] <Laney> ah man, just got a text reminding me of a dentist appointment at 08:50 on wednesday
[09:50] <Laney> WHYYYYYYYYYYYY
[09:50] <seb128> TheMuso, I guess that autostart is ubuntu specific which is why other distros don't have the issue?
[09:51] <Laney> I guess that most normal people expect to be somewhere by 08:50 every day of the week
[09:51]  * Laney coughs
[09:55] <TheMuso> seb128: No its not.
[09:55] <TheMuso> Other distros also have that file.
[09:55] <TheMuso> But Debian does modify it such that it does run everywhere.
[09:55] <TheMuso> Laney, seb128, tomorrow I'll do some more digging. It may be a matter of reversing Debian's modifications and seeing how things go.
[09:55] <seb128> TheMuso, well try without if that makes things better, that file is useful for most distro/desktop which don't use sytemd user session
[09:55] <TheMuso> Laney: And no worries no rush.
[09:56] <seb128> right
[09:56] <TheMuso> Right I know.
[09:56] <TheMuso> TIme for bed. Laters.
[09:56] <willcooke> night TheMuso
[09:57] <TheMuso> Night willcooke.
[09:59] <seb128> night TheMuso
[10:01] <Laney> nn
[10:03]  * didrocks hellos while doing bisecting
[10:07] <desrt> attente: found something nice at /proc/self/attr/current
[10:08] <desrt> aka 'really really quick way to find out if i'm a snap or not'
[10:08] <Laney> hey didrocks
[10:08] <Laney> good bad good good bad?
[10:09] <didrocks> Laney: I'm good, thanks! Couldn't go out at all for the week-end due to weather, but ok otherwise :)
[10:09] <Laney> you're like a caged animal
[10:09] <Laney> grrrrar
[10:14] <didrocks> ahah
[10:14] <didrocks> not untrue :)
[10:14] <Laney> was quite moist here too
[10:20] <didrocks> yeah, I guess it's this time of the year
[10:20] <didrocks> but soon, sun, out, nice weather :)
[10:20] <Laney> \o/
[10:22] <Laney> things are happening
[10:22] <Laney> my daffodils have been in flower for a week or so now
[10:22] <Laney> the trees look like they are going to get leaves soon
[10:23] <Laney> the wild garlic is coming up
[10:47] <willcooke> back
[10:47] <willcooke> looks like my WAN ip changed and so all my routes broke
[11:32] <Laney> jbicha: thx for doing those kylin reviews
[11:37] <attente> desrt: cool
[11:37] <desrt> attente: good morning :D
[11:38] <attente> good afternoon :)
[11:38] <Laney> what's going on here
[11:38] <desrt> attente is here!
[11:38] <desrt> ...is what's going on
[11:39] <Laney> ROLLEYES
[11:39]  * Laney searches for them
[11:39] <Laney> wish I hadn't rolled them away now
[11:45] <davmor2> Laney: that's what you get for not using an eyerolling box I've told you before :D
[14:16] <qengho> Hrm. https://www.reddit.com/r/linux_gaming/comments/5xics8/a_big_problem_with_joysticks_in_linux_right_now/?st=izy6vtng&sh=2c9c62ca
[14:17] <qengho> Summary: 1) evdev isn't as good as deprecated joydev, misses features. 2) Joystick callibration is lost when you unplug.
[14:24] <dobey> qengho: i can't even get steam to recognize my steam controller, so uh...
[17:12] <jbicha> Laney: ukui-menu uses python2; at this point is that ok since the Ubuntu desktop still has some parts using python2, if Kylin promises to fix that for 17.10? or is this something we should be firm about?
[17:15] <Laney> jbicha: I wouldn't want to add any more to Ubuntu desktop if we can help it but if they don't care for their flavour then I struggle to work myself up to bothering either
[17:26] <tedg> In Zesty, I'm getting failures with g-ir-scanner not finding a library. Have there been any changes there that anyone knows about? Failing for weird reasons.
[17:42] <Laney> tedg: not seen anything like that myself
[17:43] <Laney> got some output?
[17:44] <tedg> Laney: I do, but it's not super useful: https://launchpadlibrarian.net/309868665/buildlog_ubuntu-zesty-amd64.ubuntu-app-launch_0.10+17.04.20170306-0ubuntu1_BUILDING.txt.gz
[17:45] <tedg> I thought it was some recursive dep thing with all the stuff stuck in proposed, but that cleared on Saturday.
[17:46] <tedg> I think that dobey noticed that it built right before updates. So I think I'm going to track those down now to confirm :-/
[17:46] <jbicha> tedg: I did see something similar today
[17:46] <jbicha> https://launchpad.net/ubuntu/+source/meson/0.39.0-1/+build/12090452
[17:47] <jbicha> meson builds fine on sid but it gets the same failure when built with glib2.0 2.51.2
[17:48] <dobey> ugh most of the changes in this gir release are all just visual studio junk changed
[18:00] <dobey> oh
[18:01] <bregma> that sounds hopeful?
[18:01] <dobey> maybe, we'll see
[18:04] <dobey> yay
[18:05] <dobey> jbicha: you removed laney's patch that wasn't upstreamed; re-applying fixes the problem
[18:05] <dobey> -support-non-gobject-libraries.patch
[18:05] <dobey> that one
[18:06] <dobey> (the upstream bug it links to, is still open, fwiw)
[18:07] <dobey> jbicha, Laney: so can we get that patch added back and a new upload, for gobject-introspection?
[18:07] <dobey> (not sure if the other two patches are still valid or not, didn't check them)
[18:10] <bregma> ah, that patch
[18:11] <bregma> I remember running in to that problem several times
[18:11] <jbicha> dobey: oh :( I mistakenly thought gobject-introspection was in sync with Debian, that's why the changelog doesn't mention sync or merge or dropped patches
[18:11] <jbicha> I'll fix that now
[18:14] <tedg> Cool, thanks dobey, thanks jbicha
[18:15] <jbicha> dobey: thanks for figuring that out!
[18:17] <jbicha> Laney: we don't need these 2 patches any more apparently?
[18:17] <jbicha> https://launchpad.net/ubuntu/+source/gobject-introspection/1.50.0-1ubuntu2
[18:35] <Sweet5hark> https://biterrant.io/ <- ah, so much for the "SHA1 collision? but that is just a theoretical issue ..."
[18:36] <willcooke> dinner time, night all
[18:37] <jbicha> willcooke is not one for long goodbyes
[18:40] <sarnold> Sweet5hark: it's more fun to ignore their capitalization and read it instead as 'ermagerd bitterrant'  :)
[18:41] <Sweet5hark> sarnold: ;)
[20:16] <jbicha> tedg: the new g-i fixed the meson build
[20:17] <tedg> jbicha: Cool, locally or is it in the archive?
[20:20] <jbicha> both g-i and meson are in zesty-proposed
[20:27] <dobey> tedg: the ual silo already rebuilding fwiw
[20:28] <Laney> jbicha: I don't see why we wouldn't need them
[20:28] <tedg> Yup, it is looking good.
[20:29] <Laney> I got excited when I saw ual, but it is a silo for something else apparently
[20:30] <dobey> Laney: as opposed to?
[20:30] <tedg> Laney: That's next, this was an emergency request
[20:30] <tedg> dobey: Removing Upstart
[20:31] <dobey> oh