[05:24] <pitti> Good morning
[06:04] <didrocks> good morning
[06:11] <seb128> lut didrocks & desktopers
[06:12] <didrocks> re seb128 :)
[06:16] <seb128> didrocks, bug #1437633 might be something for you
[06:17] <pitti> bonjour didrocks et seb128 ! avez-vous eu un bon week-end ?
[06:17] <seb128> hey pitti, wie gehts?
[06:17] <seb128> w.e was ok, assembling fournitures for the most parts and it has been windy and rainy
[06:17] <didrocks> seb128: hum, are you sure? it's on the device
[06:18] <didrocks> seb128: it doesn't use, oh wait!
[06:18] <didrocks> yeah
[06:18] <seb128> didrocks, no, but you changed how the status is stored iirc?
[06:18] <didrocks> or not… shuoldn't be…
[06:18] <didrocks> seb128: right, but they aren't using vivid
[06:18] <didrocks> so no vivid whoopsie-preferences/whoopsie
[06:18] <pitti> seb128: gut, danke! we had a nice concert on Saturday, Sting and Paul Simon
[06:18] <didrocks> seb128: or they backported one of those to rtm and not the other?
[06:19] <pitti> and I took some time to brush up our holiday photos
[06:19] <seb128> pitti, oh, is that good? they are playing in Amsterdam and I was pondering getting tickets
[06:19] <pitti> seb128: Sting is amazing
[06:19] <didrocks> bonjour pitti :) jdll ce week-end (http://www.jdll.org/). J'ai donné un talk, il y avait fredp aussi à la maison
[06:19] <pitti> seb128: Admittedly Paul Simon is past his best years; still good, but not comparable any more to the Simon & Garfunkel times
[06:19] <seb128> didrocks, oh, right ... no, it's that popey reported and I assumed it was on vivid channel
[06:19] <seb128> but re-reading the descriptions seems not
[06:20] <didrocks> seb128: seems bqish, but it can be that for whatever reason they took one of whoopsie/whoopsie-preferences without the other one
[06:20] <didrocks> and they need both to be here for the new handling status
[06:20] <seb128> didrocks, I don't think so, maybe something else, maybe updating to vivid would fix it :-)
[06:20] <didrocks> let's confirm once popey is around
[06:21] <didrocks> seb128: ahah, yeah :)
[06:22] <didrocks> seb128: on the technical level, what happens is that the UI talks to a dbus activated service running as root which commits the values to /etc/default/whoopsie (or does the right thing in the new version)
[06:22] <didrocks> seb128: can be in never really worked and the life app cycle prevent the daemon to successfully starts?
[06:22] <didrocks> it*
[06:24] <seb128> didrocks, yes and no
[06:24] <seb128> I think runtime restriction are related to Mir
[06:24] <seb128> system services run fine
[06:25] <seb128> I don't think we need tweaks to the system to be able to run avahi or cups
[06:25] <didrocks> ok, so doesn't seem to be it, it's a simple polkit + dbus activation
[06:25] <didrocks> ok, let's see once popey is around
[07:22] <didrocks> pitti: btw, I didn't see a bug report about it, but someone pinged me about some vmware related mount blocking the system to start
[07:22] <didrocks> pitti: I still have his pastebins, interested?
[07:23] <didrocks> (vmhgfs mount type)
[07:23] <pitti> didrocks: sure, let's see what it says
[07:23] <didrocks> http://paste.ubuntu.com/10660233/
[07:23] <didrocks> -> which leaded me to see the issue was on the mount points, and so, I asked for fstab: http://paste.ubuntu.com/10660243/
[07:23] <didrocks> commenting the .host line did it
[07:24] <didrocks> did google a little bit about it, found some info on arch, but nothing that relevant
[07:25] <pitti> didrocks: you don't happen to have "systemctl cat mnt-hgfs.mount", do you?
[07:26] <didrocks> pitti: no, the guy was mostly in a hurry to get a system booting, I asked him to open a bug, seems he didn't
[07:26] <pitti> didrocks: yeah; would be interesting if (1) sudo mount /mnt/hgfs works manually, and (2) if it works under upstart
[07:27] <pitti> didrocks: the main difference between the two AFAICS is that systemd blocks on failed mounts, while upstart doesn't always
[07:27] <pitti> ("nofail" mount option changes this)
[07:27] <pitti> so my initial guess is that /mnt/hgfs never worked because of missing drivers or whatnot
[07:27] <didrocks> pitti: the user told me he had the share working when booting with upstart though
[07:28] <pitti> ok, then we need the output of (1) I guess
[07:28] <pitti> "mount process exited, code=exited status=1
[07:28] <pitti> i. e. it failed
[07:29] <didrocks> pitti: yeah, I'll ping him if I see him online again
[07:30] <didrocks> I would be surprise if those kinds of share doesn't work under systemd, seems like some users got them working from my search
[07:30] <didrocks> pitti: btw, you didn't see drama either on the upstart-sysv transition?
[07:31]  * didrocks got some emails because third-parties like labs.online.net install manually the list of ubuntu-minimal (they copied the list and aptitude install…)
[07:32] <pitti> didrocks: no, I'm not aware of any reports about that
[07:32] <didrocks> pitti: no news is good news (and at least, now, we know who wouldn't have used systemd by default because of cases like this)
[08:03] <Laney> duuuuuuuuuuudes
[08:05] <didrocks> Laneyyyyyyyyyyyyy \o/
[08:05] <didrocks> how are you? how were your holidays?
[08:08] <Laney> heeeeeeeeeey didrocks
[08:08] <Laney> good and great thanks!
[08:09] <Laney> plenty of walking & eating
[08:09] <didrocks> nice weather overall?
[08:09] <seb128> Laney, wb!
[08:09] <seb128> did you have good holidays?
[08:09] <Laney> mixed, this was scotland :p
[08:09] <Laney> some days were quite fine but it did rain for a few
[08:10] <Laney> hey seb128
[08:11] <Laney> was quite fine, thanks
[08:11] <Laney> it's a picturesque area :-)
[08:11] <Laney> how was the week + weekend?
[08:11] <didrocks> yeah, Julie really wants to visit there :)
[08:12] <didrocks> Laney: was nice overall, did some pretty interesting upstart transition, which triggers some issues for companies not using standard ubuntu :p
[08:12] <didrocks> (like not using ubuntu-minimal, reinstalling packages from their own list, with aptitude, of course…)
[08:13] <Laney> O_O
[08:13] <Laney> "don't do that"
[08:13] <didrocks> that was pretty much my response, but they insist and want to have some additional dependency which would break anyone else :p
[08:15] <pitti> welcome back Laney!
[08:16] <Laney> hey pitti
[08:16] <Laney> wb to you too!
[08:16] <Laney> (not sure when you returned :P)
[08:18] <pitti> Laney: last Thursday
[08:18] <Laney> aha
[08:26] <popey> didrocks: seb128 it was on a shipping bq retail handset running whatever comes on it out of the box (so not vivid)
[08:27] <seb128> popey, can you easily reproduce? can you try if vivid has the same issue?
[08:27] <seb128> could be a bug for Laney :-)
[08:27] <seb128> Laney, wb :-)
[08:27] <popey> sure
[08:28] <seb128> Laney, speaking about bug #1437633
[08:28] <seb128> I think you looked at the u-s-s/whoopsie integration code before
[08:29] <popey> i see no /etc/default/whoopsie on vivid
[08:31] <didrocks> popey: vivid is different
[08:31] <didrocks> there is only /etc/whoopsie, but this one doesn't handle the whoopsie daemon state
[08:31] <popey> it doesn't work on vivid either
[08:31] <didrocks> hum
[08:31] <popey> reproduced on a nexus 7
[08:32] <popey> running vivid r150
[08:32] <didrocks> popey: a nice hint is to disable it
[08:32] <didrocks> and look if there is a whoopsie .override in /etc/init/
[08:32] <popey> there is a whoopsie.conf in /etc/init
[08:33] <didrocks> and no .override once you disable it in the UI?
[08:34] <popey> correct
[08:34] <popey> no .override
[08:34] <didrocks> I would say the UI isn't calling the right things in whoopsie.preferences
[08:34] <didrocks> at it's consistent between vivid and rtm
[08:35] <popey> my vivid is a little outdated, lemme update
[08:36] <didrocks> popey: wait
[08:36] <popey> ok
[08:36] <didrocks> that's interesting
[08:36] <didrocks> how outdated is it?
[08:36] <popey> current build number: 150
[08:36] <popey> device name: flo
[08:36] <popey> channel: ubuntu-touch/devel-proposed
[08:36] <popey> not that bad
[08:36] <popey> last update: 2015-03-27 09:45:51
[08:36] <didrocks> popey: ah ok, no change then
[08:36] <popey> although system settings crashed when i tried to update :)
[08:36] <didrocks> if you were on older whoopsie-preferences, this one directly still read/write to /etc/default/whoopsie
[08:37] <didrocks> so that would have been an indication
[08:37] <didrocks> but yeah, my things stays: I guess whoopsie-preferences isn't called
[08:37] <didrocks> popey: when you check/uncheck, can you look if whoopsie-preferences is running?
[08:38] <seb128> didrocks, popey, remember that the fs is ro on the touch image so we might have to set paths are writable for things to work
[08:38] <seb128> like /etc/whoopsie
[08:39] <didrocks> seb128: doesn't explain rtm though, (or it never worked)
[08:39] <didrocks> but yeah, on vivid, that's a nice one
[08:40] <didrocks> seb128: I wonder even how we could do that .override thus?
[08:40] <didrocks> (as we need to have the file present to turn it rw IIRC)
[08:40] <seb128> not sure, pitti might know, he looked a bit only similar issues iirc
[08:41] <popey> didrocks: yes, whoopsie-preferences does end up running
[08:42] <didrocks> ok, it's called, but something prevents it to write (on rtm, let's forget about vivid for now which is different and will be broken from seb128's remark)
[08:42] <didrocks> did it ever worked?
[08:42] <seb128> I think it didrocks
[08:42] <didrocks> maybe /etc/default/whoopsie was never writable…
[08:42] <seb128> ups
[08:42] <seb128> it did
[08:42] <seb128> Laney looked at it a while ago iirc
[08:42] <seb128> Laney, ^?
[08:42] <didrocks> I have no clue for bq, let's see once Laney is done with his backlog
[08:43] <seb128> bq is not different from the emulator or mako afaik
[08:43] <didrocks> once that's fixed, let's look at vivid to not duplicate if there is more work involved in the system settings side
[08:43] <seb128> or do you mean "touch"?
[08:43] <didrocks> yeah, "rtm"
[08:43] <seb128> k
[08:43] <didrocks> mostly
[08:43] <Laney> erm ok
[08:43] <Laney> I could flash the rtm image
[08:44] <popey> well, /etc/default/whoopsie is a read only file when I try and edit as root with vi
[08:45] <popey> and i see no mount in "mount | grep default" which would match it
[08:45] <popey> so yeah, looks read-only
[08:46]  * didrocks wonders how it could have worked then…
[08:46] <seb128> Laney, the question was rather "did it ever work", which I though you might remember because you looked at it a while ago
[08:46] <seb128> Laney, feel free to say "dunno" ;-)
[08:46] <Laney> it's definitely dunno
[08:46] <seb128> k
[08:46] <Laney> I probably had it writable though
[08:46] <seb128> no worry
[08:46]  * popey wonders if someone tested on a device which had been set RW (in order to add PPAs for testing) which would cloud the result
[08:46] <popey> ya
[08:47] <Laney> so if it is this then I would never have seen the problem
[08:47] <seb128> right
[08:47] <seb128> most of us use rw
[08:47] <seb128> where do we set locations are writable again?
[08:47] <Laney> dpkg -S writable-paths
[08:47] <popey> (this is one reason I bought a bq phone and haven't changed it at all)
[08:47] <seb128> popey, good move :-)
[08:48] <seb128> popey, can you try if replying to sms from the messaging menu works for you?
[08:48] <popey> sure.
[08:48]  * popey finds a SIM
[08:48] <didrocks> ok, so we need to add /etc/default/whoopsie (rtm), /etc/whoopsie and /etc/init/whoopsie.override (vivid)
[08:49] <didrocks> the issue is that whoopsie.override doesn't exist potentially, so it needs test
[08:49] <didrocks> once we switch to systemd, we will have the same issue as well
[08:49] <didrocks> (but the path is more complex and subject to change there…)
[08:52] <larsu> seb128: I totally forgot proposing this on Friday: https://code.launchpad.net/~larsu/ubuntu-themes/progress-bars/+merge/254544
[08:53] <larsu> seb128: do you (or Laney if his backlog isn't killing him yet) backport that patch and have a look at the branch?
[08:53] <larsu> s/do/can
[08:53] <larsu> Laney: hi btw! How are you?
[08:57] <Laney> hey larsu!
[08:58] <Laney> doing good thanks
[08:58] <Laney> good to be back ;-)
[08:58] <Laney> what about you?
[08:58] <larsu> liar! :P
[08:58] <Laney> where can I see the effect of this branch?
[08:58] <larsu> I'm good as well thanks
[08:59] <larsu> any progress bar on the system
[08:59] <larsu> I usually test with widget factory
[08:59] <larsu> not sure if this is uife material as well
[08:59] <didrocks> Laney: with his branch, your life will be better, you will lose weight, feel stronger, reducing stress and better looking too!

[08:59] <Laney> I'LL TAKE SIX
[08:59] <didrocks> ;)
[09:00] <larsu> didrocks: clearly fake marketing. Laney can't look any better
[09:00] <larsu> you need to adjust your targetting algorithms ;)
[09:00] <didrocks> larsu: yeah, the ad targetting script isn't great yet :p
[09:00] <popey> seb128: yes, it works
[09:01] <larsu> didrocks: I think you want to market this towards progress bars (and possibly other widgets)
[09:01] <larsu> but then, this branch makes them gain weight actually
[09:01] <didrocks> larsu: not sure they have upload rights though :)
[09:01] <didrocks> ahah
[09:01] <larsu> haha
[09:02] <didrocks> popey: do you mind trying on vivid with /etc/whoopsie and /etc/init/whoopsie.override?
[09:02] <didrocks> popey: I'm unsure if setting an unexisting file at boot would work though
[09:02] <popey> sure, what do I need to do?
[09:03] <didrocks> popey: oh sorry, I thought you were talking about the whoopsie thing, not the sms one, confusion :)
[09:03] <didrocks> popey: forget about it for now then :)
[09:04] <seb128> popey, thanks for testing
[09:04] <seb128> larsu, can add to my list
[09:04] <larsu> I think Laney's on it
[09:04] <seb128> cool
[09:04] <popey> np
[09:05] <larsu> hm, chpe has been looking at my terminal patches
[09:05] <popey> seb128: feel free to ping me to confirm anything else on the retail device which doesn't require going RW or otherwise messing it up :)
[09:05] <larsu> and started committing some
[09:05] <seb128> popey, noted, thanks :-)
[09:05] <larsu> ugh, and wants gmenumodel features for the others...
[09:25] <Sweet5hark> moin.
[09:25] <seb128> hey Sweet5hark
[09:25] <seb128> had a good w.e?
[09:27] <Sweet5hark> seb128: pretty good. bad weather, so no bad conscience when staying inside hacking ;)
[09:28] <seb128> hehe
[09:28] <seb128> what did you hack on?
[09:28] <Sweet5hark> seb128: http://people.canonical.com/~bjoern/vivid/4.4.1/libreoffice_4.4.1-0ubuntu2_source.changes <- as discussed please consider this for upload for the kubuntu breeze icons. No upload of libreoffice-l10n needed for this one.
[09:28] <seb128> Sweet5hark, k
[09:30] <Sweet5hark> seb128: hacked on the UNO (C++/python/java/starbasic extension bindings) for tables in writer. I ran across that code fixing something else, realized how horrible it is while doing that and decided it needs a complete overhaul -- if only to make it less of a maintainance horror down the line.
[09:30] <seb128> Sweet5hark, libreoffice sponsorized
[09:31] <didrocks> hey Sweet5hark!
[09:31] <seb128> Sweet5hark, you should have played UNO the card game, it's probably more fun :p
[09:31]  * Sweet5hark killed some 500-1000 lines of C++ that were obsolete/nonsense/copypasta in there ...
[09:32] <Sweet5hark> hehe
[09:32] <Sweet5hark> seb128: thx for the upload
[09:32] <seb128> yw!
[09:32] <Sweet5hark> didrocks: heya!
[09:37] <seb128> didrocks, writable-paths has a line "/etc/init/ssh.override                  auto                    persistent  transition  none" so I guess we could do the same for whoopsie?
[09:40] <didrocks> seb128: yeah, there is no /etc/init/ssh.override at boot?
[09:41] <seb128> didrocks, I'm unsure on a new device, mine has one because I've used qtcreator to connect to it etc
[09:41] <seb128> but I guess not
[09:41] <didrocks> seb128: worth a try anyway
[09:41] <seb128> yeah
[09:41] <didrocks> do you handle that one, or want me to?
[09:41] <seb128> I'm going to mp changes after lunch
[09:41] <didrocks> ok
[09:41] <seb128> I can handle it
[09:41] <didrocks> thanks!
[09:41] <seb128> thanks for the guidance ;-)
[09:41] <didrocks> yw ;)
[09:43] <Laney> larsu: with "2" the "50%" in widget factory overlaps the progress bar
[09:44] <Laney> do we need the gtk patch from this bug?
[10:00]  * Laney builds an updated gtk
[10:16] <larsu> Laney: yes
[10:17] <larsu> it has weird spacing even with the default theme now
[10:17] <larsu> that's one of the things that patch fixes
[10:18] <Laney> okay
[10:18] <Laney> be good to get it on the 3.14 branch
[10:20] <larsu> I don't think we should
[10:20] <larsu> it breaks adwaita
[10:21] <larsu> hm, maybe I should patch that for the ubuntu gnome guys...
[10:25] <Laney> how's that?
[10:25] <Laney> how was it fixed in master?
[10:26] <larsu> oh! mclasen simply changed the default
[10:26] <larsu> all good then
[10:26] <Laney> ya
[10:26]  * larsu doesn't like that, but we've never been stable on style property defaults so meh
[10:51] <Laney> larsu: was hoping this would fix the software-center progress bars, seems not
[10:53] <larsu> Laney: oh?
[10:54] <Laney> search for something and 'install' from that view
[10:54] <larsu> ah, I looked at the "progress" view
[10:56] <Laney> inspector doesn't seem to really work there sadly
[10:57] <larsu> hm, doesn't work for me at all
[10:57] <larsu> failed to download package files. check your internet
[10:57] <larsu> erm, I'm typing here, aren't I
[10:57] <Laney> fun
[10:59] <larsu> archive down?
[10:59] <larsu> the fun thing is it gives me 20 dialog boxes to tell me this :(
[11:00] <Laney> seems unlikely
[11:00] <Laney> does apt-get update work?
[11:02] <larsu> Laney: yes (sorry, parallel conversations)
[11:03] <larsu> works now after restarting u-s-s
[11:03] <larsu> woah, that progress bar looks ... interesting
[11:08] <Laney> sure does
[11:22] <larsu> Laney: oops, I didn't mean to remove that
[11:23] <larsu> Laney: but I guess you're right, we don't need this branch at all
[11:23] <larsu> it's unlikely that the default changes again any time soon
[11:25] <Laney> as you wish :)
[11:25]  * larsu deletes
[11:25]  * larsu wishes a brownie
[14:41] <tkamppeter> Laney, hi
[14:50] <Laney> hello tkamppeter
[14:50] <Laney> I saw you subscribed me to some random bugs
[14:51] <seb128> hehe
[14:51] <seb128> Laney, is that some cups-filters segfault in glib code?
[14:52] <Laney> something like that
[14:55] <larsu> Laney: feel free to reassign to desrt
[14:55]  * larsu hides
[14:57] <seb128> tkamppeter, you wrote that those don't happen on utopic, but only vivid has the new cups-filters, so if it's a bug in the new version it's normal it's only in vivid
[14:59] <tkamppeter> seb128, I am using the newest cups-filters also with Utopic, not only with Vivid.
[14:59] <seb128> tkamppeter, well, you also don't get the issue on vivid
[15:00] <seb128> so your config doesn't trigger the bug
[15:00] <tkamppeter> Laney I have seen that you are uploading glib2 and as I am not sure whether the crashes come from cups-browsed itself or perhaps from glib2 I wanted to show you these two bugs.
[15:01] <tkamppeter> seb128, Laney, strange thing is also that I am on default config, not getting the crashes and the users who get the crashes are also on default config )at least cups-browsed.conf).
[15:02] <seb128> tkamppeter, is there anything you need to do from the UI to exercice cups-browsed?
[15:03] <tkamppeter> seb128, no. cups-browsed is started on boot as a system daemon. It keeps running until system shutdown.
[15:04] <seb128> tkamppeter, right, but does it do more things at some moment? can you command through dbus or something?
[15:04] <seb128> tkamppeter, to what event does it react?
[15:05] <Laney> listens for printers over avahi I think
[15:05] <tkamppeter> seb128, it actually does something if an IPP network printer is connected and turned on or if a remote shared CUPS queue appears, for example by turning on another Ubuntu/Linux/Mac OS X computer in the network.
[15:06] <tkamppeter> Laney, exactly this. It listens for printers through Avahi and in addition, it listens to broadcasts of legacy CUPS servers (CUPS 1.5.x or older).
[15:06] <tkamppeter> Laney, seb128, it does not use D-Bus.
[15:06] <seb128> ok
[15:11] <tkamppeter> Laney, seb128, my most recent changes were on auto-shutdown and auto-shutdown is not used by the standard desktop installation of Vivid, this makes it also less probable that my recent changes cause the crash.
[15:12] <seb128> tkamppeter, look at https://errors.ubuntu.com/problem/e6a8f46421486ee16eb01db5bd331f69a3292d0c the issue is not specific to 0.67
[15:12] <seb128> the number of reports raised with 0.66 not sure why
[15:13] <seb128> could be more users of vivid or a bug in that version
[15:14] <tkamppeter> Laney, seb128, another recent change is that Vivid switched to systemd as process 1, but I cannot really imagine that a program which was stable when started by Upstart gets crashy when started by systemd. And Debian uses systemd for longer time and there cups-browsed does not crash.
[15:14] <seb128> I doubt it's due to that
[15:16] <didrocks> happyaron: hey, are you around?
[15:16] <Laney> can any of the reporters reproduce the problem?
[15:19] <didrocks> happyaron: I have the upstream of libcangjie (who develops as well the cangjie ibus module) who is interested in helping you (and modifying libcangjie if needed) so that fcitx get a better Cangjie support, seems like there are quite some improvments into this since the past year
[15:19] <didrocks> happyaron: so, he says he doesn't know about the fcitx status of Cangjie, but if you feel that we can get some code factorized and reusing what they do, maybe it worthes a look?
[15:19] <tkamppeter> seb128, 1.0.66 only modified a function to remove bad characters from strings, improbable that this causes crashes in the event loop. My bet is more that it is somewhere in all this stuff which Tim Waugh did in 1.0.65.
[15:21] <tkamppeter> Laney, I will ask them and if I find someone I will ask them to do things like turning off legacy CUPS browsing or downdating cups-browsed.
[15:44] <Laney> tkamppeter: They can probably also try with glib from utopic if you want to isolate that
[15:51] <tkamppeter> Laney, OK.
[16:22] <seb128> ogra_, rsalveti, is there a vcs for lxc-android-config? or what's the best way to propose a change to it?
[16:22] <ogra_> good ole debdiff :)
[16:23] <rsalveti> yeah, debdiff
[16:24] <ogra_> note that it is currently blocked in silo 19
[16:24] <ogra_> (with the new mtp handlin)
[16:24] <ogra_> +g
[16:29] <seb128> ogra_, rsalveti, https://launchpadlibrarian.net/201616563/lac.debdiff
[16:29] <ogra_> seb128, why are you making the upstart job writable ?
[16:29] <seb128> if you want to add that to your queue for the next upload
[16:30] <seb128> ogra_, it's the override
[16:30] <ogra_> also... if you make a writable file, it needs to exist
[16:30] <seb128> ogra_, because otherwise it can't be written?
[16:30] <seb128> oh, it does? how does it work for the ssh override?
[16:30] <ogra_> so you need to ship an empty .override file
[16:30] <seb128> k
[16:38] <seb128> ogra_, would an empty .override disable the job though?
[16:39] <ogra_> not sure, i think not though
[16:39] <ogra_> as long as there is nothing to override inside ....
[16:39] <ogra_> but i dont know how upstart in general manages to deal with empty .override, you would have to ask jodh
[16:40] <seb128> jodh, ^ :-)
[16:40] <Laney> they have to specify the stanzas to override
[16:40] <seb128> so empty override is fine?
[16:40] <Laney> pretty sure
[16:40] <Laney> you could try it with some job in ~/.config/upstart/
[16:41] <jodh> seb128: ogra is right - the empty override would be parsed and found to contain no stanzas, so would be a NOP
[16:41] <ogra_> sudo touch /etc/init/mountall.override ...
[16:41] <ogra_> will show pretty easily if it works ;)
[16:42] <ogra_> (if it fails your system is screwed .,.. that should be pretty obvious ;) )
[16:44] <seb128> jodh, thanks
[16:46] <seb128> ogra_, new debdiff on the bug then
[16:47] <ogra_> "the bug" ?
[16:47]  * ogra_ looks at the 83721452387 bugs in his bugmail 
[16:50] <seb128> ogra_, the one I pinged about with the first debdiff 15 minutes ago
[16:50] <ogra_> i see the diff but not a bug number :)
[16:50] <seb128> oh, the bug was in the changelog :p
[16:50] <seb128> bug #1437633
[16:50] <ogra_> oh, its secretly hidden in that changelog thing :P
[16:51] <ogra_> who would have guessed :)
[16:52] <seb128> lol
[16:52] <ogra_> seb128, hmm, so who writes to that override file ?
[16:53] <ogra_> is there some dbus service at the system end ?
[16:54] <seb128> whoopsie-preferences
[16:54] <seb128> it uses systemctl under systemd to change the status, and writes an override for upstart
[16:54] <ogra_> ok
[17:06] <Laney> so light at 6pm
[17:06] <Laney> amazing!
[19:19] <attente> Trevinho: hey, are you able to run gnome-terminal under the mir proving server?