[15:39] <Laney> Hello upstart friends! I'm after some help writing a user-session job for monkeysphere-validation-agent. It's usually run from Xsession.d in the usual manner taking another program to spawn, but can also run in the foreground, in which case it outputs some shell to be evaluated (setting the important env variable).
[15:41] <Laney> Not really sure how to deal with this
[16:10] <jodh> Laney: I think stgraber was looking at that at the client sprint. We had a similar headache with dbus but circumvented the problem with dbus-launch by calling dbus-daemon directly after first setting the required env var (see /usr/share/upstart/sessions/dbus.conf)
[16:12] <jodh> Laney: problem is that you need the env var to be exported to the Session Init environment using 'initctl set-env', but you can't do that if the program is in the foreground (unless the value of that env-var is fully predictable? *shudder*)
[16:12] <Laney> correct, and it is of course not predictable (or settable AFAICT)
[16:13] <Laney> all I can think of is somehow reinventing parts of the STARTUP mechanism in jobs
[16:13] <Laney> hmm, or having some helper script which does the work (msva-perl my-cool-script)
[16:14] <jodh> Laney: that sounds workable - just have it call 'initctl set-env' and sleep forever.
[16:16] <Laney> jodh: yeah, let me try that
[16:16] <Laney> funny how thinking out loud makes these things turn up
[16:17] <jodh> Laney: yeah :)
[16:32] <stgraber> Laney: sounds like you're doing the same thing I did at the client sprint (go through all packages shipping something in /etc/X11/Xsession.d and fixing those that break under upstart)
[16:33] <Laney> yeah
[16:33] <Laney> plus I happen to use this one so it seems like a good place to start :-)
[16:33] <stgraber> Laney: FWIW when I did that at the client sprint, I only noticed gpg-agent (which I fixed) and monkeysphere-validation-agent which I chose to ignore
[16:33] <stgraber> ah, so people actually use this thing? good to know ;)
[16:35] <stgraber> I chose to ignore it on the basis that nobody in the foundations room knew what it was, the code wasn't terribly readable and it wasn't easy at all to figure out how to run that thing on my machine for testing ;)
[16:37] <Laney> heh
[16:37] <Laney> it probably requires some time investment to set it up
[16:40] <Laney> initctl set-env from the script doesn't work though
[17:16] <Laney> hmm, it /is/ in list-env, but not in my session's environment
[17:33] <Laney> ah, so if I block in post-start until it's set then I get it there
[17:33] <Laney> stgraber: jodh: how would you do that?
[17:43] <stgraber> Laney: hmm, so I'm not completely clear on what's the problem you're having
[17:45] <Laney> soooooooo I call a script as an argument of the main program which does initctl set-env --global foo=bar and then sleeps indefinitely
[17:45] <Laney> but I need to block the job from completing until the set-env has finished, otherwise the env var isn't set in the session
[17:49] <Laney> One option would presumably be to use an event to signal when it's ready
[17:51] <stgraber> ah, I suppose that's because monkeysphere-validation-agent actually exits when the wrapped software returns and there's no way to have it not do that?
[17:52] <Laney> correct
[17:54] <stgraber> so I think the way I'd do it is with a job having only a pre-start and post-stop section (similar to ssh-agent.conf). In pre-start you'd call monkeysphere-validation-agent with a script which prints the environment variables. You'd pipe that output into (while read line; do ...; done) so you can parse the output and when done, just leave the process running in the background
[17:54] <stgraber> similarly to ssh-agent.conf, you'll want to set an environment variable containing the PID of monkeysphere-validation-agent so that you can kill it in post-stop and then unset all the variables
[17:56] <stgraber> though the cleanest way to solve this may be to patch monkeysphere-validation-agent to support just printing the environment variables and then forking into the background (similar to what gpg-agent and ssh-agent do)
[18:00] <Laney> mmm, I'll try that out tomorrow and see what it's like, thanks
[18:01] <stgraber> not sure how active upstream is, but I don't think it'd be unreasonable for them to merge a --print-env or similar function that implements a behaviour similar to gpg-agent/ssh-agent, that'd definitely be my preference
[18:03] <Laney> pretty sure he's fairly active
[18:03] <Laney> you could then basically do the same as the *-agent jobs


[11:19] <StrangeNoises> yes, but you need to customise the settings of the dock, which you can do via installing dash to dock and using its settings.
[11:19] <StrangeNoises> which ubuntu dock also uses
[11:19] <StrangeNoises> oh i just saw the timestamp
[14:03] <lundmar> So now that Ubuntu 17.10 is switching to wayland is there are way to force chrome or firefox to run as wayland clients?
[14:03] <lundmar> are=a
[14:07] <lundmar> I tried setting both GDK_BACKEND and CLUTTER_BACKEND to 'wayland' but then chrome complains "cannot open display: :0"
[14:08] <lundmar> I assume chromium is hardcoded to X11 then :/
[14:10] <akik> lundmar: did you try xwayland?
[14:11] <lundmar> akik: thats the default behaviour, works fine except the webgl performanve is about half what I normally get. That is why I would like to try run it natively as a wayland client.
[14:12] <lundmar> I understand that Chromium have had support for wayland for a while but maybe it is not enabled in the Ubuntu build
[14:14] <akik> lundmar: you can maybe find out if it's linked with the wayland libs "ldd binary"
[14:18] <lundmar> its linked with 3 wayland libs including libwayland-client.so
[14:18] <lundmar> perhaps I need to clear the DISPLAY variable or set it to something different
[14:21] <lundmar> hmm, maybe not as there is already a WAYLAND_DISPLAY
[14:21] <akik> lundmar: what syntax does WAYLAND_DISPLAY's value have?
[14:22] <lundmar> wayland-0
[15:06] <lundmar> akik: I just got confirmation from the chromium guys that there is no working wayland backend for chromium yet
[15:21] <lundmar> and for firefox there is a special wayland nightly build available
[15:22] <lundmar> man, its going to be a while before we can run our favorite applications at native speed under wayland without the Xwayland slowdown
[18:33] <genii> Lubuntu liveusb not connecting to wifi... is this a known issue, and if so, is there a fast fix?
[18:56] <genii> Also cannot edit connections
[23:12] <|rt|> I've run into a new behavior with Ubuntu 17.10 server running kvm guests that are using sparse provisioned qed images.  Where it crashes when allocating more space to the image.  I made a few other changes to my setup so I can't be sure it's not a change in my configuration.  Wondering if anyone else has seen anything like this.
[23:13] <|rt|> the change that i made to my setup was adding an lvm cache pool to the logical volume that's backing my virtual machine images
[23:14] <|rt|> using qemu-convert to convert the images from spares allocated to full images sorted out my issues.
[23:14] <|rt|> sorry `qemu-img convert`


[00:45] <Joki> hello guys
[00:45] <Joki> i am a newbie with ubuntu
[00:46] <Joki> i did something now i dont see options on the right hand side of my firefox for it to be closed minimized etc
[00:46] <Joki> and thats for every window thats open
[00:46] <Joki> i can move them with alt
[00:46] <Joki> but there are no options on the right top corner for it to be closed
[00:46] <Joki> can anyone help please?
[00:47] <jmarsden> Joki: That doesn't sound like a Ubuntu Java packaging issue.  Try /join #Ubuntu and ask in there?
[00:48] <Joki> i searched for ubuntu chat
[00:48] <Joki> how do i join /join ubuntu
[00:48] <Joki> ?
[00:54] <jmarsden> Joki: in most IRC clients you type in  /join #Ubuntu to join the #Ubuntu channel -- does that not work for you?
[00:54] <cody-somerville> jmarsden, I guess he figured out /part
[00:54] <jmarsden> OK :-)
[00:56] <jmarsden> cody-somerville: I have a question/issue for you sometime when I am at home (am at work now) re getting rid of old config.sub/config.guess in an updated package of koverartist.  There's a debdiff attached to the bug but it has lintian errors still.
[00:57] <cody-somerville> ok
[00:57] <jmarsden> bug #236140 .I'll be home in maybe 90 minutes or so.
[02:36] <jmarsden> cody-somerville: OK, can you take a look at my koverartist debdiff and help figure out why it doesn't really get rid of the old config.{sub,gues} files please?
[02:43] <jmarsden> cody-somerville: ping?
[02:44] <cody-somerville> jmarsden, link?
[02:44] <jmarsden> http://launchpadlibrarian.net/16226779/koverartist_0.5-0ubuntu2.debdiff
[02:44] <jmarsden> https://bugs.launchpad.net/ubuntu/+source/koverartist/+bug/236140 is the bug #236140 link
[02:50] <cody-somerville> :S
[02:51] <jmarsden> ?
[02:52]  * persia notes that koverartist is not Java, and suggests #ubuntu-motu
[02:53] <jmarsden> FIne with me.  staying here keeps this one separate from the copyright/etc discussion over there.
[02:53] <persia> Yeah, but the audience is sufficiently different to be confusing.
[02:54] <jmarsden> OK.
[23:40] <Vamkiir> anyone around? :)
[23:52] <cody-somerville> Yes
[23:53] <Vamkiir> yey
[23:55] <Vamkiir> I had a question about the Scanner class.
[23:56] <Vamkiir> Not actual java syntax or anything.
[23:56] <cody-somerville> Is it a packaging question? ;]
[23:57] <Vamkiir> well see I am not quite sure.
[23:58] <Vamkiir> It is a compiler error, and I think it has to do with what version of java I am using
[23:58] <cody-somerville> what happens when you try it with a different version?
[23:59] <Vamkiir> well, I am currently using build <IP_ADDRESS>_06-b02