[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`