[07:46] <lordievader> Good morning
[09:35] <Ian_Corne> Anyone else has their X crash after a while after suspend?
[09:39] <fhf> Ian_Corne: this happen to me sometimes but only if i close the lid with particular apps opened
[09:42] <Ian_Corne> hmm
[09:42] <Ian_Corne> I've always had chrome and webstorm open
[09:43] <fhf> dunno this happen to me sometimes with spotify
[12:23] <BluesKaj> Hey folks
[13:53] <Ian_Corne> Hey :)
[14:13] <sjoshi> Hello, Is release ubuntu15.10 on track and will be available by tommorow?
[16:20] <sjoshi> Hello, is this channel logged somewhere?
[16:23] <k1l> !logs
[16:24] <sjoshi> thanks k1l !
[17:19] <PanV> Hello, where can I get mr Wily?
[17:19] <ZeZu> I have a Wily install that I can't get to boot,  it's failing to find rootfs and going into loop waiting on mdadm to find an array ... but i can boot into it just fine in a VM...  but when i update initramfs I get warnings from mdadm.conf that no arrays are defined (which i've never seen before).  And there is no reason for it not to boot,  the kernel finds the usb disk it's on just fine as I boot a livecd off of it.
[17:20] <OerHeks> PanV, see the topic
[17:21] <PanV> Nevermind! I already broke Ubuntu once, I really don't want a second time.
[17:22] <TJ-> ZeZu: Is the root-FS on an md array?
[17:25] <ZeZu> no
[17:25] <ZeZu> It's on a usb-hdd
[17:25] <ZeZu> there are no arrays at all
[17:25] <ZeZu> The only thing that may be different is I had to install through debootstrap,  because installer failed repeatedly
[17:25] <ZeZu> I've double checked the UUID it uses, and tried booting through grub command line manually using root=/dev/sdb3  instead of uuid
[17:27] <TJ-> ZeZu: and does it drop to a busybox shell prompt eventually?
[17:28] <ZeZu> No, it loops forever
[17:29] <ZeZu> If I remove mdadm scripts from initramfs it drops to busybox, but i don't have keyboard input for some reason :(
[17:29] <ZeZu> hmm, maybe that's part of the problem thinking about it... if usb is not working then the hdd the rootfs is on wouldn't be available
[17:32] <TJ-> ZeZu: does the initrd.img need some additional usb mass storage drivers including?
[17:33] <ZeZu> I wouldn't think so
[17:33] <ZeZu> I've never had to add additional usb drivers to them before
[17:34] <TJ-> GRUB loads the kernel/initrd via the firmware or its own nativedisk device drivers; when the /init script starts it will need the kernel drivers for the USB path to the device
[17:34] <ZeZu> I'm thinking more along the lines of a kernel bug on my chipset,  since it works fine in the livecd which likely uses another kernel version.  I guess i'll see if there's another kernel avail and test
[17:37] <ZeZu> Yes, but i'd imagine usb drivers are prob. built-in, I could check the config...
[17:38] <TJ-> ZeZu: if it has a USB keyboard which also isn't working, that suggests a chipset driver is required too
[17:39] <TJ-> ZeZu: which ubuntu release, kernel version, and what make/model of PC or motherboard?
[17:40] <ZeZu> It's a mid`11 imac, so common intel chipset is why I figured they'd deff. be included.   Ubuntu 15.10 / linux 4.2.0-16-generic
[19:14] <erle-> is release schedule on time?
[19:15] <fhf> yup
[19:15] <fhf> wily will arive tmmrw
[19:22] <erle-> then I will upgrade already :)
[19:30] <erle-> update-manager -d is not showing anything
[19:30] <erle-> then I have to wait
[19:33] <Faux> erle-: Isn't it do-release-upgrade -d?
[19:33] <erle-> Faux, did not do it in years
[19:33] <erle-> Faux, that's new then
[19:33] <erle-> Faux, thanks
[19:33] <Faux> I personally think it's a pile of trash and you should just edit sources.list and learn to use aptitude, but who knows. :)
[19:34] <erle-> both suffer from the same problems in my opinion
[19:35] <erle-> it should update the core packages first before touching anything optional in my opinion, but that would be a big job to implement
[19:35] <Faux> Personally I just dist-upgrade and try and find a solution I don't think is too offensive.
[19:35] <erle-> oh, do-release-upgrade is the commandline tool
[19:36] <Faux> Personally I should stop starting every sentence with personally.
[21:06] <lordievader> !schedule
[21:08] <lordievader> Faux: That is the Debian way. I heard things might break if you do that in Ubuntu.
[21:09] <Faux> Things break, but only because apt or aptitude is too dumb to pick a decent solution.  And/or if you have hundreds of extra repos/ppas, which would be the same in debianland anyway.
[21:18] <lordievader> do-release-upgrade disables those and starts a screen session. It simply takes a couple of steps for you to try and ensure a smooth upgrade process.
[21:33] <Faux> It also uninstalls some random packages.
[21:44] <erle-> transmission-gtk and vino have missing dependencies
[21:44] <erle-> both are “supported” by cannonical
[21:45] <Faux> Both are installable for me!
[21:45] <erle-> weird
[21:45] <k1l> erle-: sudo apt update && sudo apt full-upgrade
[21:46] <erle-> do you mean apt-get?
[21:46] <erle-> do you mean dist-upgrade?
[21:46] <k1l> nope
[21:46] <k1l> i mean the new fancy apt command. well its not that new
[21:48] <Faux> COLOURS
[21:48] <erle-> now they install
[21:48] <erle-> thanks
[21:49] <erle-> what is the difference between full-upgrade and dist-upgrade?
[21:50] <k1l> erle-: its basically the same. its just that the "new" apt names it full-upgrade to make the users not be confused with ubuntu release (dist) upgrades
[21:50] <k1l> "no i dont want to upgrade to 15.10 already" when people are told to run dist-upgrade to install all packages
[21:51] <erle-> k1l, thanks
[23:02] <bk_> anybody home?