[07:59] <lordievader> Good morning.
[08:00]  * ObrienDave waves
[11:57] <BluesKaj> Hiyas all
[11:58] <penguin42> Hey BK
[12:02] <BluesKaj> hey penguin42
[16:02] <studio_> hi
[16:02] <studio_> someone online, or only bots in here?
[16:03] <lordievader> No, just 111 bots in here.
[16:03] <studio_> cool :)
[16:04] <studio_> i need some help with ubuntu-desktop-next under vbox 5.0
[16:04] <studio_> it is still not working ...
[16:05] <lordievader> Not working.. how?
[16:06] <studio_> under tail -f /var/log/systemlog i get a message like "can't connect to mir" or something like that ...
[16:07] <lordievader> Ah, Mir. I'm out ;)
[16:09] <studio_> tail -f /var/log/syslog ... sorry
[16:10] <studio_> ah, ok, who can "maybe" help?
[16:12] <studio_> i am not happy about MIR, it makes more problems than it is helpful ...
[16:14] <studio_> is 15.10 based on systemd or not?
[16:16] <penguin42>    Konsole output     root         1     0  0 12:03 ?        00:00:08 /lib/systemd/systemd --system --
[16:16] <penguin42> deserialize 17
[16:17] <studio_> i am not sure about that, because i am able to set "enp0s3"  via /etc/network/interfaces ...
[16:17] <penguin42> (I would love to know why cutting/pasting is now prepending 'Konsole' when I paste from Konsole)
[16:18] <studio_> why eth0 is now called enp0s3 in ubuntu-desktop-next?
[16:19] <Meerkat> where can I find existing bug reports on Wily?
[16:22] <studio_> @Meerkat, Wily is working fine for exp. on Ubuntu-Studio, or Ubuntu-Mate, but on Unity8 with MIR it is a "no-go" ...
[16:23] <penguin42> studio_: It comes from bios naming, it's great when you've got multiple ethernet cards and you need some consistency in how they get named
[16:24] <lordievader> studio_: That is the new udev/systemd interface naming, http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
[16:24] <penguin42> you can turn it off if you feel really offended by it though
[16:25] <studio_> @penguin42, how to use Ubuntu-Desktop-Next on VBox 5.0 ?
[16:25] <penguin42> studio_: YOu don't need to use @ on here
[16:25] <penguin42> studio_: And, I've not tried vbox recently, so not sure what the problem is
[16:29] <studio_> @penguin42, Ubuntu-Desktop-Next is a heavy Alpha, I do not like, to install that on my HDD ...
[16:31] <studio_> @penguin42, please, try to install it on VBox 5.0 ...
[16:31] <lordievader> Could it be that it requires proper hardware acceleration?
[16:36] <studio_> I don't know, but "tail -f /var/log/syslog" allways tells me, that it can't connect to MIR ...
[16:36] <lordievader> Ubuntu Next doesn't use Systemd?
[16:37] <studio_> i don't know, therfore i asked ...
[16:37] <lordievader> studio_: What does 'ps -p 1' return?
[16:38] <studio_> @lordievader, on the phone or on the desktop?
[16:38] <lordievader> The Ubuntu Next thing... not sure if that is the phone or the desktop ;)
[16:39] <studio_> the phone suckz ...
[16:41] <studio_> i "think" the "phone" is a "sub-version" from Android" ...
[16:42] <lordievader> Where do you run the 'tail -f ...' on?
[16:45] <studio_> @lordievader, under VBox 5.0 under Ubuntu-Desktop-Next, latest Version, Kernel 4.1 ...
[16:45] <lordievader> Right, so run 'ps -p 1' there ;)
[16:46] <studio_> wait ...
[16:52] <studio_> on the "Desk-Top":  ps -p 1
[16:52] <studio_>   PID TTY          TIME CMD
[16:52] <studio_>     1 ?        00:00:01 systemd
[16:53] <studio_> but i am not able to login via UI !
[16:53] <lordievader> Right, so you are using systemd. Then why ready /var/log/syslog? It ain't used.
[16:53] <lordievader> Use 'journalctl'.
[16:54] <studio_> /var/log/syslog allway tells me, not able to connect to MIR ... or something like that ...
[16:55] <vivid> probably mir requires an egl driver and vbox isnt providing it?
[16:55] <lordievader> Is that information up to date?
[16:55] <studio_> sudo service lightdm restart restarts the UI, but i am not able to login
[16:56] <vivid> right, mir, egl
[16:56] <lordievader> studio_: https://wiki.ubuntu.com/SystemdForUpstartUsers
[17:02] <studio_> @lordievader, sorry, https://wiki.ubuntu.com/SystemdForUpstartUsers is describing why Ubuntu-Desktop-Next is not working unter VBox 5.0? So why i can still use /etc/network/interfaces under "systemd" ?
[17:06] <studio_> did i missed something?
[17:10] <lordievader> No it describes the transition from upstart to systemd.
[17:12] <studio_> but it seems not to be true ... is the Ubuntu-Touch-Device or the "Ubuntu-Desktop-Next" not able to handle true systemd?
[17:15] <studio_> do i need to purge the "network-manager" to test it?
[17:17] <lordievader> studio_: If 'ps -p 1' returns systemd, you are running systemd ;)
[17:30] <studio_> @lordievader, and if  i  am able to run systemd, why my network-configuration is still working unter /etc/network/intefacec
[17:30] <lordievader> Because it is configured there?
[17:30] <studio_> interfaces and not unter /etc/systemd/network?
[17:31] <studio_> so it is still compatible?
[17:31] <lordievader> No, Ubuntu configures their network devices in /etc/network/interfaces
[17:33] <studio_> and since when eth0 is called enp0s3 ?
[17:33] <lordievader> Since some update of systemd/udev.
[17:33] <lordievader> See the link I posted earlier.
[17:34] <studio_> so it is "nearly"  same  as fedora?
[17:35] <lordievader> Perhaps. I don't know Fedora. But seeing as Redhat developed Systemd, probably ;)
[17:35] <studio_> ok :)
[17:39] <penguin42> actually my fedora box seems to have called it em1 on this box, but hey such is variety
[17:43] <lordievader> Hmm, that should be consistent across OS'es.
[17:43] <lordievader> As it gets the name from the bios.
[17:45] <penguin42> yes, I think it might depend on whether the bios is giving a sane answer
[17:46] <lordievader> That might very well be.
[17:46] <studio_> my fedora  (22) is using enp0s3 fot eth0,  maybe it is a "chance" for ubuntu-touch ...
[17:48] <studio_> since ubuntu-touch is just another clone from android, ubuntu-touch is not "my thing" ...