[02:34] <jimtendo-X540S> Hi guys, has anyone else here encountered issues on 16.04 when using an encrypted swap? For some reason, it seems that when my physical RAM starts to run out and the Swap RAM starts to be used, my PC becomes so slow that the cursor only updates every 10s or so. I usually just restart at this point.
[08:24] <lordievader> Good morning.
[10:00] <R13ose> Hi
[10:04] <R13ose> I have a black line on the left side of the desktop where I have a small panel.  How do I get rid of the black line?
[10:52] <yossarianuk> hi - can you set dpi per monitor is you are using optimus/hybrid GPU (nvidia-prime)
[10:53] <yossarianuk> as xrandr doesn't seem to work (on hybrid gpu systems / prime)
[10:59] <yossarianuk> i.e with xrandr I see Screen 0 - which is the size of 2 displays combined. 'Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 16384 x 16384'
[10:59] <yossarianuk> my laptop screen -> eDP-1-1 connected primary 1920x1080+0+0 344mm x 194mm
[10:59] <yossarianuk> and my monitor -> HDMI-1-2 connected 1920x1080+1920+0 531mm x 299mm
[10:59] <yossarianuk> this does nothing -> xrandr --output eDP-1-1 --dpi 96
[11:15] <BluesKaj> 'Morning folks
[17:45] <sgrover> When I do "ip addr" I get a bunch of devices with identifiers like "br-b4f613d83403" - I'm wondering what these are.  I am running *buntu in a Virtual Box VM, so that explains the 3 veth* devices I see listed, but I don't know about the br-* devices.
[17:46] <sgrover> These br-* devices have IP ranges close to my native network DHCP range, and I think they may be causing issues on the network...
[17:47] <BluesKaj> sgrover, what ip are you trying to determine?
[17:48] <Dragnslcr> Might be bridge devices that let your VM communicate with the network
[17:49] <Dragnslcr> I use libvirt/kvm, and I don't see any bridge devices inside the VM, but I have the bridge device on the host
[18:02] <sgrover> BluesKaj: I'm diagnosing a printer connection issue.  Seems my VM can no longer connect to the network printers - can't ping them even.  So working through identifying what is going on.
[18:03] <sgrover> The host network is 111.21.84.0.  The br-devices are getting IPs like 111.20.84.0, 111.23.84.0, etc.
[18:04] <sgrover> close enough to make me wonder if those IPs are being pulled from the host network somewhere, causing problems.
[18:04] <sgrover> Dragnslcr: I had the VM network adapter in bridged mode, tried changing it to NAT and rebooted, still see those br-* devices.
[18:05] <sgrover> Another factor though - I have Docker running in the guest *buntu system - it sets up it's own networking adapters/devices as well.
[18:11] <BluesKaj> n clue about vm guest and docker
[18:11] <BluesKaj> no
[18:11] <sgrover> BluesKaj: np, I realize this is a little um.. specific... :)
[18:14] <BluesKaj> personally i've never a found a vm works without proiblems so dual boot is my pefernce, a little less convenient perhaps, but I'll put up with it.
[18:20] <Dragnslcr> sgrover- yeah, looks like an issue with the LAN. I wouldn't think that a VM system would assign IP addresses that aren't reserved local (normally 192.168.0.0, maybe 10.0.0.0).
[18:21] <Dragnslcr> The system or boot logs in the VMs might have log lines for DHCP
[18:22] <sgrover> Dragnslcr: turns out the br-* devices are created by Docker's networking support.  So they are a non-issue for my printer issue.  Now I know I can ignore those. :)
[18:23] <sgrover> what sucks is that with Brother printers, you often get "br-*" devices or commands... can lead to confusion.
[18:25] <Dragnslcr> Hooray for naming conflicts
[18:27] <Dragnslcr> If you do go back to that addressing issue, /var/log/syslog should have info about DHCP requests, so you can reboot a VM and look for something like getting an address from the wrong DHCP server
[21:29] <Zypres> my top app for kde is KDE connect.. It just works.. I hope that it gets more advanced. I also wish I writing sms could get full suport.. IDK why its not working on my systems..
[22:35] <keithzg> Zypres: I'm jealous, KDE connect has never worked and seems likely never to work on the primary setup I'd want it to (which would require it going through a VPN, since at work some silly person has separated our WiFi from our main network)
[22:35]  * keithzg is that silly person, for the record
[22:55] <Walex> keithzg: VNC usually is fast enough