[11:31] Hi [11:32] Are the 18.04 builds stable enough to not crash when using the installer or booting up the installer? >.> [11:45] yes, it works for me just fine [12:17] is there any way to test 18.04 server prior to the import freeze? [12:17] i see desktop pre images, but i am interested in testing server === tfgbd is now known as tfgbd_ [17:35] if anyone knows how to fix these errors I'm all ears - https://github.com/Microsoft/WSL/issues/2960 [17:54] donofrio: have systemd services started in that container (ps ax)? [18:01] albert23, hu? [18:01] not using docker anything just wsl/lxrunoffline [18:02] donofrio: run the command ps ax in the container, that should show some systemd services [18:02] I'm game lets see.... [18:03] albert23, here is what it returns https://apaste.info/aFc2 [18:05] so no systemd services [18:05] albert23: it's Windows! :) [18:05] I know [18:05] this is what I see https://1drv.ms/u/s!AsBlZbBf72iNoL80WYzed14twrwo0Q [18:06] Bit starting a bionic container on debian/sid gives similar fun [18:06] ignore onedrive login jazz [18:07] donofrio: is there anyway in windows to see the container starting, like a normal console? [18:07] no it's not a container its wsl (I mean I can do container things but it's not docker) [18:08] albert23, and others thank you for talking and thinking about this I've not gotten anywhere in four days ;( [18:09] donofrio: it looks like a container just running on a different type of host [18:09] Somehow that conatainer (or however you name it) must be started [18:10] ok I could see that....but I'm limited in what I can see/do outside the wsl [18:11] "c:\tools\lxrunoffline\LxRunOffline.exe list" returns two items bionic and Ubuntu I am trying bionic so I run "c:\tools\lxrunoffline\LxRunOffline.exe run -n bionic" and it retuirned the "donofrio@WSAL0013:~$" prompt [18:13] donofrio: can you pastebin the output of mount? [18:13] sure thing [18:15] https://apaste.info/DDTb [18:16] so no cgroups mounted at all [18:17] fwiw, my 16.04 install returns https://apaste.info/IVqu [18:18] donofrio: I think the missing cgroups are the reason systemd services don't start [18:19] Running bionic on debian sid one missing cgroup was enough to stop systemd [18:19] If you can get the console output, that would probably tell you [18:19] On sid there was a cleer FREEZE message [18:23] I have console output let me check..... [18:23] opps no I dont [18:24] that was all done though powershell/bash [18:25] so my boxes do not have any cgroups (like they might not be implemented in WSL yet?) here is my right desktop w10 1703 w/17.04 disto-upgraded from 16.04 by changed sources (and is my main working terminal till I get left desktop stable and updating again) [18:25] https://apaste.info/r0np [18:26] Well, I cannot be sure you have the same problem as I saw. But systemd services not running is not good. [18:27] And in my case I can also still attach to the container and many things just seem to work [18:27] systemd is running on the right desktop (at least I beleve it is (i started it) [18:27] how to query for health of it? [18:27] Until you need one of those systemd services [18:28] systemctl would tell you [18:29] when I try "systemctl -a" it returns "Failed to list units: Launch helper exited with unknown return code 1" [18:29] on right desktop (17.04) [18:30] donofrio: how is this related to 18.04? [18:30] lotuspsychje, on 17.04 it doesn't [18:30] just figured I built them close to the same [18:30] donofrio: 17.04 is end of life also [18:30] only right desktop is a year older install (1703) [18:32] donofrio: and what dows systemctl say on the 18.04 desktop? [18:33] albert23, it returns "Failed to connect to bus: No such file or directory" [18:34] That's the same I see with 18.04 on sid [18:34] that is a good sign (guessing) [18:34] means wsl is closer to normal linux/sid [18:34] On SID there is a trick to get the cgroups and systemd properly working for the bionic container [18:34] I'm all ears [18:34] But how that works on WSL I have no idea [18:38] shouldn't it just be sudo service systemd start? [18:39] No, on SID you need to create a directory and mount cgroup 2 on it to allow the bionic container to start properly [18:39] So you need to do something on the host, not in the conatiner [18:39] albert23, what does your mount have for your 18.04? [18:41] humm https://github.com/Microsoft/WSL/issues/2209 [18:44] donofrio: this is how it looks in a bionic container on sid: https://apaste.info/TqFm [18:46] cool, much to learn still about wsl and its offerings and what is missing still..... [19:09] what can we do for you furkan [19:09] FurretUber: [19:12] FurretUber: what bug are you wondering about? [19:12] Hi, I "updated" from 17.10 to 18.04 by changing the sources.list file. The xfce4 package does not depend from xfce4-volumed, so xfce4-volumed is marked to be autoremoved, but without it the volume keys don't work [19:12] FurretUber: well first of all, we dont reccomend to upgrade yet in this stage [19:13] FurretUber: if you want to help bug out 18.04 plz install the daily image clean [19:13] FurretUber: this way, we can trace if its really a bug instead of a leftover from a previous release [19:14] This was exactly what I was wondering [19:18] I will download and test with a clean install [19:42] howdy [19:48] albert23, now for crazy question how do I take all my installed package selections and diff them out of the bionic install so I can apt-get the missing ones installed from the steps here https://github.com/Microsoft/WSL/issues/2618 [19:48] so far its up and running just apt-get installing things like xfce4 and ubuntu-desktop and the like.... [19:50] 1466 packages to go....lol [19:50] donofrio: dpkg -l | grep ^ii [19:53] is "archive.ubuntu.com" a alias for "use lowest ping rate mirror?" [19:54] FurretUber, your going to get sadness oneday (at least I was told that when I dist-upgraded from 16.04 to 17.04 using the sources.list way) [19:55] opps lotus beat me to that.....going back to mute ;) [19:56] The notebook survived the 17.10 upgrade (it's a Lenovo), so I thought 18.04 would be a cinch [20:01] FurretUber, "time will tell." [20:04] The bug really biting me started with 17.04: https://i.imgur.com/ad81Dwd.png [20:09] FurretUber, how does it run in VMWare Player? or like me run in WSL :) #duckforcover #lol [20:09] That virtual machine works perfectly when opening it using QEMU command line and VirtualBox [20:10] When using virt-manager, it dies when it tries to update the kernel or the package linux-firmware [20:13] Every Ubuntu's virt-manager virtual machine freezes and stops working when updating the kernel or the linux-firmware package, and the only information I could get from them is that from that screenshot. [20:13] The host system seems to have no issues (there is no dmesg message or anything), but nothing works in the guest after that [20:14] if the has happened before to you might want to ask #ubuntu this is for 18.04 only...... [20:17] I already asked there at least three times, but the message was not read/others didn't paid attention to it (I waited 12 hours for answers) [20:18] irc is slow may take days for answers [20:19] FurretUber, did you try Vmware player on host and how did guest do when firmware was applied? [20:19] I have not tried using vmware player. On the host I have only used QEMU and libvirt [20:20] Never installed any other program, as VirtualBox [20:20] "it's free" fwiw I had many issues with VB and windows 7 guest all was solved when I used vmware player [20:33] Nice touch, I just noticed this as the updates went by "It is likely that 4.4.0-43-Microsoft belongs to a chroot's host" [20:35] error found [20:35] "Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.36.11-1) ...W: http: aptMethod::Configuration: could not load seccomp policy: Invalid argument" what does that mean? [20:36] cause it stopped the update I ran "apt-get install xfce* hexchat firefox inxi pianobar ubuntu-desktop -y" and I do not believe its finished yet [20:38] well maybe it is done....checkin... [20:43] and xfce4 is up - yah me..... [20:57] how do I get screenfetch's output to maintain formatting in pastebinit? [21:01] awesome behold "OS: Ubuntu 18.04 bionic [Ubuntu on Windows 10]" :) I'm a happy man https://1drv.ms/u/s!AsBlZbBf72iNoL84RCA9UQG92YVkPA (skip onedrive login - unneeded)