[05:30] <pitti> Laney: yup, glib is now in; I'm still looking at the hanging udisks2, I can't reproduce that locally
[06:20] <pitti> ah, now I can actually, with the latest kernel/image
[06:24] <larsu> good morning!
[06:24] <pitti> hey larsu!
[06:25] <larsu> pitti: happy Monday! Wie geht's?
[06:25] <pitti> larsu: gut, danke! wir hatten ein schoenes WE in Dresden. und dir?
[06:28] <larsu> pitti: schön! Mir auch. Viel Familie dieses WE
[06:28] <larsu> und kaaaaaaalt
[06:34] <ochosi> larsu: in .at ists auch nicht viel besser (temperaturmäßig), falls dich das tröstet ;)
[06:35] <larsu> ochosi: ein bisschen :)
[07:02] <didrocks> good morning
[07:03] <pitti> bonjour didrocks, c,a va ?
[07:03] <pitti> oops -- where is my compose key??
[07:03] <larsu> lut didrocks!
[07:03] <didrocks> pitti: ça va bien, et toi ?
[07:03] <didrocks> hey larsu :)
[07:04] <pitti> didrocks: je vais bien aussi, merci ! nous avons eu un bon week-end a` Dresden
[07:04] <didrocks> pitti: pas trop court ?
[07:04] <pitti> didrocks: toujours :)
[07:04] <didrocks> héhé ;)
[07:05] <pitti> didrocks: mais pendant les vacances Noe:l nous allons avoir beaucoup de temps
[07:05] <didrocks> certes !
[07:06] <didrocks> nous, on a joué à des jeux de société vendredi soir dans une ONG
[07:06] <didrocks> nous sommes allés à un concert de musique classique samedi soir
[07:06] <didrocks> et j'ai terminé mass effect 3 hier :)
[07:07] <pitti> :-P c'est grand ! -- qu'est-ce que c'est "ONG" ?
[07:07] <didrocks> pitti: NPO
[07:07] <pitti> TLAs!
[07:07] <pitti> non-profit organization ?
[07:07] <didrocks> right ;)
[07:08] <didrocks> like a local group of people, you need to be a member to play in the local
[07:15] <didrocks> pitti: should I ping back on my systemd patch on upstream ML?
[07:15] <didrocks> maybe CCing Lennart
[07:15] <pitti> didrocks: perhaps try on IRC around noon/afternoon first?
[07:16] <didrocks> pitti: ok, will do then
[07:16] <pitti> didrocks: but sure, CC'ing him might help too, I don't know
[07:16] <didrocks> will try IRC first
[08:53] <willcooke> morning all
[08:57] <larsu> morning willcooke!
[08:57] <darkxst> hey larsu
[08:57] <larsu> hi darkxst
[08:57] <darkxst> any progress on gtk?
[08:58] <didrocks> hey willcooke
[08:58] <darkxst> hey didrocks
[08:58] <larsu> darkxst: progress for getting it in?
[08:58] <seb128> good morning desktopers
[08:59] <darkxst> larsu, well yes of course ;)
[08:59] <darkxst> hi seb128
[08:59] <larsu> darkxst: the theme should be good enough for a first upload, but there are a few other minor issues with 3.14
[09:00] <larsu> so ya, progress, but not done yet
[09:00] <seb128> the icons one is a bit annoying
[09:00] <larsu> next on my list :)
[09:01] <darkxst> seb128,  yes there are new icons
[09:01] <seb128> I don't speak about new or old icons
[09:01] <darkxst> what do you speak of then?
[09:01] <seb128> but thinks like indicators having wrongly scaled icons
[09:01] <seb128> or gvim in nautilus' context menu
[09:03] <didrocks> evening darkxst ;)
[09:06] <darkxst> seb128, perhaps a theme issue, I'
[09:06] <darkxst> I've not seen anything like that
[09:07] <seb128> no, not a theme issue, Debian has the same issue
[09:07] <ricotz> hello to all of you
[09:07] <seb128> with updated themes and using the upstream one
[09:07] <seb128> hey ricotz
[09:07] <ricotz> is there a plan/decision about splitting adwaita-icons-theme like it is done with gnome-icons-theme?
[09:08] <darkxst> hey ricotz
[09:08] <ricotz> seb128, hi, did darkxst mentioned this to you?
[09:08] <seb128> ricotz, he probably mentioned it before, no plan/decision that I know about
[09:08] <darkxst> I mentioned it a while back, never got an answer though
[09:08] <seb128> I guess whoever is interested in that new package needs to do the work
[09:08] <seb128> or I don't see an incensitive from changing from g-i-t as we have it atm
[09:09] <darkxst> seb128, we would be happy to keep the new package synced from debian
[09:09] <darkxst> but there are new icons needed for 3.14 that would need to be copied into g-i-t
[09:09] <seb128> well, as long as it's not installed and nothing in Unity depends on it
[09:09] <ricotz> seb128, did the ubuntu icon theme gained the needed bits?
[09:09] <seb128> no
[09:10] <seb128> what needed bits?
[09:10] <seb128> did anyone made a list/open a bug?
[09:10] <ricotz> like e.g. the arrows for combo-boxes
[09:10] <seb128> no idea what you are talking about
[09:10] <darkxst> ubuntu icon theme falls-back to gnome for like a 100icons
[09:11] <seb128> yeah, that's not going to change
[09:11] <ricotz> darkxst, keeping it in sync would be nice of course
[09:11] <darkxst> seb128,  have you not noticed missing icons in testing 3.14?
[09:11] <ricotz> i see, so it seems reasonable to switch depending on adwaita-icon-theme for 3.14
[09:11] <seb128> darkxst, no, but I didn't test much
[09:12] <seb128> ricotz, we are not switching anything to a-i-t until it gets the same split as g-i-t if that's the one supperseeding g-i-t
[09:13] <ricotz> seb128, this is what i am asking, and gnome3 ppa contains a splitted packages
[09:13] <ricotz> and yeah a-i-t is the replacement for g-i-t
[09:13] <seb128> do you have a sponsoring request with the changes?
[09:14] <ricotz> no, since as you said there is plan to pursue this while weirdly no problems occur with g-i-t and gtk 3.14 regarding missing icons
[09:15] <seb128> ?
[09:15] <seb128> no, I said I've no clue what issues you are talking about
[09:15] <ricotz> i mean "no plan"
[09:15] <seb128> but that if there is nothing buggy there is no need to change
[09:15] <seb128> if the gtk update is buggy we need to update the icon theme of course
[09:15] <ricotz> yeah, this is weird since things like arrows should not show up
[09:15] <seb128> and we need to do it in a way that doesn't regress what we have
[09:16] <seb128> what arrows?
[09:16] <ricotz> larsu, hi, did you not run into such issues ^
[09:17] <ricotz> seb128, the e.g. tiny "down-arrow" on combo-boxes!
[09:17] <darkxst> seb128, the list arrows in things like dconf editror
[09:18] <ricotz> anyhow, i need to go, bbl
[09:18] <larsu> ricotz: what issues? Arrows in list views having the wrong icons? (yes)
[09:19] <ricotz> larsu, if they are wrong or missing it is related to the icon-theme
[09:19] <larsu> ricotz: not sure what the issue is. Probably missing, yes
[09:21] <darkxst> larsu,  there are a number of icons definately missing from g-i-t!
[09:21] <larsu> I know. Not sure what your point is...
[09:21] <ricotz> https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-14&id=9a127d364f9413f3e7c431c09ff4495f0ac88137
[09:22] <ricotz> "pan-down-symbolic"
[09:31] <Sweet5hark> moin
[09:31]  * Sweet5hark .oO( life isnt fair )
[09:32] <darkxst> larsu, the point is either need to split a-i-t or copy the missing icons across to g-i-t
[09:38] <Laney> I copied a couple of icons from a-i-d to <mumble> (humanity?) a while ago
[09:38] <Laney> -t
[09:39] <Laney> pan-something ones
[09:40] <seb128> hey Laney
[09:40] <Laney> hi ;-)
[09:40] <Laney> just sneaking through, nothing to see here
[09:42] <Laney> how's it going?
[09:42] <mlankhorst> morning
[09:43] <darkxst> Laney, I'm all for the copying thing, I would prefer to keep a-i-t in sync with debian
[09:43] <seb128> Laney, good, you? had a good w.e?
[09:46] <Laney> darkxst: alternatively we could not care about the size (~10mb) :-)
[09:46] <Laney> seb128: yeah was good, put all of our things in a van and drove them somewhere else and then removed them all
[09:47] <seb128> Laney, I don't want to go that path (stop carring about adding 10mb packages to the iso)
[09:48] <seb128> Laney, oh, right, moving ... you are not working this week?
[09:48] <seb128> what are you doing here?
[09:48] <darkxst> seb128, stop complaing, upstream was just a rename, you wouldnt add anything to the iso
[09:48] <seb128> darkxst, ?
[09:48] <seb128> darkxst, I'm not complaining
[09:49]  * larsu waves to Laney
[09:49] <seb128> darkxst, I'm just saying that we are not going to add another 10mb to the iso
[09:50] <darkxst> seb128, and we need to know if you want to split a-i-t or stick with g-i-t
[09:51] <seb128> darkxst, I don't care either way, either we copy the missing icons over or we split a-i-t and transition to that
[09:51] <seb128> up to who does the work I guess
[09:51] <seb128> it probably makes more sense to split a-i-t
[09:52] <willcooke> mlankhorst, hey!  I'm going to try and get your Xmir work running today. I might be bothering you with questions :)
[09:52] <darkxst> seb128, except g-i-t contains a (manual?) list of missing icons
[09:53] <seb128> darkxst, can't we transition that list to a-i-t?
[09:54] <mlankhorst> willcooke: ok :P
[09:56] <darkxst> seb128, sure, but you still need to work out the missing icons either way
[09:56] <willcooke> mlankhorst, first question - how do I find out what version of Mir I'm running?  I'm using the desktop next image
[09:57] <mlankhorst> apt-cache policy libmirserver.*; look for the installed one
[09:59] <willcooke> ok, I'm on 0.8, so that's job #1
[09:59] <mlankhorst> the archive has the correct versions
[10:00]  * willcooke upgrades
[10:00] <willcooke> mlankhorst, and then I use your PPA from LP?  https://launchpad.net/~mlankhorst/+archive/ubuntu/ppa
[10:00] <mlankhorst> yeah
[10:00] <willcooke> cool, thanks mlankhorst
[10:00] <mlankhorst> install mir-demos after updating
[10:00] <willcooke> kk
[10:02] <mlankhorst> after that and installing xserver-xorg-xmir from the ppa switch to vt1 with ctrl alt f1, log in and: sudo stop lightdm; sudo mir_demo_server_shell & sudo Xmir & .. wait a few seconds then run COMPIZ_CONFIG_PROFILE=ubuntu compiz
[10:04] <willcooke> \o/
[10:04] <willcooke> mlankhorst, is compiz being used here as a benchmark, as a way of poking all the bits of XMir/Mir to find gaps?
[10:05] <mlankhorst> sort of, but in reality it should just spawn a full ubuntu desktop
[10:05] <willcooke> erk:
[10:05] <willcooke> dpkg: cycle found while processing triggers:
[10:05] <willcooke>  chain of packages whose triggers are or may be responsible:
[10:05] <willcooke>   ureadahead -> ureadahead
[10:05] <willcooke>  packages' pending triggers which are or may be unresolvable:
[10:05] <willcooke>   dbus: /etc/dbus-1/system.d
[10:05] <willcooke>   ureadahead: /etc/init.d: /etc/init
[10:05] <willcooke> dpkg: error processing package dbus (--configure):
[10:06] <willcooke>  triggers looping, abandoned
[10:06] <willcooke> dpkg: ../../src/packages.c:226: process_queue: Assertion `dependtry <= 4' failed.
[10:06] <willcooke> E: Sub-process /usr/bin/dpkg exited unexpectedly
[10:06] <mlankhorst> remove ureadahead I guess ?
[10:06] <willcooke> meh - fixed
[10:06] <willcooke> did dpkg --configure -a
[10:06] <mlankhorst> ok
[10:07] <Laney> what were you doing?
[10:07] <willcooke> Laney, apt-get upgrade on my desktop next machine
[10:07] <Laney> vivid to vivid?
[10:07] <willcooke> yeah
[10:07] <Laney> what version of ureadahead?
[10:07] <Laney> apt-cache policy ureadahead
[10:07] <Laney> seb128: (splitting is probably reasonable I guess)
[10:08] <willcooke> ureadahead:
[10:08] <willcooke>   Installed: 0.100.0-16
[10:08] <willcooke>   Candidate: 0.100.0-17
[10:08] <willcooke>   Version table:
[10:08] <willcooke>      0.100.0-17 0
[10:08] <willcooke>         500 http://gb.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
[10:08] <willcooke>  *** 0.100.0-16 0
[10:08] <willcooke>         100 /var/lib/dpkg/status
[10:08] <Laney> yeah I thought so
[10:08] <Laney> https://launchpad.net/ubuntu/+source/ureadahead/0.100.0-17 ;-)
[10:08] <willcooke> :)
[10:09] <Laney> although we may need to SRU that too, I think
[10:09] <mlankhorst> won't that break everyone who has ureadahead installed? :p
[10:09] <Laney> why?
[10:09] <mlankhorst> if they upgrade
[10:10] <Laney> why?
[10:10] <mlankhorst> ironically to fix that bug :P
[10:10] <mlankhorst> dno
[10:10] <willcooke> if they have the "broken" version installed, then in order to install the fixed version, dpkg will bail out first
[10:10] <willcooke> ?
[10:11] <willcooke> (after doing a --configure -a and re-runnng upgrade it's all ok)
[10:12] <Laney> It doesn't happen on every upgrade
[10:12] <Laney> I think we should SRU it though because there's a decent chance release upgrade paths will invoke the old trigger
[10:12] <mlankhorst> ok
[10:13] <Laney> maybe someone could look at that this week (/me nominates the bug)
[10:13] <Laney> otherwise I'll look at it next
[10:13] <Laney> speaking of which, got to go buy a coffee table, laters
[10:14] <Laney> seb128: I think splitting and migrating to a-i-t is probably the way to go btw
[10:14] <Laney> sorry darkxst if we can't keep it in sync, you know it pains me too :'(
[10:14] <seb128> Laney, +1
[10:14] <Laney> bye!
[10:14] <willcooke> cya Laney
[10:14] <seb128> Laney, have fun, see you later
[10:18] <darkxst> Laney, for the sake of a few icons, and a list that still needs to be maintained? seems just as easy to copy them over
[11:13] <didrocks> seb128: if you run nautilus <dir> from the terminal, do you have it appearing behind it?
[12:45] <seb128> didrocks, yes
[12:50] <willcooke> balls.  Run out of space on my machine
[12:53] <willcooke> popey, did you buy a new SDD for your Thinkpad?
[12:54] <popey> not recently
[12:54] <popey> creative have one on offer right now
[12:54]  * willcooke googles
[12:54] <popey> http://uk.crucial.com/gbr/en/store-ssd-factory-recertified?cm_mmc=affiliation-_-null-_-null-_-null
[12:54] <willcooke> thanks popey
[12:54] <popey> i have two in mine
[12:55] <willcooke> blimes - thats cheap
[12:55] <popey> if you want lots of space you could put an mSATA SSA in (I have a 240GB one of those in) and some spinning rust
[12:55] <popey> then you get the best of both worlds
[12:55] <willcooke> I think 240GB will be enough for now (I hope)
[12:55] <popey> yeah, i have 2x240 in mine
[12:55] <popey> still run low
[12:55] <popey> <- hoarder
[12:56] <willcooke> is one of those an mSATA?
[12:56] <willcooke> yes
[12:56] <popey> yes
[12:56] <willcooke> you just said it was, :/
[12:56] <willcooke> sorz
[12:58] <willcooke> hm - it says that disk isnt compatible with my X220
[12:59]  * willcooke remembers something about 7mm drives not fitting
[13:00] <willcooke> no, 7mm drives should fit fine
[13:08] <didrocks> willcooke: those are the ones which fits: http://www.amazon.com/Samsung-830-Series-MZ-7PC256N-Internal/dp/B005T3GPXY
[13:08] <willcooke> 500 USD ?!?!?!?!?!?
[13:09] <didrocks> willcooke: I just picked the one I bought 2 years ago (but it was way cheaper at the time :p)
[13:09] <didrocks> willcooke: at least, you can have the correct size now
[13:09] <willcooke> :)
[13:09] <willcooke> thx didrocks
[13:09] <didrocks> yw
[13:10] <didrocks> I remember having spent some times as well on the size to ensure it's fitting the x220 :)
[13:11]  * didrocks goes for a run
[13:49] <pitti> didrocks: hah, j'ai vu la premie`re episode de Doctor Who :)
[13:49] <pitti> ou -- le docteur qui :)
[13:53] <Trevinho> ricotz: hi, why mir support in xorg edgers mesa is disabled? It doesn't look to fail here (patch and compilation)...
[13:54] <ricotz> Trevinho, hi, historical reason to avoind maintaining this patch
[13:54] <Trevinho> ricotz: isn't it quite stable now?
[13:55] <ricotz> Trevinho, not sure, i am not very fond about mir
[13:56] <ricotz> will try to enable it again next time
[13:56] <Trevinho> thanks
[14:21] <desrt> Laney: you (temporarily?) assigned a bug to me... was that a mistake?
[14:24] <larsu> desrt: morning :)
[14:24] <desrt> good morning
[14:25] <larsu> remember your PrimaryConnectionType thing? Looks like it's not being used
[14:26] <desrt> ya.  someone closed my bug on the dash as 'opinion'
[14:26] <didrocks> pitti: oh? from the new series I guess, did you like it?
[14:27] <desrt> as in, it's only my opinion that doing 400 dbus calls and a bunch of signal subscriptsions to bring up an entire network manager tree worth of devices and monitor it in order to determine a single boolean value is overkill
[14:27] <pitti> didrocks: yes, and yes I did :)
[14:27] <larsu> desrt: bug #1386109 ?
[14:27] <didrocks> pitti: sweet! You will see, it's getting better and better (especially after the 6th episod)
[14:27] <larsu> desrt: there's a new thing called com.ubuntu.connectivity1...
[14:27] <desrt> fwiw, i think the property added to NM is wrong
[14:27] <larsu> supplied by indicator-network
[14:27] <desrt> i don't know if the connectivity thing is right
[14:28] <desrt> but they're not using that either :(
[14:28] <larsu> and according to that bug, it always tells apps its online
[14:28] <larsu> desrt: why?
[14:28] <desrt> they're treating the issue as strictly a qt bug
[14:28] <desrt> ie: fix the race/deadlock in qt and the problem is 'solved'
[14:28] <desrt> fine by me.... *shrug*
[14:29] <desrt> fwiw, though, i think my patch in NM is bogus
[14:29] <desrt> i should maybe discuss that with dcbw
[14:29] <larsu> why?
[14:29] <desrt> i found out something really neat the other day: android sends a field in its dhcp reply to people who tether: ANDROID_METERED
[14:29] <larsu> if you fix the deadlock in qt, you still have the dash talking to nm directly
[14:29] <larsu> rendering all of indicator-network pointless
[14:30] <desrt> ie: treating a "802-11-wireless" or whatever device type as being "not on 3g" is a bad heuristic
[14:30] <desrt> since we have more information -- we're just not using it
[14:31] <larsu> desrt: that is _seriously_ nice. `apt-get update` ran in the background and used my monthly data allowence the other day
[14:31] <desrt> i'm gonna file the upstream NM bug now, in fact
[14:31]  * desrt noticed that field in debugging output of NM the other day while hacking bluetooth stuff
[14:31] <larsu> what kind of property do you propose?
[14:31] <larsu> ConnectedToSomethingFast?
[14:32] <desrt> IsMetered? 
[14:32] <larsu> not every 3g connection is metered...
[14:32] <desrt> well that's android's problem
[14:32] <desrt> i don't know why my phone sends ANDROID_METERED
[14:33] <larsu> but ya, that's a much better heuristic than is-wifi?
[14:33] <desrt> maybe there is a switch somewhere to control that
[14:33] <desrt> since i have an unlimited plan...
[14:33] <larsu> it's definitely very cool
[14:33] <desrt> (although, strictly speaking it is metered.... they slow me down after 10GB of usage)
[14:33] <desrt> so probably i still prefer that it doesn't do updates...
[14:33] <larsu> desrt: there's a setting for warning you once you cross some treshold
[14:33] <larsu> *threshold
[14:40] <desrt> https://bugzilla.gnome.org/show_bug.cgi?id=740982
[14:40] <desrt> i heard some crackrock about building a list of known wifi mac addresses of phones in order to deal with this problem
[14:40] <desrt> this is clearly going to be a better approach....
[14:40] <larsu> wouldn't that be kind of a big list.......
[15:08] <cyphermox> seb128: hey
[15:09] <desrt> cyphermox: remember that primaryconnectiontype property?  starting to have second thoughts there....
[15:09] <desrt> and apparently nobody in ubuntu will use it anyway...
[15:10] <desrt> i just filed #740982 upstream -- let's see how that goes.... but maybe it's worth dropping that patch in ubuntu
[15:10] <seb128> cyphermox, hey
[15:12] <cyphermox> seb128: can I subscribe desktop team (or desktop-bugs?) to the new build-depends from NM?  it's libteam, libndp, and jansson for their MIRs
[15:13] <seb128> cyphermox, desktop-bugs yes
[15:13] <cyphermox> seb128: ack
[15:13] <seb128> that's the team we use for packages bugs
[15:14] <cyphermox> oops
[15:14] <cyphermox> seems I don't have that kind of access
[15:15] <seb128> cyphermox, done it for you
[15:15] <cyphermox> seb128: thanks
[15:16] <seb128> yw
[16:32] <seb128> dpm, pitti, hey, vivid translations are open/active, who can/should enable the langpack cron job?
[16:35] <dpm> seb128, I generally ping wgrant to enable the exports, and then pitti sets up the langpacks
[16:36] <seb128> dpm, let me ping wgrant then ;-)
[16:37] <seb128> dpm, or do you know where to check if those are already enabled?
[16:44] <didrocks> seb128: do you know what is used nowdays for mime types association, I don't see mimeapps.list anymore
[16:45] <seb128> didrocks, you mean?
[16:45] <didrocks> seb128: IIRC in the past (but didn't check since 2010), mime types association were defined in a mimeapps.list file
[16:46] <didrocks> (which was compiled from the available apps)
[16:46] <seb128> didrocks, /usr/share/applications/defaults;list
[16:46] <seb128> .list
[16:46] <seb128> if you mean our default list
[16:46] <seb128> or do you mean user ones?
[16:46] <didrocks> oh right, that one
[16:46] <didrocks> thanks seb128 :)
[16:46] <seb128> yw
[16:47] <seb128> didrocks, user config is ~/.local/share/applications/mimeapps.list though
[16:47] <seb128> those are changes over the defaults
[16:47] <didrocks> seb128: yeah, hence the confusion :)
[16:47] <seb128> with added/removed sections
[16:48] <seb128> dpm, I guess it's on https://translations.launchpad.net/ubuntu/vivid/+language-packs ?
[16:51] <dpm> seb128, sorry, I was otp. Yeah. Generally I keep the schedule here and I file an RT to get the exports going: https://dev.launchpad.net/Translations/LanguagePackSchedule
[16:52] <seb128> dpm, thanks, I pinged wgrant on #ubuntu-devel, I can file a rt if you want/that's preferred though
[16:53] <dpm> seb128, if pinging works, that works well for me
[16:53] <seb128> let's see what he replies
[16:54] <dpm> I guess we cannot drop any released off the schedule, so we should probably do the exports on the Friday
[16:55] <dpm> or actually on the Tuesday and move the utopic ones around
[17:40] <pitti> dpm: making a note, I'll build them tomorrow
[18:08] <dpm> pitti, yeah, let's sync up to see if we can get the exports on the schedule first
[18:20]  * willcooke_ -> EOD.
[18:20] <willcooke_> o/
[19:32] <Laney> desrt: I assigned that to the canonical-desktop-team, you probably got mailed through that
[19:32] <desrt> ahh
[19:32] <desrt> launchpad writes bad email :)
[20:37] <popey> seb128: would you say bug 1298297 is assigned to the right place?
[20:37] <popey> or is it in fact unity as ali1234 suggests?
[20:37] <ali1234> it's both really
[20:38] <ali1234> i mean they both want to lock the screen
[20:38] <ali1234> you;re presumably disabling the unity lock screen but the lightdm one is still there, and you no longer have a control panel for it
[20:38] <ali1234> we had this exact same problem in xubuntu with lightdm + light-locker
[21:06] <seb128> popey, ali1234, is that still an issue? it's likely unity-settings-daemon and a bug like that was fixed on friday
[21:06] <ali1234> no idea, i use xubuntu...
[21:08] <seb128> well, by default logind/systemd suspend on lid close
[21:08] <seb128> then it's up to something to set an inhibitor
[21:08] <seb128> in unity/gnome it's unity/gnome-settings-daemon
[21:08] <seb128> not sure in xubuntu
[21:09] <seb128> then the locking is up to e.g unity/gnome-screensaver
[21:09] <ali1234> yes in xubuntu we had to add a patch to inhibit logind
[21:09] <larsu> add a patch to what?
[21:09] <ali1234> to light-locker
[21:10] <ali1234> bug 1303736
[21:10] <ali1234> actually i think it was patched in xfce4-power-manager
[21:12] <ochosi> yup, it was xfpm
[21:14] <popey> seb128: fixed already? yay!
[21:18] <seb128> popey, well, feel free to test/confirm if the fix works
[21:28] <larsu> seb128: any known bugs about mouse input events not being sent to apps?
[21:28]  * larsu is just seeing that...
[21:29] <larsu> anything in the shell works (launcher, dash, panel), but not in the windows itself. window management doesn't work either
[22:04] <seb128> larsu, not that I know no
[23:25] <WhiteIntel> Hello can anyone tel mel a remote desktop solution that is working out of the box with user session handling, good performance, easy to install?
[23:43] <RAOF> WhiteIntel: AFAIK, ‘Desktop Sharing Preferences’ is installed by default, works, and is reasonable.
[23:43] <RAOF> WhiteIntel: Together with ‘Remote desktop viewer’ (aka vinagre)