=== Warrigal is now known as tswett === Toledo|gone is now known as croberts === not_phunyguy is now known as phunyguy [06:18] Is the recovery mode broken in xenial for everyone, or just for me? :) [06:50] coolmouse: hello mate, did your card have better support now on xenial? [06:51] morning k1l [11:04] Trying to make Ubuntu 16.04 use lightdm instead of gdm as the login manager, but `systemctl start lightdm` just fails with the nebulous message “Failed with result 'exit-code'.”. How can I figure out what's happening? [11:05] haasn: isn't lightdm the default?! [11:06] alkisg: No, on a fresh install I just have gdm installed.. hmm [11:06] haasn: is that normal ubuntu (unity), or something like ubuntu-gnome? [11:07] Maybe you downloaded the wrong cd? [11:10] alkisg: I don't know, I'm installing via debootstrap. It's just set to install “xenial” from the normal ubuntu mirror [11:11] haasn: I don't think debootstrap includes a default desktop environment, so you're probably telling it to install some package like ubuntu-desktop? [11:12] alkisg: ubuntu-desktop, yes [11:12] ubuntu-desktop depends on lightdm, not gdm [11:12] Hmm, I tried forcibly deinstalling gdm, installing lightdm and rebooting the system, now I'm stuck on a VT and can't actually type anything (but I can still switch VTs with ctrl+alt+Fn) [11:13] alkisg: I'm also installing ubuntu-gnome-desktop, maybe that's what pulls in gdm? [11:13] Yup, most likely [11:13] Apparently SSHd doesn't start itself on boot, now [11:14] I can ping the machine but not SSH [11:14] And since gdm is installed after lightdm, that's what you're seeing [11:14] Use the recovery console to fix it [11:14] And don't purge gdm if you want ubuntu-gnome-desktop [11:14] Use update-alternatives to select a DM [11:15] If lightdm was uninstalled, then ubuntu-desktop was uninstalled too, as it depends on it [11:15] So it sounds like you have a pretty broken installation now, maybe it would be best to reinstall properly [11:16] Oh, lightdm *is* installed [11:16] I'm just trying to get it to run lightdm instead of gdm3 on boot [11:17] update-alternatives is the command for that [11:18] And there's also /etc/X11/default-display-manager [11:20] Huge upgrade today, it seems, including the new software center, I like it [11:27] alkisg: Hmm, just setting /etc/X11/default-display-manager didn't help (it just displayed graphical error messages claiming “graphics/keyboard/mouse not configured correctly” and asking me to reconfigure them, which did nothing) but removing ubuntu-gnome-desktop definitely changed something [11:27] Now on booting I get this purple login manager with a scrollable user list down the left sided [11:27] Is that ubuntu's lightDM config? [11:28] haasn: I think your issue is broken packages, I don't think it's worth to spend time to troubleshoot a broken installation [11:28] It should be much easier to reinstall [11:28] alkisg: I'm running a fresh install ATM on another machine already [11:28] alkisg: These are installed with an auto-deployment system [11:28] If there's something broken now, it'll be broken on future fresh installs too [11:29] And that system needs both ubuntu-desktop and ubuntu-gnome-desktop? [11:29] That doesn't sound right... [11:29] alkisg: Well, I didn't add those entries to the package list. Somebody else did. So I don't know what the rationale behind it was. But we provide multiple window managers for users to use [11:30] If installing gnome-desktop breaks unity desktop, you should probably contact those projects then... [11:30] File bug reports etc [11:30] I never claimed installing gnome-desktop breaks unity desktop [11:31] I don't know how you're arriving at this unreasonable conclusion. It just sets gdm3 as the default login manager, and I wanted to revert back to lightdm (with our own custom theme) [11:33] OK, I thought you were in the place were your system was broken: [11:33] (01:12:49 μμ) haasn: Hmm, I tried forcibly deinstalling gdm, installing lightdm and rebooting the system, now I'm stuck on a VT and can't actually type anything (but I can still switch VTs with ctrl+alt+Fn) [11:34] Try sudo dpkg-reconfigure lightdm, it might take care of alternatives for you [11:42] alkisg: Another reboot solved tht, apparently [11:42] Anyway, I'm back on lightdm now [11:42] OK [11:43] I'll probably just install the gnome etc. WM separately instead of pulling in the whole ubuntu-gnome-desktop [11:44] Or maybe reverse their install order in the package listr [11:57] Ah, I found the reason it was set to gdm3 [11:58] the debconf file contained gdm3 as the disambiguation question for the DMs [12:57] Okay, pretty much everything is in a working state now (fresh install, udpated configs) - only thing I still need to debug is why unit-shell needs about 5 lightyears to start. (Like, it sits frozen for like half an hour with very high load averages according to `uptime`) [12:57] How can I find out what it's doing? [12:57] It spawns a billion subchilds and none of them seem to be doing anything that would cause a freeze [12:57] Is there a log file or something for unity shell? [12:58] iotop shows no CPU load, iftop shows no network load, top shows no CPU load [12:58] but `uptime` shows a load average >10 [12:59] Ah, after it starts, clicking on the “gear” icon (some sort of settings manager?) also causes it to freeze up [13:01] Only seems slow the first time around [13:02] Ah, dmesg shows a ton of errors related to drm_intel [13:02] GPU might be bad [13:08] Hiyas all [14:40] Should it be possible to run upstart together with systemd? [14:41] bjornar: why would you do that? [14:41] I wouldnt [14:42] but some of my playbooks would [14:42] !systemd [14:42] systemd is the default init system for Ubuntu 15.04 onwards. For information on transitioning from upstart to systemd, see https://wiki.ubuntu.com/SystemdForUpstartUsers [14:43] bjornar: i dont think its meant to run both at the same time... [15:14] Systemd is a replacement for upstart, but there is a compatibility layer available. As in, run upstart services through systemd. [15:29] anyone doing apt-get update & getting a 403? [15:30] hggdh: connected directly with cable/wifi? [15:32] lotuspsychje: wifi; but these are internal apt-get errors: http://paste.ubuntu.com/15111348/ [15:34] hggdh: did you add weird ppa's from somewhere? [15:35] lotuspsychje: nope, this is a brand new install (3 days ago), standard Ubuntu [15:35] hggdh: no other sources enabled then default neither? [15:36] lotuspsychje: none other. /etc/apt/sources.list.d is empty [15:37] hggdh: ok mate can you try ask in #ubuntu-mirrors to doublecheck if there are known issues for your country? [15:37] hggdh: togheter with your paste [15:37] lotuspsychje: ah, #ubuntu-mirrors, had forgotten about that channel. Thanks [15:37] hggdh: not sure its your case, but lets find out :p [15:47] allin all, this is interesting. 16.04 is the first time I had to ditch my install for a fresh install in 5 years. [15:52] running stable as rock here [16:29] mine was stable-ish. Only nit was unity (and compiz) would not start on login [18:49] hm unity performance seems very bad in 16.04, though its a super crappy nvidia quadro 285 [18:54] jtaylor: FWIW, similar graphics card on one of my boxes, and running xdm/openbox is snappy, and DVD/video playback is good. Might be apples and oranges, but the binary nVidia drivers seem to work well enough in Xenial. [18:55] ChibaPet: which driver? [18:55] Um. Let me check. I think 340. [18:55] 3.04 is the latest the card supports unfortunately [18:55] hrm, that's odd [18:56] other de's probably work fine, didn't test them yet [18:56] nvidia-340 here on G86 [Quadro NVS 290] [18:56] but unity is unusable :/ (not a big issue its a remote machine anyway) [18:56] 290 supports 340, 285 not [18:56] Yeah, I thought mine was older, but evidently not. [18:57] I have another machine with 290 but its still on 14.04, theres quite a big difference between the two cards [18:58] ChibaPet: have you tried unity? [18:59] ChibaPet: I do plan on upgrading the 290 machine at some point and that is actually my desktop, so it would be good to know if its usable [18:59] jtaylor: Sporadically in the past, but I usually gut it and just run Openbox. That said, I'm transitioning a few folks to Ubuntu/Unity before long and will have more firsthand experience. [19:00] What I can say is that I had to do my install using the Desktop ISO, and Unity runs there. It didn't feel at all sluggish. [19:00] ChibaPet: good, thanks [19:00] (I was working out root-on-ZFS-on-LUKS for Xenial, and the server install sadly lacks tools for that.) [19:01] (root-on-ZFS-on-LUKS with boot-on-MD-RAID1 to be precise. :P ) [19:02] have they fixed boot from raid1 in the meantime? [19:02] the bug in wily is still open ... [19:02] Well now. That's interesting. What was broken? I didn't know to be wary, so I just did it. [19:02] I'm guessing it's either fixed or what I did sidestepped it somehow. [19:02] in wily the initramfs is missing the raid module [19:02] its a quite simple fix [19:03] but annoying [19:03] Oh, that sounds like root on MD-RAID, not boot. Can't answer that one, as once I'm in the initrd it fires up ZFS and goes from there. === ChibaPet is now known as TwisterFruit === TwisterFruit is now known as TwistedFruit === TwistedFruit is now known as Landru [22:22] hi [22:23] too late to see vulkan in 16.04 ? [22:23] I saw that there are .box images (vagrant) for the cloudimages of xenial. [22:23] Are there also official .box images for the desktop or server version of xenial?