[04:55] <hikiko> Hi
[05:44] <pitti> Good morning
[05:45] <pitti> seb128, Laney: I simply ran out of time on Friday when I reviewed the SRU queue :)
[05:45] <seb128> good morning pitti!
[05:45] <pitti> Good morning
[05:45] <seb128> & desktopers
[05:45] <seb128> how are you?
[05:45] <pitti> quite fine, thanks! had a swap day yesterday, and met StevenK
[05:46] <pitti> we did a tour through Augsburg, and went to Munich in the afternoon to pick up my wife from work, see the English Garden, and have Bavarian dinner
[05:48] <sarnold> schnitzel? pig knuckles? thuriginer klosse? :)
[05:48] <seb128> ah, nice!
[05:48] <sarnold> welcome back pitti :) I hope travel was alright?
[05:48] <seb128> what is StevenK doing around there? holidays?
[05:49] <pitti> sarnold: yes, uneventful and on time indeed, thanks! and I mostly figured out now how to deal with jetlag
[05:49] <sarnold> pitti: nice all around :)
[05:49] <pitti> seb128: yeah, his mother, sister, and him do some kind of Europe tour right now
[05:49] <seb128> nice
[05:49] <pitti> seb128: and they stay in Munich for a week
[05:49] <pitti> sarnold: absolutely; it was a nice sprint too
[05:49] <seb128> you still have summer there btw?
[05:52] <pitti> seb128: not really, it has been grey and a bit rainy since yesterday :/
[05:53] <seb128> same here :-/
[05:53] <pitti> I hope it gets better for the weekend, we want to do a rafting tour on Sunday
[06:27] <desrt> good morning desktop!
[06:31] <pitti> heeey desrt!
[06:33] <desrt> hello pitti
[06:33] <desrt> another beautiful day here :)
[06:42] <seb128> hey desrt! how are you?
[06:42] <desrt> good... doing some morning cleaning :)
[06:42]  * desrt is switching from debfoster to apt-mark
[06:42] <seb128> flexiondotorg, bug #1580382 seems like one for you ("topmenu-gtk" issue)
[06:43] <seb128> flexiondotorg, I'm just pointing it out in case, unsure if that watch that source but all the reports seem to come from your flavor
[06:48] <desrt> desrt@humber:~$ apt-mark showmanual | wc -l
[06:48] <desrt> 46
[06:49] <desrt> shiny
[06:51] <seb128> happyaron, hey, could you get a SRU/update ready for bug #1574347 (on top of the current one so we can upload once the first one goes to -updates)
[07:03] <happyaron> seb128: work on that today
[07:03] <seb128> happyaron, thanks!
[07:29] <happyaron> seb128: have time to sponsor -openconnect? https://launchpad.net/~happyaron/+archive/ubuntu/ppa/+sourcepub/6404038/+listing-archive-extra
[08:03] <Laney> morning!
[08:05] <willcooke> morning Laney
[08:06] <Laney> what ho
[08:06] <willcooke> 'tis misty today, almost foggy
[08:08] <Laney> pretty gruesome here
[08:09] <willcooke> Rained all day yesterday, but still warm.  Good for the plants thogh
[08:09] <willcooke> though
[08:09] <willcooke> The allotment will need some weeding I expect :)
[08:10] <Laney> hoe hoe hoe
[08:10] <willcooke> \o/
[08:11] <Laney> the other day I made a contraption to water underneath the cloches
[08:11] <Laney> wonder if that's working
[08:11] <seb128> happyaron, yes, on my list for this morning
[08:11] <seb128> hey Laney willcooke
[08:11] <Laney> yo seb128
[08:11] <Laney> what up gangsta
[08:12] <seb128> I started fresh and early today, was there for pitti's "good morning"!
[08:12] <Laney> that's exciting
[08:12] <seb128> and just back from getting some coffee
[08:12] <pitti> hey Laney, good morning!
[08:12] <seb128> which was welcome after email catchups
[08:12] <seb128> what about you?
[08:18] <Laney> hi pitti!
[08:19] <Laney> I'm good thanks
[08:19] <Laney> managed to dodge the rain yesterday while on the bike
[08:20] <seb128> :-)
[08:52] <seb128> pitti, remember that usd/upower segfault?
[08:52] <pitti> seb128: I do, yes; on lid closing?
[08:52] <seb128> yes
[08:52] <seb128> that's a simple code reproducer
[08:52] <seb128> 	UpClient *client = NULL;
[08:52] <seb128> 	client = up_client_new ();
[08:52] <seb128> 	printf("lid is closed? %d\n", up_client_get_lid_is_closed (client));
[08:52] <seb128> do that with upower down
[08:52] <seb128> -> segfault
[08:52] <seb128> I moved the upowerd binary here for testing
[08:52] <seb128> but some of the reports have upower taking up to a minute to start
[08:53] <seb128> which I guess is some lower stack issues
[08:54] <pitti> seb128: ah, so this crash comes even before the point when it would crash on a nonexisting lid object? or does it somehow handle that without crashing then?
[08:54] <pitti> so I guess calling up_client_something() lazily does the dbus connection, it's not up_client_new()? or does that return NULL?
[08:54] <pitti> (as client != NULL in the stack trace that I saw)
[08:54] <seb128> the stacktrace might be a different issue
[08:55] <seb128> I get a segfault with the code I just copied
[08:55] <seb128> up_client_new() hang for a while
[08:55] <seb128> then give a dbus timeout warning
[08:55] <seb128> and code goes on
[08:55] <seb128> and up_client_get_lid_is_closed() segfaults
[08:55] <pitti> seb128: what's the value of client? some object or NULL?
[08:55] <seb128> let me check the value, I think it was not null
[08:56] <pitti> that'd be sad indeed
[08:56] <pitti> if up_client_new() does block and shows a timeout, then it already does the connection and ought to return NULL
[08:56] <pitti> if not, we surely need to fix that
[08:56] <pitti> but I have a feeling that's not the whole story with the lid close crash yet
[08:57] <seb128> no, it's not
[08:57] <seb128> #0  0xb7f797ed in up_exported_daemon_get_lid_is_closed (object=0x0)
[08:57] <seb128>     at up-daemon-generated.c:747
[08:57] <seb128> #1  0xb7f7417d in up_client_get_lid_is_closed (client=0x8053f08 [UpClient])
[08:57] <seb128>     at up-client.c:208
[08:57] <seb128> #2  0x080485f6 in main (argc=1, argv=0xbfffef34) at upower.c:8
[08:57] <seb128> so client != NULL
[08:57] <pitti> eww
[08:57] <seb128> so up_client_new() returns a non null value
[08:58] <pitti> seb128: do you mind filing a bug about that on fd.o? will look at it ASAP
[08:58] <seb128> doing
[08:58] <seb128> thanks
[08:58] <pitti> so with that, the lid was either a red herring, and those reporters have a slow-starting upower
[08:58] <seb128> right
[08:58] <seb128> which makes more sense
[08:58] <pitti> or upower does start, and the lib later crashes on the nonexisting lid object
[08:58] <seb128> because u-s-d code didn't change since trusty
[08:59] <seb128> there were a few comments on the bug from people who say that upower is slow to start
[08:59] <pitti> as it doesn't check if a lid is present
[08:59] <pitti> seb128: interesting; so ideally it's just that then :)
[08:59] <seb128> yeah
[08:59] <pitti> let's see what they say once we have a -proposed package
[09:07] <seb128> pitti, https://bugs.freedesktop.org/show_bug.cgi?id=95350
[09:08] <pitti> seb128: merci !
[09:08] <seb128> pitti, let me know if you need more debug info, I'm locally testing with a systemctl stop upower/moving the binary away to avoid dbus activation, then using the test code
[09:08] <seb128> de rien !
[09:12] <seb128> pitti, some of the comments state e.G
[09:12] <seb128> "You'll know if the system is hit with this as it'll be much slower to boot and the kernel will spew errors of the type:
[09:12] <seb128> kernel: usb 2-1.1: device descriptor read/64, error -110
[09:12] <seb128> kernel: usb 2-1-port1: unable to enumerate USB device"
[09:12] <seb128> so I guess part of those are also kernel issues
[09:12] <seb128> those users say boot is slow
[09:12] <seb128> but I guess that should be reported separately as a kernel bug
[09:12] <pitti> ack
[10:08] <Laney> pitti: seb128: do you want to reschedule that meeting about de-upstartification?
[10:09] <pitti> Laney: yeah, let's; I still don't have a good idea about how the user session is plumbed together these days, so let's at least exchange some braindump and see how to go on
[10:10] <pitti> Laney, seb128, tedg: would tomorrow afternoon (EU)/morning (US) work for you?
[10:10] <pitti> xnox: ^
[10:11] <pitti> we have the foundations meeting at 1500 UTC, before that would be good
[10:11] <xnox> that.
[10:11] <Laney> pitti: I heard that systemd --user isn't really that ready yet though, so it sounds like this either means going back to gnome-session / xdg autostart /or/ taking on the systemd work
[10:11] <Laney> desrt: ^^^
[10:11] <desrt> talking about dropping upstart in the user session?
[10:11] <Laney> yeah
[10:12] <pitti> Laney: it indeed doesn't replace upstart --session directly, it's aiming for services that apply to all running user sessions indeed
[10:12] <xnox> Laney, so, there are github repositories with user session units and systemd generators for xdg autostart things
[10:12] <desrt> systemd --user _is_ a reality
[10:12] <desrt> but it doesn't do all of the things that we might expect of it
[10:12] <pitti> there's no systemd user instance per session indeed
[10:12] <xnox> and it does work, however lenart didn't take any units like that upstream.
[10:12] <desrt> debian is running systemd --user already
[10:12]  * pitti has dbus-user-session installed for two weeks now, finding a few small issues but it by and large works
[10:12] <xnox> so do we.
[10:12] <Laney> well anyway, I don't know that much about it
[10:12] <desrt> but as a gnome-session replacement?  not even close...
[10:12] <xnox> but it's per user instance, not per user-session.
[10:12] <pitti> such as https://bugzilla.gnome.org/show_bug.cgi?id=759115
[10:12] <pitti> desrt: agreed
[10:13] <Laney> so if someone wants to exchange their information to me/us that would be helpful
[10:13] <desrt> i think we should do what debian is doing
[10:13] <pitti> desrt: AFAIK they just use gnome-session and dbus activation
[10:13] <pitti> but we moved from that to upstart --user
[10:13] <pitti> and I'd like to understand the advantages that we got from that, and whether they justify maintaining upstart further
[10:14] <pitti> as nobody is doing that ^ right now
[10:14] <desrt> is there some benefit to having processes started from upstart instead of dbus-daemon?
[10:14] <pitti> (and don't look at me, maintaining one init system / ubuntu boot is enough for one person :) )
[10:14] <desrt> the answer to this is surely "yes, but they're pretty minimal."
[10:14] <pitti> I see no benefit for real services, as they just get auto-activated
[10:14] <pitti> it might be for things like indicators
[10:14] <pitti> as with upstart user you can set them to auto-restart after crashes
[10:14] <desrt> and this is where you were discussing xdg-autostart...
[10:15] <pitti> and IIRC xdg-autostart/gnome-session don't have an autorestart thingy
[10:15] <pitti> desrt: do you have time tomorrow around 14:00 UTC to join a hangout?
[10:16] <Laney> and then what of phone?
[10:16] <desrt> i will probably be on ICE
[10:16] <pitti> Laney: oh, no gnome-session there?
[10:16] <desrt> let me check
[10:16] <Laney> nope
[10:16] <pitti> Laney: although on a phone we could actually use systemd --user, as realistically there's only ever one session anyway?
[10:17] <Laney> I should have said unity8/mir
[10:17] <desrt> pitti: in fact, i'll be inside of a plane
[10:18] <pitti> is this afternoon any better?
[10:18] <desrt> yes.  it would be fine.
[10:19] <pitti> seb128, xnox, Laney: ^ what about you this afternoon?
[10:20] <Laney> sure
[10:20] <Laney> you might want stgraber or slangasek for a discussion of the initial motivation
[10:21] <pitti> ok, I'll invite them
[10:21] <xnox> or jodh
[10:21] <Laney> heh
[10:24] <pitti> I sent invites, please feel free to move the thing around
[10:25] <desrt> pitti: 3pm?
[10:26] <Laney> it says 3pm here too
[10:26] <pitti> desrt: too earl?
[10:26] <Laney> maybe set a timezone and it'll fix it
[10:26] <Laney> wait
[10:26] <pitti> it was an initial approxmiation of "afternoon/East coast morning"
[10:26] <Laney> I think my calendar is still on prague time
[10:26]  * Laney looks
[10:26] <pitti> I meant it to be at 15:00 CEST/13:00 UCT
[10:26] <pitti> but later WFM too
[10:27] <Laney> ya
[10:27] <Laney> my bad
[10:27] <Laney> I did wonder when a meeting earlier this week happened an hour before I thought it would
[10:27] <Laney> should have been suspicious then :)
[10:27] <pitti> time zones FTW
[10:30] <desrt> somehow timezones always manage to be completely screwed for everything
[10:30] <desrt> email and the web should have a widget that allow displaying a unix-epoch-based timestamp in whatever timezone the rendering machine is currently in
[10:31] <desrt> (without allowing arbitrary javascript from email to run in my browser)
[10:31] <pitti> not sure how many people would be *less* confused by "let's meet at 1462962700"
[10:32] <desrt> you wouldn't actually see that....
[10:33] <Laney> the tech ctte does this:
[10:33] <Laney> Subject: Next Debian CTTE Meeting is at date -d 'Tue May 31 17:00:00 UTC 2016'
[10:33] <pitti> hah, nice
[10:33] <desrt> ya.. i basically want a form of this that is capable of rendering itself
[10:34] <pitti> shell injection in email Subject: :)
[11:43] <willcooke> Laney,seb128  "standing excemption for snappy etc" trello card is marked as done - is it really done?
[11:44] <seb128> ah, thanks for the reminder
[11:44] <seb128> I commented about that yesterday but I think after Laney left
[11:44] <seb128> then I closed IRC so didn't see potential replies
[11:45] <seb128> desrt, pitti, Laney, systemd-session meeting wfm
[11:45] <Laney> isn't it about feature freeze?
[11:45] <seb128> Laney, it's about SRU exception
[11:45] <seb128> like being able to SRU new versions
[11:45] <Laney> ok then move it back
[11:45] <seb128> even if they include features and such
[11:45] <seb128> k, thanks
[11:45] <seb128> willcooke, ^
[11:45] <Laney> I've not heard those things called standing exemptions before
[11:45] <Laney> that is a term used for feature freeze exceptions
[11:46] <willcooke> tomato, tomato.  What should it be called?
[11:46] <willcooke> or maybe its not even a thing?
[11:47] <seb128> dunno if there is an official namez
[11:47] <seb128> well
[11:47] <seb128> https://wiki.ubuntu.com/StableReleaseUpdates#Documentation_for_Special_Cases
[11:47] <seb128> so "SRU special case"
[11:47] <seb128> ?
[11:47] <Laney> or just put a description in
[11:47] <Laney> it doesn't matter to me
[11:48] <willcooke> oki
[11:49] <seb128> Laney, does snappy about a standing FFe btw?
[11:49] <seb128> just curious now, since you put it to done :-)
[11:49] <seb128> does snappy have*
[11:49] <seb128> I guess it's more a by-cycle situation though
[11:50] <Laney> no
[11:50] <Laney> there is no feature freeze
[11:50] <seb128> it's seeded in Ubuntu so for sure it's subject to that feature freeze?
[11:50] <Laney> everything is subject to feature freeze when there is one
[11:50] <seb128> except things that have a ffe :p
[11:50] <Laney> but a previous cycle's exception would no longer apply
[11:50] <seb128> like touch packages have(had?)
[11:51] <Laney> they ask for that every cycle
[11:51] <Laney> but haven't actually for the last two
[11:51] <seb128> k, makes sense I guess
[11:51] <Laney> well they asked but didn't get them
[11:51] <Laney> and it was in fact ok
[11:51] <seb128> yeah, they cheat by using their overlay :p
[11:51] <Laney> mostly by ignoring the development release
[11:51] <Laney> or violating feature freeze
[11:52]  * Laney doesn't read the changes list
[11:52] <Laney> best not to know
[11:52] <seb128> yeah :-/
[12:20] <Laney> tedg: seb128: pitti: xnox: desrt: mind if we make it 13:30 UTC?
[12:20]  * Laney would ideally be AFK at 13:00
[12:20] <pitti> Laney: fine for me, just move it in the calendar?
[12:21] <desrt> Laney: so, in 70 minutes?
[12:21] <Laney> ack
[12:22] <Laney> 70 minutes indeed, thanks - moved
[12:25] <Laney> biab
[12:25] <Laney> telegram me if someone can't make the new time
[12:28] <seb128> Laney, wfm
[12:50] <xnox> Laney, i thought we are meeting at 14:00 british summer time, no?
[12:50] <xnox> oh 14:30 summer time now.
[12:59] <davmor2> xnox: now you put this in my head https://www.youtube.com/watch?v=yG0oBPtyNb0
[13:01] <xnox> davmor2, whoop whoop =)
[13:01]  * xnox swings his hips
[13:27] <andyrock> morning all
[13:28] <seb128> hey andyrock! how are you?
[13:28] <pitti> seb128, Laney, xnox: ready for session in a minute?
[13:29] <seb128> pitti, yes
[13:29] <desrt> pitti: desrt@desrt.ca plz
[13:30] <Laney> pitti: coming
[13:30] <pitti> desrt: invite sent
[13:31] <tjaalton> shouldn't unity pick up newly installed apps automatically?
[13:31] <tjaalton> i mean the search thing
[13:32] <willcooke> tjaalton, https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1506744
[13:32] <tjaalton> ahah .)
[13:32] <tjaalton> :)
[13:32] <seb128> what willcooke said
[13:32] <desrt> pitti: not seeing it :(
[13:32] <willcooke> :)
[13:33] <Laney> oh hangouts
[13:34] <desrt> "Trying to join the call..."
[13:35]  * desrt sighs
[13:35] <Laney> I think pitti has to approve it or something
[13:35]  * Laney switched to canonical account and got straight in
[13:36] <pitti> I /msged him hte URL
[13:36] <Laney> it looked like the hangout owner has to approve external people or something
[14:01] <andyrock> hey seb128 fine just finished swedish class
[14:03] <seb128> andyrock, hey :-)
[14:24] <pitti> xnox: ideally we could make these services hang off session-c2.scope (the session specific logind "master unit"), then the lifecycle on logout would happen automatically
[14:24] <pitti> xnox: and I think we have to, as you can't guarantee that you run shutdown code in the session itself (kill -9/crash/etc.)
[14:26] <xnox> hm.
[14:26] <xnox> pitti, but session-c2.scope is system, not user one....
[14:26] <xnox> or can user units be part of system scope?
[14:26] <xnox> i guess they must?!
[14:27] <Laney> look at systemd-cgls
[14:27] <pitti> xnox: not with the "classical" /user session ones
[14:27] <pitti> xnox: but the logind scope is the one that is supposed to group all the processes that actually run in your session, so the lifetime of that is exactly what we want
[14:28] <pitti> this is where it gets fuzzy and where I'd like to confer with the dbus and systemd upstream people
[14:28] <xnox> Laney, pitti - e.g. /lib/systemd/systemd --user is not in a session-c2.scope, it's user-wide.
[14:28] <Laney> how do you get systemd to put things in that scope?
[14:28] <Laney> indeed
[14:28] <pitti> there's another option, though
[14:28] <xnox> use system units, templates per-user?!
[14:28] <pitti> we can run the units as part of user@1000.service, and bind them to session*.scope
[14:29] <pitti> so that they go down with the session
[14:29]  * pitti needs to test that
[14:29] <xnox> will those have DISPLAY?
[14:29] <xnox> or does display need to be fetched from the session?
[14:29] <pitti> xnox: user units do, yes
[14:29] <pitti> I don't want to use system units for user session stuff, that'd be conceptually wrong and also dangerous
[14:30] <pitti> and you can't make them start as the correct user
[14:44] <seb128> hum, does somebody what part we were cleaning with snapcraft to avoid redownloading the debs?
[14:45] <seb128> popey, ^
[14:45] <seb128> like to rebuild after the wrapper changes
[14:47] <seb128> ha
[14:47] <seb128> "build"
[14:47] <Laney> desrt / larsu / darkxst: do you recommend fastmail?
[14:47] <desrt> yes-ish
[14:47]  * Laney is de-neckbearding
[14:48] <desrt> it's not awesome, but i don't know of anything better
[14:48] <larsu> yes, it's pretty good
[14:48] <seb128> arg, no -:/ that cleaned the deb cache as well
[14:49] <larsu> greg was saying that they rate limit him sometimes
[14:49] <seb128> or not, it's only redownloading the index
[14:49] <larsu> but I assume you don't send that much email ;)
[14:49] <seb128> larsu, "him"?
[14:49] <seb128> larsu, oh, and hey :-)
[14:49] <larsu> seb128: greg
[14:49] <larsu> hi seb128!
[14:49]  * desrt guesses that greg uses fastmail as a smarthost for git patch mailings
[14:50] <larsu> ya
[14:50] <larsu> 500 at a time :)
[14:50]  * Laney wondered which greg but gets it now
[14:50] <desrt> few people have a legitimate need to send 500 emails in a go :)
[14:50] <seb128> lol, sorry I did skip over the "grep" at the stat of the line for some reason :p
[14:50] <seb128> oh, no
[14:50] <seb128> I read that as "grep" :p
[14:50] <seb128> though you were grepping logs
[14:50] <Laney> grep greg log.txt
[14:50] <seb128> :-)
[14:51] <desrt> i'm naming my kid grep
[14:51] <larsu> Hahhahahah
[14:51] <desrt> this is not going to cause any confusion or misspelling at all
[14:52] <Laney> alright, migrating off this shit is my weekend project
[14:53] <Laney> laney@cripps> wc -l .procmailrc                                                                                                                                                                     ~
[14:53] <Laney> 351 .procmailrc
[14:53] <Laney> and porting that to sieve is going to be fun
[14:53] <Sweet5hark> grep sure will marry lil bobby tables one day...
[14:53] <desrt> Laney: i bet there is a tool for that
[14:54] <seb128> Laney, just curious what's the motivation behind?
[14:55] <Laney> too much spam
[14:55] <Laney> and a few times I have ruined everything and made emails bounce
[14:55] <Laney> like the times the disk on the server got full
[14:55] <seb128> :-/
[14:55] <Laney> or the times that dspam crashed
[14:55] <Laney> which makes mail get rejected
[14:55] <Laney> So Good
[14:56] <Laney> it's a really boring problem to have to solve
[14:56] <seb128> yeah :-/
[14:57] <Laney> and if my server is no longer doing email then I might actually upgrade it off wheezy /o\
[14:59] <popey> seb128: i installed apt-cacher-ng in the end
[14:59] <popey> but snapcraft clean <partname>
[14:59] <seb128> popey, right, I remembered, "pull" is the part I don't want to clean, so doing a "clean build" works fine
[15:01] <popey> oooh
[15:01] <popey> learned something today
[15:01] <popey> thanks
[15:19] <seb128> popey, yw!
[15:32] <seb128> pitti, how does the systemd suspend delay inhibit thing works? is it up to the processes to say when they are done/let the system suspend?
[15:33] <pitti> seb128: yes, as otherwise you can't predict when they are done with whatever they need to do before suspend
[15:34] <pitti> https://www.freedesktop.org/wiki/Software/systemd/inhibit/
[15:34] <seb128> pitti, k, I'm looking a bit a bug #1574120, my guess is that one of the process has to no give the lock back ... I wonder if a "sleep 10; systemd-inhibit" call would tell us which one, just asked on the bug
[15:34] <pitti> seb128: the process tells that it's done by closing an fd that you got from the Inhibit() call (so taht the inhibitor goes away when the process crashes)
[15:34] <seb128> k
[15:35] <seb128> so if one process is misbehaving it could make suspend not happen
[15:35] <seb128> though why it work when selecting directly the item then?
[15:36] <seb128> also InhibitDelayMaxSec defaults to 5s
[15:36] <seb128> that's probably not it :-/
[15:36] <pitti> seb128: it might mis-detect that there is an external monitor?
[15:37] <pitti> suspend only happens with the internal monitor, if you have an external one or docked lid close doesnt' do anything
[15:37] <pitti> (on purpose)
[15:37] <seb128> pitti, is there any command that would tall that? there is no multimonitor suspend lock from u-s-d and xrandr doesn't list one
[15:37] <seb128> unsure how to poke the systemd state though
[15:38] <seb128> or how systemd check if there is one
[15:38] <pitti> seb128: this isn't done via delays, but via  blocks
[15:38] <pitti> some of the submitters have a block, but not all of them AFAIR
[15:38] <seb128> pitti, right, but https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/comments/38
[15:38] <seb128> that's the one I 'm looking at
[15:38] <seb128> there is no block
[15:39] <pitti> so it could be that logind itself detects an external monitor and doesn't suspend by default
[15:39] <seb128> right
[15:39] <seb128> how would one tell if that's the case?
[15:39] <seb128> do you know where systemd would look to tell if there is an external monitor?
[15:42] <pitti> seb128: /sys/class/drm/ basically
[15:43] <pitti> it removes the first cardN-, then  checks
[15:43] <pitti>                 FOREACH_STRING(i, "VGA-", "DVI-I-", "DVI-D-", "DVI-A-"
[15:43] <pitti>                                "Composite-", "SVIDEO-", "Component-",
[15:43] <pitti>                                "DIN-", "DP-", "HDMI-A-", "HDMI-B-", "TV-") {
[15:43] <pitti>                         if (startswith(dash, i)) {
[15:43] <pitti>                                 external = true;
[15:44] <pitti> seb128: enabling debug (systemd-analyze set-log-level debug) and then closing the lid should show that
[15:44] <seb128> pitti, thanks
[15:44] <pitti>                 log_debug("System is docked.");
[15:44] <pitti>                 log_debug("External (%i) displays connected.", n);
[15:44] <pitti> seb128: so an ls of /sys/class/drm plus debug output would be insightful
[15:48] <seb128> pitti, thanks, asked that on the bug
[17:07] <Laney> night!
[17:07] <willcooke> see ya Laney
[17:09] <seb128> night Laney
[17:09] <willcooke> dinner. bbl
[17:11] <seb128> pitti, waiting for the systemd debug but drm has "card0 card0-LVDS-1 controlD64 ttm" and only the one is "enabled"
[18:37] <seb128> pitti, he added a journalctl | grep systemd log on https://launchpadlibrarian.net/259010581/somekindoflog.log
[18:38] <seb128> there are lid closed/opened event without anything printed in between :-/
[19:53] <willcooke> night all
[22:27] <robert_ancell> ximion1, hi
[22:30] <ximion> robert_ancell: hi!
[22:30] <robert_ancell> ximion, been hacking on paid app support for G-S. Do you see this as something that should be in appstream?
[22:31] <robert_ancell> ximion, It mostly requires attaching a price to an app. This wouldn't be added in the appstream file in the source, but in the service that compiles these together.
[22:31] <ximion> robert_ancell: depends... What kind of metadata would you need?
[22:32]  * robert_ancell struggles for the right terms :)
[22:32] <ximion> jup - problem I see there is that the price can to be changed anymore then, as soon as the metadata is published
[22:32] <ximion> it can only be changed by doing a new release to a different suite
[22:33] <ximion> at least if you're talking about paying for .deb packages
[22:33] <ximion> if there is a different system providing the metadata, it could of course be updated more frequently
[22:33] <robert_ancell> Yes, and it probably should because getting old prices is bad
[22:33]  * ximion isn't against adding a <price currency="eur">10</price> tag to metainfo and distro-metadata files
[22:34] <robert_ancell> that's basically it.
[22:34] <robert_ancell> and perhaps <allows-donations>true</allows-donations>
[22:35] <robert_ancell> ximion, for snapd it's not appstream so I don't need to solve this right now, but worth thinking about for the future / other projects.
[22:37] <ximion> robert_ancell: yeah, we had that discussion over at #PackageKit regarding Snappy using AppStream
[22:38] <ximion> rejecting it for political reasons will hurt you later, and I honestly think it's a short-sighted bad decision
[22:40] <ximion> robert_ancell: for donations, we already have an URL type which many upstreams use: https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-url
[22:40] <ximion> unfortunately, GS doesn't show this link
[22:40] <ximion> I think the designers or legal teams didn't like it, but I am not sure about the exact reason for that
[22:40] <ximion> (it's basically just another URL)
[22:41] <robert_ancell> right
[22:42] <ximion> I'd like some feedback from hughsie on the price thing...
[22:42] <ximion> at time I think the currency-issue would be a problem
[22:42] <ximion> standardizing it one one currency won't work, but having a huge enum of all the currencies in the world wouldn't cut it either
[22:43] <ximion> worse, we would need to do currency conversion in the SCs
[22:45] <robert_ancell> ximion, in the case of snappy, an app has multiple prices - one for each currency it supports
[22:45] <robert_ancell> snapd suggests which currency you should use (locale + account preferences)
[22:46] <robert_ancell> the currency code is a string using ISO 4217
[22:47] <ximion> sounds reasonable
[22:47] <robert_ancell> If the app didn't have the currency you pay with, the conversion would be done by the payment processor
[22:47] <ximion> this would need to go into metainfo files, so upstreams can set a price
[22:47] <robert_ancell> It would be too hard / dangerous to try and solve this in the UI
[22:48] <ximion> agreed, that was my concern with it
[22:48] <robert_ancell> ximion, well, I don't think upstreams can set a price because you're not going to be able to pay them directly - the money will have to go to a store and then be redistributed to each upstream
[22:48] <robert_ancell> that's where I think the prices would have to be added in the service that compiles the appstream together. i.e. Launchpad in the case of Ubuntu
[22:49] <robert_ancell> And each distribution could offer different prices
[22:49] <ximion> robert_ancell: shouldn't upstream offer a price estimate?
[22:49] <ximion> and would the distributor only ship one price per app?
[22:50] <ximion> s/price/currency-price-combo/
[22:50] <robert_ancell> ximion, well, the upstream could put a price and then the distributor could allow that price through if it had a relationship with the upstream / means of paying
[22:50] <robert_ancell> The downside is you couldn't change the price quickly which is what is required for sales.
[22:51] <robert_ancell> The norm seems to be one price per target market (USD/EUR etc)
[22:52] <ximion> robert_ancell: well, appstream-generator always treats the metainfo file as suggestion, not as the final word ;-)
[22:52] <robert_ancell> ok, good
[22:53] <robert_ancell> yeah, it would probably make sense for upstream to start the price there (though the docs would need to be appropriately worded as to what exactly that means)
[22:53] <ximion> robert_ancell: since frozen/released suites can't get new AppStream data, that would mean all stuff in there would have a fixed price
[22:53] <ximion> (unchangeable even)
[22:53] <robert_ancell> that's the downside of appstream...
[22:53] <robert_ancell> it's less streamy than the name suggests
[22:54] <ximion> well, that's more a property of the distro release process
[22:54] <ximion> technically, updating the data would be no problem :)
[22:54] <robert_ancell> ximion, so the appstream data could be changed for released distros
[22:54] <robert_ancell> Might not be very efficient if it constantly changes though
[22:55] <ximion> it *could* but since Launchpad doesn't allow any changes for released suites, this won't work
[22:55] <ximion> but if they payed apps are in a different repo, that would work
[22:55] <ximion> and I think this is what will happen, right?
[22:56] <robert_ancell> ximion, we're only supporting snaps but yeah, the old paid .deb support was in separate repos
[22:56] <ximion> I think that would be no problem then
[22:56] <ximion> hmm, I wonder if asgen would allow a Snappy backend...
[22:58] <ximion> it was designed for distro packages, but backends actually don't do much - they emit file lists and some basic package metadata