[00:11] <ShellcatZero> dumb question: when I see warnings about init scripts, where should I find these files?  For example: insserv: warning: script 'K01xfce4-power-manager' missing LSB tags and overrides.  I've checked in /etc/init and /etc/init.d and I can't find a script with this name.
[00:24] <TJ-> ShellcatZero: the prefix K01 tells you it's a 'stop' (kill) script, and the number tells you it's a sylink under one of the /etc/rc?.d/ runlevel directories. Such symlinks point to the real script in /etc/init.d/xfce4-power-manager
[00:31] <tomreyn> also asked and answered in #ubuntu :-/
[00:32] <TJ-> haha ahh well, 2 heads are better than 1
[00:41] <ShellcatZero> thanks anyway TJ-
[00:42] <ShellcatZero> that's very informative for the future
[00:52] <ShellcatZero> what would you recommend to do to investigate this error? https://pastebin.com/ZhwNAxVA
[01:11] <TJ-> check the "journalctl -u systemd-modules.load.service" log
[01:14] <ShellcatZero> TJ-: executing that command gives me: "-- No entries --"
[01:16] <TJ-> ironic that systemd doesn't log it's own services
[01:18] <TJ-> try "journalctl -xb -p warning"
[01:21] <ShellcatZero> TJ-: yes, that gave me quite a lot of output to read through
[01:24] <TJ-> ShellcatZero: scary how many warnings and so on a standard boot can cause
[01:27] <ShellcatZero> TJ-: yes, I'm investigating an issue where lightdm fails, along with the error message: "Failed to start Detect the available GPUs and deal with any system changes".  I feel like I'm running in circles investigating a whole bunch of non-issue error messages.
[01:27] <TJ-> That message comes, I think, from gpu-manager, and may be none-fatal.
[01:28] <ShellcatZero> neither lightdm nor gdm will succeed, but lxdm will succeed and the resulting desktop environment is crippled, with few applications that will launch.
[01:29] <TJ-> check the /var/log/gpu-manager.log
[01:29] <TJ-> also check /var/log/Xorg.0.log - maybe the accelerated drivers for the system's GPU aren't being loaded
[01:30] <TJ-> "lspci -nnk -d ::0300" should list the VGA-compatible GPU(s) and the drivers
[01:33] <ShellcatZero> Hmm, here is the gpu-manager.log file: https://pastebin.com/ddFjYDJT
[01:36] <ShellcatZero> output for lspci command: https://pastebin.com/fheAesEU (it's a hybrid system, but the Intel driver is the only one I use AFAIK)
[01:36] <ShellcatZero> https://pastebin.com/fheAesEU
[01:40] <ShellcatZero> here is Xorg.0.log: https://pastebin.com/FVKzLy5C
[01:48] <ShellcatZero> attempting to boot into an older kernel fails as well
[04:17] <mojtaba> Hello, I am backing up a computer using rsync, do you know how should I deal with the file names with special characters?
 mojtaba: try quoting them
 or rather the entire argument
[04:21] <tomreyn> is what i responded last time you asked
[04:22] <mojtaba> tomreyn: How should I do that, they are all in different directories.
[04:22] <mojtaba> tomreyn: As the source, I gave directory path.
[04:23] <tomreyn> mojtaba: so you don't actually provide paths with special characters in them as an argument to the rync command?
[04:23] <tomreyn> it just recurses through directories and then hits them?
[04:24] <mojtaba> tomreyn: No
[04:24] <mojtaba> tomreyn: yes
[04:26] <tomreyn> mojtaba: are both computers running ubuntu? same release or different? which ones?
[04:26] <tomreyn> same architecture?
[04:26] <mojtaba> tomreyn: source is Mac, and dest is ubuntu
[04:27] <tomreyn> both ext4 file systems?
[04:27] <tomreyn> Mac as in Mac OS, or just Mac hardware running Ubuntu?
[04:28] <tomreyn> you probably need to https://askubuntu.com/questions/533690/rsync-with-special-character-files-not-working-between-mac-and-linux
[04:31] <mojtaba> tomreyn: thanks
[04:34] <mojtaba> tomreyn: The thing is that, I initialize the rsync from ubuntu (destination), using ssh.
[04:34] <mojtaba> I have just ssh access to the mac.
[04:35] <mojtaba> tomreyn: I still get the same error.
[04:37] <tomreyn> mojtaba: the article i pointed to explains how to use the iconv option dpending on which side you initiate the transfer from.
[04:38] <tomreyn> i have no further means to help here, i'm afraid.
[04:39] <mojtaba> tomreyn: thanks anyway.
[11:51] <Henster> hi guys i have a free bare metal machine ( i7 intel 2700 12 gb of ram) , i want to install a few servers on it  ,, what free hyper-v OS are you using ?
[11:55] <Ussat> Well....at home I use vmware player to test/play with stuff, at work I have a an esxi cluster I use for prod
[11:55] <Ussat> you could always install the free esxi hypervisor and use that
[12:02] <Henster> https://www.cb-net.co.uk/linux/managing-vms-in-ubuntu-server-16-10/
[12:03] <Henster> mybey i shoudl try this ,, wonder if i can make it run on a nas drive as well
[12:28] <Henster> ill try unsing this https://www.proxmox.com
[17:33] <ShellcatZero> Any help is greatly appreciated: https://askubuntu.com/questions/1021244/can-not-get-lightdm-or-gdm-working-on-lts-16-04
[17:41] <sarnold> ShellcatZero: try uninstalling all the virtualbox guest stuff
[17:42] <ShellcatZero> why do you suggest that, sarnold?
[17:44] <sarnold> ShellcatZero: two reasons (a) a few weeks ago someone else was in here with a problem that sounded similar to yours and uninstalling the guest additions fixed it (b) those were installed around the time your bug said the problem started
[17:44] <sarnold> I can't recall the details of the last guy, whether it was no graphics at *all* during boot or just couldn't get past the plymouth graphics or something like that. but uninstalling the guest additions let him get to X11
[17:50] <ShellcatZero> Wow, sarnold, you were right. That fixed it, I am furious about virtualbox but glad to have my system back.
[17:51] <ShellcatZero> I uninstalled all virtualbox stuff for good measure
[17:52] <sarnold> ShellcatZero: that might be overkill :) but keeping guest packages in guests is probably a good idea, hehe
[17:54] <ShellcatZero> I am going to try to replicate this again sarnold and pinpoint the offending packages.  Looking through my history, how do I interpret the version installed from something like: virtualbox:amd64 (5.0.40-dfsg-0ubuntu1.16.04.2, 5.1.34-dfsg-0ubuntu1.16.04.2)
[17:55] <sarnold> ShellcatZero: I *think* that indicates the old version (5.0.40..) and then the new version (5.1.34..)
[17:55] <teward> sarnold: old, new.
[17:55] <teward> at least for upgrades.  In that order.
[17:55] <sarnold> nice, thanks teward
[17:55] <ShellcatZero> ok, awesome, thanks teward
[17:56] <teward> you're welcome.  (Evils of debugging nginx installation/upgrade failures that only happened between two versions lol)
[17:56] <teward> (I learn a lot about apt history with those evils)
[17:56] <ShellcatZero> lol
[17:56] <sarnold> teward: oh man. :/ that sounds unfun.
[17:56] <teward> it was.  back in the 13.10 era.
[18:01] <dpb1> sarnold: how did you know this was in virtualbox???
[18:01] <dpb1> I'm still stuck on that
[18:04] <sarnold> dpb1: heh, a case of being in the right place at the right time ... from the ask ubuntu page, "the issue then occurred on March 31st"  .. and then noticed the upgrades on the 30th all looked harmless enough but the 31st included virtualbox stuff
[18:04] <dpb1> wow
[18:04]  * dpb1 bows
[18:05] <sarnold> .. and then remembering that other guy a few weeks ago with a problem that made *no sense* until he reported back that removing the guest additions solved the problem
[18:05] <sarnold> similar to this, none of the other logs looked at *all* related
[18:06] <dpb1> right, digging through the bug, virtualbox does stand out
[18:07] <dpb1> ShellcatZero: I'm going to edit a couple of those things to mention virtualbox, just so it's a bit more obvious (now that we know it's a factor)
[18:07] <sarnold> if the other guy hadn't been here first, I would have suggested uninstalling the intel microcode update. I wouldn't have *liked* that answer, but it's what I would have suggested.
[18:07] <dpb1> oh man
[18:07] <dpb1> if that fixed it.  smh
[18:08] <sarnold> yeah :/ we've had enough reports of trouble with the latest drop from intel that I'm not convinced of their stability yet
[18:34] <nacc> rbasak: around?
[20:06] <ShellcatZero> sure dpb1, I'll update it again once I pinpoint the specific offending package(s). I don't think the systemd/openbox updates had anything to do with the issue as of now.