[00:02] <ColdKeyboard> Anyone have a suggestion on how to check why my Ubuntu Server went offline?
[00:02] <ColdKeyboard> This has been happening often... Whenever I'm not using the NAS for couple of hours or days, SSH connection dies and I cannot remote into
[00:03] <ColdKeyboard> So far, only thing that works is power cycle
[00:03] <MJ6666> I did fire up pavucontrol.  The interesting thing with pavucontrol was that there used to be an entry for redream in there when it was running.  Now there is nothing pertaining to redream.
[00:03] <sarnold> ColdKeyboard: is there anything in the logs?
[00:04] <ColdKeyboard> sarnold: Nothing that stands out to me... It just "crashed" again so I'll restart it and check logs.
[00:04] <MJ6666> I'm going to try to get a fresh dev build.
[00:04] <ColdKeyboard> I don't have a monitor connected so I don't know if it hibernates, halts or crashes...
[00:04] <sarnold> ColdKeyboard: dang.. maybe once it's back up, leave a journalctl -f and top running..
[00:05] <sarnold> ColdKeyboard: hopefully it'll be able to report whatever is going on on its way down..
[00:05] <ColdKeyboard> I don't see it on my routers DHCP leases so it's most likely off
[00:12] <rfm> ColdKeyboard, last time I had a server quitting like that it turned out to be bad memory; might be worth putting a monitor on it and running memtest
[00:14] <ColdKeyboard> rfm: That's a good point...
[00:14] <ColdKeyboard> I restarted the server, checking logs now
[00:17] <ColdKeyboard> This is the syslog -> https://www.pastiebin.com/5de5a97a7efea
[00:18] <ColdKeyboard> Actually here it is in pastebin and longer -> https://pastebin.com/De3SRT57
[00:20] <sarnold> hmm I don't spot anything all that illuminating
[00:22] <ColdKeyboard> What can I run in the background to catch when this happens?
[00:22] <ColdKeyboard> I can leave my desktop connected to the server 24/7
[00:23] <sarnold> journalctl -f and top are my first two thoughts; *maybe* it'd be able to write something to a network connection even if it couldn't write it to disk... and top would let you see what's running, how much memory vs swap is used, etc..
[00:25] <ColdKeyboard> Ok, I have both of them running now and monitoring to see what happens
[00:25] <sarnold> good luck :)
[00:27] <ColdKeyboard> NAS has 16GB of ram, nvme hdd and 8 threads... on top of that it's running two tiny docker containers and samba so utilization is sub 1%. That's what's confusing me... It's not overheating, it's not running out of ram or space
[00:29] <sarnold> memory leaks do happen from time to time though
[00:34] <Volad_Malevich> trying to compile kernel module using this manual, but have some errors((( https://askubuntu.com/questions/960827/drives-for-ralink-mt7601u-wireless-adapter/1004867
[00:35] <Volad_Malevich> downloaded same version of kernel as installed, unpacked needed folder, edited phy.c
[00:35] <Volad_Malevich> compiling: make -C /lib/modules/$(uname -r)/build M=$(pwd) modules
[00:36] <Volad_Malevich> have these errors: scripts/Makefile.build:265: recipe for target '/root/mt7601u/usb.o' failed
[00:37] <Volad_Malevich> </3
[00:39] <sarnold> wow that's hacky... I'm surprised that worked
[00:48] <OerHeks> i think this is a better guide https://github.com/muratdemirtas/MT7601u
[00:50] <sarnold> oh yes
[00:50] <sarnold> there's some silly errors on that page but it overall looks way better
[00:52] <wil3> Evening all... Got a working Ubuntu Server box... I made it an Iscsi client to a big box elsewhere - formatted as xfs, transfered a few files - all working great... I then rebooted the box and it hangs. Last line on screen is SSH server, but, the line beforehand is "Started iSCSI initiator daemon (iscsid).", so, I think I screwed something up - can anyone advise?
[00:53] <sarnold> is sshd running? does the system have an IP configured? does it respond to pings?
[00:53] <wil3> no, SSH is not responding, not pingable
[00:54] <sarnold> dang :(
[00:54] <leftyfb> wil3: lacking ping is your problem, not ssh
[00:54] <wil3> sorry if I get terminology wrong - it's my first time using iscsi... this is the initiatior, I have another box as target.
[00:54] <wil3> argh - it is dhcp on the server, no fixed IP... but, why is iscsi hanging the startup rather than failing/moving on?
[00:55] <sarnold> wil3: oh are you actually using iscsi?
[00:55] <wil3> well... trying to!
[00:55] <wil3> I edited fstab - I put the uuid / _netdev in there, so, I take it that it is failing to get on the network and that is causing the problem?
[00:56] <sarnold> wil3: hmm. I wonder.. I'd hope the iscsi startup stuff doesn't try to start it up until enough of the system is running .. but maybe the dependencies aren't quite sorted out yet. maybe start up with a rescue shell and undo the fstab changes?
[00:59] <wil3> happy to try - annoyingly, the host server is too quick, I can't get to grub menu fast enough... and, when it hangs, even control+alt+delete doesn't seem to work
[00:59] <sarnold> o_O
[01:00] <sarnold> normally servers take like three minutes to get to grub :)
[01:01] <wil3> It's a vm, I hard reboot it, but, it goes through too quick... anyway, I suck... I haven't done resuce in a while... I did e, added systemd.unit=rescue.target to the end of the line and booted, but, it is still hanging on the iscsi line... I'm Googling, but, has the process changed or did I remember wrong?
[01:02] <sarnold> I never learned how to do the systemd way, if 'single' doesn't work then I'd use 'init=/bin/bash' instead
[01:03] <wil3> ok... so... recovery mode is an option under advanced - however, loading it leads to a kernel panic :/ WTF!
[01:04] <wil3> https://snipboard.io/YCOZwv.jpg
[01:04] <wil3> just my luck!
[01:05] <sarnold> wil3: ohho.. how about previous kernels?
[01:06] <wil3> yeah, just did that - and weird... it loaded the previous kernel fine, went to recovery menu, then after a few seconds, the screen went weird... and it mounted the iscsi drive fine:
[01:06] <wil3> https://snipboard.io/ALZcsF.jpg
[01:07] <sarnold> gross but not entirely unexpected, heh
[01:07] <sarnold> does it get further?
[01:07] <wil3> yeah... working in recovery
[01:08] <wil3> so, brain dump... not sure deleting from fstab will do much - but, I'm not sure the order stuff happens in... if the network isn't up, I think iscsid may try to discover even if not mounting - but, I could be wrong
[01:08] <wil3> going to try it now
[01:10] <wil3> yep, removed from fstab, it is still hanging on boot
[01:11] <sarnold> :(
[01:11] <wil3> I can confirm that the network is down, however, another issue - looking at the iscsi target, I can see that it still connected - so, during reboot, it never drops the connection... so, even if network was up, it wouldn't mount
[01:11] <sarnold> but if it made it further on a previous kernel, I wonder if this is a kernel regression or if your hypervisor needs new cpu microcode?
[01:12] <wil3> ok... maybe it does... it just took a bit longer to release target
[01:12] <sarnold> we got some complaints from a recent microcode update but those were hardware I believe https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1854764
[01:12] <wil3> hmm - I'm a poweruser, but, kernel stuff is beyond me... sorry
[01:13] <sarnold> we also had some problem with amd microcode .. https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1853614 .. but that was a reboot loop, not hangs..
[01:13] <wil3> So, I updated today... there is no kernel panic/it just hangs on normal boot - but, I won't see it isn't what is happening as everything is unresponsive
[01:14] <wil3> according to advanced options, it is 4.15.0-72 generic recovery which fails, and 4.4.0-62 generic that works
[01:14] <wil3> the cpu is Xeon E5-2650 v4 - I'll try to boot the old kernel in normal mode...
[01:15] <wil3> ok... old kernel works fine
[01:15] <wil3> this is beyond my understanding, so, if you want me to do any testing or gather any info, I'm happy to, but, I'm out of my depth!
[01:17] <sarnold> wil3: could you file a bug report on this? ubuntu-bug linux will probably do most of it, but you'll have to explain a bit about your environment by hand
[01:18] <wil3> I'm creating an account and trying to do it now (Sorry, new to this)
[01:18] <sarnold> thanks!
[01:18] <wil3> I did do a normal upgrade and distribution upgrade earlier today... is there anyway I can change the default kernel on reboot without screwing other stuff up?
[01:19] <sarnold> hmm nothing that I can think of that's easy..
[01:19] <wil3> @sarnold - should I just add a comment on https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1854764 or should I post a whole new topic?
[01:20] <sarnold> wil3: please a new bug, I just grabbed that one out of thin air..
[01:31] <Bashing-om>  wil3: Probably unrelated, but, I too upgraded the kerenl to -72 and experienced a system lock upon rebooting. A cold re-start and things seem now stable on the 4.15.0-72-generic kernel.
[01:32] <wil3> I've tried without luck :(
[01:34] <wil3> argh, may have messed that up, I tried to submit at generic, but, looks like it did intel-microcode... I can't say it is related or not, but, here it is - https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1854881
[01:34] <wil3> I hope someone can fix it!
[01:36] <wil3> ok... put it back in fstab, rebooted and selected the old kernel - it booted without issue and mounted the iscsi fine... so, glad I didn't mess that up!! bugs (which I hope it is) really shake your confidence!
[01:43] <aleksandrdvorkin> hi
[01:43] <matsaman> hi
[01:44] <aleksandrdvorkin> i am having problem logging into my modem i can login before creating the no-ip.com address but after it wont accept the same password and username
[01:44] <freechoice> hey folks, i've mount a nfs server item to local system , but what i can see the uid and gid are not correct,
[01:44] <freechoice> can anyone help me to fix this
[01:45] <sarnold> wil3: can you run apport-collect 1854881  ?
[01:51] <freechoice> how can i fix this nfs client groupid<PHONE_NUMBER> issue?
[01:51] <freechoice> and user shown as nobody
[01:52] <wil3> @sarnold - ERROR: The python3-launchpadlib package is not installed. This functionality is not available.
[01:52] <wil3> I should have read before I pasted! one sec...
[01:53] <gry> haha :-)
[01:55] <wil3> That's a lot of info!!! Submitted
[01:57] <sarnold> thanks
[01:59] <wil3> Thank you for the help... I'm going to try to get some sleep now and fingers crossed, someone will write something by morning!
[02:29] <d0tsun7> can someone highlight me real quick. testing my weechat notify_send.py -- sorry a little OT
[02:29] <sarnold> hi d0tsun7
[02:29] <sarnold> d0tsun7: hi
[02:30] <d0tsun7> amazing -- it works, thanks
[02:30] <sarnold> woot
[02:30] <d0tsun7> :)
[02:32] <lotuspsychje> good morning to all
[02:58] <altendky> lotuspsychje: so i think i'm finally on a 'real' installation.  clean kubuntu 19.10 worked fine with hdmi.  the installer had already added the nvidia stuff.  my resume issue is addressed in master-next and there was another report of my brightness issue over at freedesktop.org with a(nother) patch.  so i've got master-next + that patch and working resume/brightness/hdmi.  thanks so much for all the help with all of
[02:58] <altendky> those issues.
[02:59] <altendky> there's still some nagging stuff i'm curious about but it can wait (after resume the external display position isn't retained, i'm not convinced fans are being managed properly (overly aggressive))
[02:59] <lotuspsychje> altendky: great to hear! can we conclude something from all your sorrows?
[03:01] <altendky> lotuspsychje: if you wanted to read what was wrong in ubuntu 18.04: https://github.com/altendky/issues/issues/1#issuecomment-560150544  basically how i ran ubuntu-drivers was probably wrong so it didn't get the xorg nvidia driver installed.
[03:02] <ColdKeyboard> I finally caught the event when my ubuntu server goes offline/crashes -> https://pastebin.com/hpG4WtKW
[03:02] <lotuspsychje> altendky: but from a clean install, ubuntu should pick the 'best' driver for you right away, specially from 19.10
[03:02] <altendky> lotuspsychje: i didn't know what was going on.  i flailed/explored, got a vague clue, got lucky that there were existing fixes _somewhere_ and i just needed to get them coalesced into one place.
[03:02] <ColdKeyboard> Can someone explain what does this mean "Dec 02 20:46:38 nas kernel: ACPI Error: Could not allocate 15 bytes (20170831/nsnames-344)" ?
[03:03] <lotuspsychje> altendky: maybe you messed too much with those bumblebee-like software that scrambled it?
[03:04] <sarnold> ColdKeyboard: crazy! my first thought is to look for BIOS updates
[03:04] <altendky> lotuspsychje: yes.  and i think i was aware i was scrambling it.  hence occasionally stopping and going back to fresh with my newfound knowledge and some fixes i'm relatively confident in (a single commit or two that claim to address an issue that match mine and fix mine).  after i scramble it enough i conclude that the time spent learning how to unscramble it is less valuable than starting fresh and learning some more
[03:04] <altendky> there.
[03:05] <sarnold> oh hmm. that 10/18/2019... maybe it's got a bios that's only six weeks old..
[03:05] <ColdKeyboard> sarnold: I'll give it a try... It's a cheap Gigabyte mbo for AMD AM4 CPU. Hopefully there is something
[03:05] <lotuspsychje> altendky: thats a great attitude/journey !
[03:06] <altendky> lotuspsychje: so we need more bug reports.  1) ubuntu 18.04 not installing the driver, 2) ubuntu 18.04 not handling brightness, 3) ubuntu 18.04 not handling resume.  i started reading the bug submission guidelines and iirc they said to _not_ guess as to what issues are duplicates.  seems weird that someone else needs to connect my issue in 19.10 with the same (sure, sometimes we guess wrong) issue in 18.04.  am i
[03:06] <altendky> really not supposed to relate such issues?
[03:07] <lotuspsychje> altendky: i advice before filing bugs, you ask your issues here first one by one systematicly
[03:08] <lotuspsychje> altendky: you clean install the 'problem' release and work from there
[03:08] <sarnold> ColdKeyboard: I'm got to run.. I suggest filing a bug against linux on this; ubuntu-bug linux  should do the trick; maybe try older kernels, older microcodes, we've gotten reports of buggy amd64 microcodes recently .. sigh
[03:09] <altendky> lotuspsychje: sure.  symptoms were the same as in 19.10 kubuntu (brightness control only triggers osd, resume leaves screen black).  i admittedly have not checked to see if the same commits are missing but it seems highly likely.
[03:09] <sarnold> ColdKeyboard: if this is a brand new problem aft er a recent update, that might be nice to note
[03:09] <sarnold> ColdKeyboard: good luck
[03:09] <ColdKeyboard> sarnold: Thanks! Appreciate your help!
[03:11] <altendky> lotuspsychje: anyways, maybe at some point i'll toss on an external drive and go through those details.
[03:13] <Mr_Cyclops> lotuspsychje, hello, big confusion, and hence the question .... for long term storage of files, is Samsung 860 EVO SSD is a good option, I will be using it on my Ubuntu machine ext4
[03:13] <Mr_Cyclops> I have a Spare one, so thought if not inside the machine, will use it for backup, but not sure if its good for long term storage. Any suggestions, most welcome, thanks
[03:13] <lotuspsychje> Mr_Cyclops: yes, the 860 series are pretty great working, 4x faster then the 850 series, reccomended to check firmware updates before install
[03:14] <Mr_Cyclops> how do I do firmware update on the SSD using Ubuntu?
[03:14] <lotuspsychje> Mr_Cyclops: i use samsung magigician for it, but winbased, then after install ubuntu
[03:15] <Mr_Cyclops> Cool  and assuming I can do that by sticking the SSD to ubuntu machine, and using that s/w using Windows on VirtualBox?
[03:15] <Mr_Cyclops> or do I need baremetal Windows?
[03:16] <lotuspsychje> Mr_Cyclops: would be a cool test from VM, but havent tested that, not sure that will work on a virtual HD
[03:16] <Mr_Cyclops> sorry dont know what just happened
[03:16] <Mr_Cyclops> :-/
[03:17] <OerHeks> samsing gives a boot iso https://www.samsung.com/semiconductor/global.semi.static/Firmware_Update_Utility_UserManual.pdf
[03:18] <OerHeks> no windows no linux no osx needed
[03:19] <lotuspsychje> OerHeks: indeed i also tryed that once, think with a utility from plop boot manager, cause unetbootin didnt like this
[03:20] <Mr_Cyclops> OerHeks, so just put the iso on a flashdrive, attach the samsung ssd and boot with iso?
[03:21] <OerHeks> yes, it says so
[03:22] <Mr_Cyclops> sweet, sounds like something worth a try!, thanks so much
[03:22] <p0a> Hello how can I update my emacs?
[03:22] <p0a> Right now I think I'm using 26.1 and 26.3 is out a while now
[03:24] <Bashing-om> !info emacs| p0a
[03:24] <Bashing-om> !info emacs eoan | p0a
[03:25] <Mr_Cyclops> Well, thanks so much OerHeks and lotuspsychje ... gonna try it out and share the results! nite nite ...
[03:25] <p0a> Bashing-om: I'm using 19.4 sorry
[03:27] <altendky> p0a: from what i saw eoan (19.10) is the only one with emacs 26.3.  i don't use emacs or this ppa but https://launchpad.net/~kelleyk/+archive/ubuntu/emacs
[03:27] <OerHeks> 2.7 today .. edge https://snapcraft.io/emacs
[03:31] <p0a> OerHeks: hm...? I see 26.3 in emacs.org
[03:32] <p0a> OerHeks: oh unstable!
[03:35] <OerHeks> and 2.63 stable
[03:35] <OerHeks> sudo snap install emacs --beta --classic
[03:37] <OerHeks> https://github.com/emacs-mirror/emacs for diehards
[04:32] <p0a> OerHeks: thank you!
[06:11] <Lunatunes> Hello I was wondering if I could get some help. Ubuntu 19.10 on my asus tuf laptop isn't detecting my tv/monitor through hdmi.
[06:14] <gry> Hi Lunatunes I would suggest to check dmesg at the time of plugging the tv in.
[06:15] <Lunatunes> okay gry
[06:26] <Lunatunes> gry: so I got this HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.1/0000:01:00.1/sound/card0/input17
[06:27] <Lunatunes> Does this mean its only seeing it as audio?
[08:16] <tmiland> Howdy, made some deb packages for IceCat: https://github.com/tmiland/GNU-IceCat if anyone is interested. 👍
[08:19] <lotuspsychje_> !discuss | tmiland
[08:28] <tmiland> lotuspsychje_ Done, thanks.
[08:56] <fire66> hi upgrade from 19.04 to 19.10 and have kernel panics on every kernel installed, someone can help ?
[09:02] <fire66> hi upgrade from 19.04 to 19.10 and have kernel panics on every kernel installed, someone can help ?
[09:23] <fire66> hi upgrade from 19.04 to 19.10 and have kernel panics on every kernel installed, someone can help ?
[09:23] <gry> hi
[09:23] <gry> does it boot into safe mode?
[09:24] <fire66> mope
[09:25] <fire66> nope
[09:26] <fire66> tested also grub changes nothing can solve, i am looking at a fstrim bug that maybe be the cause of this no kernel will boot the system of go in safty mode
[09:28] <fire66> ther's a bug opend but no response
[09:28] <fire66> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849419
[09:42] <Pricey> fire66: Can you boot using an older kernel? Old versions shouldn't have been removed and still be accessible via grub?
[09:44] <lotuspsychje_> his bug was marked incomplete
[10:52] <nightuser> Hi folks. What's the right way of enabling auto-updates on a server? Still use cron or systemd timers?
[10:52] <lotuspsychje> come join at #ubuntu-server mate
[12:06] <BluesKaj> Hi folks
[12:11] <makara2> help. I just apt update/upgraded my system (18.04 Ubuntu Mate) and restarted. It logins in itself, and then the mouse pointer and keybord are unresponsive. I can see CPU/load/network graph working away in taskbar
[12:22] <makara2> and holding down shift doesn't bring up the grub menu
[12:31] <makara2> esc brings up grub menu
[12:41] <makara2> Grub dpkg says my python3 is corrupted. I dropped to root, apt install --reinstall python3 and reboot into 5.0.0-37-generic, and then 5.0.0-36-generic. Same, except the taskbar doesn't even show
[12:41] <makara2> i'm running out of options
[13:05] <trickyriky> hello ubuntu
[13:06] <trickyriky> do we have any guru's around here? i am really strugling with what i suspect to be a driver problem
[13:09] <trickyriky> if anybody could help me with https://askubuntu.com/questions/1193325/how-to-get-my-wintv-hvr-4000-hd-working-again i would be forever indebted
[13:32] <stratus_ss> good day all. I was wondering if the logs from the IRQ channel are reviewed and responded to? I posted a question twice over the weekend and just wondered if I should repost it during the week
[13:34] <rbasak> stratus_ss: generally they are not. It's OK to repost a question as long as you don't do it too frequently (once a day is definitely fine) and you're on-topic and not splitting the discussion somewhere else.
[13:34] <coz_> stratus_ss, this past weekend, in the US, was a holiday weekend. It may not have been seen during that time. The best solution is to repost it a few times during the day,several hours apart if it is not picked up quickly. Patience is also required ")
[13:35] <rbasak> stratus_ss: if you continue not to get an answer, somewhere like askubuntu.com may work better.
[13:35] <coz_> ^^^
[13:36] <stratus_ss> ok so let me ask the less technical question. How do I go about determining where to ask things? (RE the last couple Ubuntu podcasts have been talk about this)
[13:36] <stratus_ss> I didn't use Ubuntu bug thing because I dont know exactly where the problem exists
[13:37] <stratus_ss> and being an employee of a company that receives a large amount of bug reports, didnt want to generate noise for no reason
[13:38] <makara2> trickyriky: i don't think this is the right channel for your question
[13:39] <trickyriky> makara2 sorry if i'm in the wrong place, can you point me in the right direction please?
[13:40] <rbasak> stratus_ss: that's a good question but I'm not sure we have a good general guide to that unfortunately
[13:40] <rbasak> stratus_ss: I think it depends on the nature of your questoin
[13:40] <rbasak> stratus_ss: I'd like to think that if you ask the question in the "wrong" place then the community will helpfully and politely point you to the right place. You shouldn't worry about getting it wrong.
[13:41] <stratus_ss> ok without getting into the actual technicals, I was having a problem with Plex (or so I thought). I went on their support forms and they believe it is related Aquantia network drivers in ubuntu
[13:42] <stratus_ss> one specific client (a chrome book) would case the entire Ubuntu server to lock up consistently
[13:42] <stratus_ss> without logs
[13:43] <stratus_ss> they requested that I switch to Fedora to confirm, so that is what I am in the process of doing right now, as this is considered the main function of the box, its "mission critical" the WAF is through the floor
[13:43] <rbasak> What's WAF?
[13:43] <stratus_ss> Wife Approval Factor
[13:43] <rbasak> I see, OK.
[13:43] <stratus_ss> sorry common acronym where i am from
[13:45] <rbasak> Plex doesn't ship _with_ Ubuntu, so it's difficult for the Ubuntu community in general to help. Ideally if it's an Ubuntu issue, the Plex community would help you isolate the problem to a demonstration of how Ubuntu locks up without Plex - for example by triggering a bug in Ubuntu in the most simple way that doesn't involve Plex at all.
[13:45] <stratus_ss> however, I really would prefer to have this box on Ubuntu in the long run, did not want to file a bug against the network card itself as I have other machines with this same card
[13:45] <rbasak> But regardless I think it's on-topic here - it's just more difficult for the community to help without that, as you're limited to others who know Plex well.
[13:46] <makara2> trickyriky: are u sure there's an irc channel for this? YOu're having issuing with a product, so their support page
[13:46] <rbasak> Are you installing third party network drivers on your Plex server?
[13:46] <stratus_ss> ya that is exactly my problem, I know plex is 3rd party. However, as I said their support believes Plex is mearly exposing a problem with Ubuntu drivers for the card
[13:47] <stratus_ss> nope just the ones that ship with Ubuntu Server 18.04/19.04/19.10
[13:47] <stratus_ss> its present in all versions
[13:47] <makara2> WAF = web application firewall
[13:48] <trickyriky> makara2 unfortunately i have no idea if they have an irc channel or not, im strugling to find anything of help. The setup was working perfectly in 16.04 and 18.04 after dist upgrade, but after about a week it crashed and i have not been able to get it working since
[13:50] <trickyriky> currently rebuilding a kernel, if that dont work i will try a fresh install of 16.04 just to make sure
[13:50] <rbasak> stratus_ss: are you installing third party network drivers on your Plex server?
[13:51] <stratus_ss> rbasak: nope Its just the default ones that come with Ubuntu Server. I have tried Ubuntu 18.04/19.04/19.10 the issue presents itself in all of them
[13:54] <rbasak> stratus_ss: can you describe exactly what you mean by "lock up"?
[13:56] <stratus_ss> rbasak: the system is completely unresponsive. It doesn't respond to ping, the monitor displays "no signal", cannot ssh into the machine, it doesn't respond to ctrl alt del
[13:57] <rbasak> stratus_ss: "no signal" is odd, unless the issue is that your monitor wasn't connected at boot. If you have the monitor connected and log in first, and then reproduce the crash, does that give you anything?
[13:57] <stratus_ss> rbasak: I looked at journalctl there is nothing consistent before the crash. Sometimes Cron has kicked off, sometimes NetworkManager-dispatcher.service is the last line
[13:57] <stratus_ss> I live a "crash cart" plugged into this computer at all time so the monitor is always plugged in
[13:57] <stratus_ss> *leave
[13:58] <makara2> trickyriky: well if everyone else in your 18.04 system works then its doubtful anyone here would have any insight into your very specific problem
[13:58] <makara2> s/everyone/everything/
[14:00] <rbasak> stratus_ss: what does the monitor show before the crash then? Is it working? Do you have a login screen that disappears with "no signal" at the time of the crash? Or something else?
[14:01] <trickyriky> makara2 i was hoping somebody would see something obvious to them in the dmesg and laugh at me then tell me what i'm missing. i don't actually know what the problem is, but i strongly suspect its a driver issue. like i say if this kernel im currently building doesnt fix it then i will try a fresh install of 16.04 and if that doesnt work somethings
[14:01] <trickyriky> heading for the bin lol
[14:02] <stratus_ss> rbasak: Normally I have logged in as a regular user and its just sitting there, which means its just the prompt. And then the monitor goes off, there are no kernel messages if thats what you mean
[14:02] <stratus_ss> rbasak: or maybe there are but because it stops sending a signal almost immediately i dont catch them
[14:03] <makara2> trickyriky: I strongly recommend moving off 16.04
[14:03] <makara2> when dealing with quirky drivers, move forwards in updates not backwards
[14:04] <trickyriky> makara2 i am currently on 18.04 but even a fresh install wont make it work, reverting to 16.04 where it worked for over a year is a last resort before putting some hardware in the bin
[14:05] <makara2> trickyriky: why not try 19.10?
[14:05] <rbasak> stratus_ss: before a crash but after everything is running, what does "cat /proc/sys/kernel/tainted" say?
[14:05] <trickyriky> makara2 is that a server flavour? i thought 18.04 was the latest server?
[14:06] <makara2> trickyriky: all ubuntu is server. 18.04 is the latest LTS
[14:07] <rbasak> stratus_ss: oh, and also could you report the output of "uname -a" please?
[14:07] <makara2> desktop is just server with a display manager installed
[14:07] <stratus_ss> rbasak: good question. I will test this out, since I am following the steps suggested in the plex forums right now, the system is on fedora (now). My mission now is to gather a bunch of things to look at when I switch it back over christmas
[14:07] <rbasak> stratus_ss: OK.
[14:07] <stratus_ss> I do have the kernel version
[14:07] <stratus_ss> rbasak:  Linux version 5.3.0-23-generic
[14:07] <rbasak> stratus_ss: if the kernel isn't tainted, and you're definitely running an Ubuntu-shipped kernel, then I think you have a kernel bug.
[14:08] <trickyriky> @makara2 i think i went with the LTS version because the system is normally headless, i do everything over ssh
[14:08] <stratus_ss> rbasak: I have most definitely NOT installed anything except the following: Plex, ZFS, NFS
[14:08] <stratus_ss> and of course just running updates
[14:08] <rbasak> ZFS will taint the kernel I think
[14:09] <stratus_ss> because its a module?
[14:09] <rbasak> But if it is the ZFS that shipped with Ubuntu and the problem is in ZFS then it's still an Ubuntu bug :)
[14:09] <stratus_ss> ya i just did apt install zfs, or whatever the package is called
[14:09] <rbasak> You could try https://wiki.ubuntu.com/Kernel/MainlineBuilds to help debug, but I'm not sure if that will play well with ZFS
[14:09] <rbasak> Maybe try without ZFS and with a mainline build if necessary
[14:10] <stratus_ss> i can dump zfs though
[14:10] <rbasak> To help narrow down where the problem is.
[14:10] <stratus_ss> ya absolutely i am just making a list of things to try. So far I have checking it the kernel is tainted, removing zfs, trhing a mineline kernel
[14:10] <rbasak> That sounds good to me.
[14:11] <rbasak> https://wiki.ubuntu.com/Kernel/Bugs describes how the kernel team would like bugs reported
[14:11] <stratus_ss> thanks for the pointers.... Perfect I was just going to ask
[14:11] <rbasak> And please do file a bug once you have the answers to those questions
[14:11] <rbasak> However I'm not sure that you'll get any progress on a bug without steps to reproduce without Plex
[14:12] <stratus_ss> ya, it may be something I live on fedora for a while... sadly of all the computers I have, this one does not have ipmi which means when it locks up someone has to physically push buttons
[14:12] <rbasak> If on the other hand you find that a mainline build does not have the problem but adding ZFS or Ubuntu's normal kernel introduces the issue, then the kernel team might be able to help you bisect to find the problem.
[14:13] <nixfreak44> I'm trying to run a 32bit elf file, can I run a 64bit arch and install 32bit libs or do I need to run a i386 arch ?
[14:13] <makara2> trickyriky: that's got nothing to do with it. Server/desktop is just about what packages you have installed
[14:15] <makara2> get the latest 19.10 server and try with that. 99% of the reason to take a later distro is to support quirky hardware
[14:15] <stratus_ss> rbasak: thanks again cheers!
[14:16] <rbasak> You're welcome!
[14:21] <trickyriky> my irc crashed, appologies i may have missed a message
[14:22] <makara2> trickyriky: get the latest 19.10 server and try with that
[14:23] <trickyriky> makara2 i will reluctantly give it a try if this kernel im building don't work, i dont like the sound of no i386 support though.
[14:27] <nixfreak44> I'm trying to run a 32bit elf file, can I run a 64bit arch and install 32bit libs or do I need to run a i386 arch ?
[14:28] <nixfreak44> I tried installing the server version of Xenial LTS
[14:28] <funabashi> When i copy from putty text to word,notepad (windows) it get a new line after each sentence
[14:36] <StucKman> lxc is unstoppable
[14:37] <StucKman> sudo snap stop lxd
[14:37] <StucKman> Stopped.
[14:38] <StucKman> t
[16:14] <MWM> i Just upgraded to 19.10 from 19.04 with 'do-release-upgrade' (Budgie) and now I cant open a terminal.  I just get the little spinner for a minute and then the terminal doesnt open.  Now what? :)
[16:16] <SE7EN`> MWM: Can you drop into console mode to see what syslog has to say?
[16:16] <jgoux> Hello
[16:16] <jgoux> I'm looking for a channel to get some help about some bash syntax
[16:16] <jgoux> Is there such a channel? :)
[16:17] <leftyfb> jgoux: did you try #bash?
[16:17] <jgoux> nice !
[16:17] <jgoux> thanks ^^
[16:18] <MWM> syslog says : cannot open display: :1001
[16:18] <SE7EN`> -_-
[16:18] <MWM> currently googling to see if I can find a fix for that. feel free to chime in if you know what that means though :)
[16:19] <SE7EN`> Well generally speaking an issue with X configuration
[16:20] <eelstrebor> if i understand signing a kernel, you  can't just sign the kernel debs but have to sign every kernel module?
[16:24] <nixfreak44> I'm trying to run a 32bit elf file, can I run a 64bit arch and install 32bit libs or do I need to run a i386 arch ?
[16:25] <nixfreak44> sorry for the repeat the network keeps splitting
[16:37] <mmlj4> if I use LTS, will it be a painless upgrade to (I'm assuming) the next one that's released?
[16:37] <compdoc> 16 to 18 was great for my systems
[16:38] <compdoc> no issues
[16:42] <lotuspsychje> mmlj4: every ubuntu release comes with changes, there's no magic red button that will promise painless
[16:42] <lotuspsychje> mmlj4: its highly reccomended to keep backups yourself before upgrading, but most cases the LTS way is a more stable way
[16:43] <mmlj4> thanks, both of you
[17:33] <deadrom> hi
[17:34] <deadrom> had a Lenovo Thinkpad T530 on a dock which I used to suspend-to-RAM and wake up, worked in 18.04LTS all the time. switched to a Dell M4800 on dock, now *this* one loses the displays everytime I resume. anyone have an idea why?
[17:35] <deadrom> it sometimes comes up again right after suspend as if sth woke it up again. is there such a difference in support? both intel core, both nvidia
[17:36] <rud0lf> deadrom: i have dell m4800 and its power management is crazy, along with lightdm and lid handling
[17:36] <rud0lf> had to disable everything
[17:36] <deadrom> rud0lf: so not crazy good but crazy crazy?
[17:37] <rud0lf> crazy crazy
[17:37] <rud0lf> and no way to google the issue
[17:37] <deadrom> it sits here on a dick on AC power all the time, lit closed. only using it as a desktop replacement.
[17:37] <rud0lf> *cough*
[17:37] <deadrom> DOCK!
[17:37] <deadrom> :D
[17:38] <rud0lf> it's winter time, nothing wrong to warm yourself...
[17:39] <rud0lf> deadrom: may be a void try, but try to do Ctrl+Alt+F1 then Ctrl+Alt+F8 (not F7!) when screen is blank
[17:39] <rud0lf> may be a temporary solution
[17:39] <rud0lf> or F7 if F8 fails
[17:44] <deadrom> I've got a script with a xrandr  command set that usually sets things right, haven't figured where to call it so it's run after a resume
[17:44] <deadrom> and sometimes is does not even work
[17:45] <deadrom> first thought was "get a W541", but those are expensive. maybe a modern Ryzen micro system serves me better
[17:47] <deadrom> rud0lf: ill try that. maybe gives insight what happens
[18:14] <temp4question> Hi. Package gimp-python is not available for Ubuntu Focal Fossa. What replaced it?
[18:19] <SlowJimmy> hi i am running an older version of ubuntu 18.04
[18:19] <SlowJimmy> and i would like to aks how i can update my php and my php only?
[18:19] <SlowJimmy> i need it one version higher at least as it comes in the repos
[18:20] <OerHeks> temp4question, reask in #ubuntu+1 please, untill release
[18:20] <OerHeks> !fossa
[18:20] <temp4question> OK, thanks OerHeks
[18:21] <SlowJimmy> OerHeks: ty
[18:21] <OerHeks> seems like that package is gone since Warty .. https://launchpad.net/ubuntu/+source/gimp-python/+publishinghistory
[18:22] <OerHeks> SlowJimmy, update my php and my php only? .. don't do that, update all packages.
[18:22] <OerHeks> sudo apt update && sudo apt full-upgrade
[18:32] <texla> Ubuntu 18.04.3 when I login I get a message "quit waiting on suspense" this causing my laptop to be slow booting where do I correct this message
[18:45] <eelstrebor> any chance there'll be a decent 5G linux based cellphone?
[18:45] <OerHeks> eelstrebor, no.
[18:49] <SlowJimmy> OerHeks the highest available version in the repos is 0.1 versions too low can't i install from tar? if i mv the folder to etc/... and so forth and then show the OS where to look?
[18:52] <seere> SlowJimmy: php is a binary installation, if you grab the source tar you would need to compile it.
[18:52] <OerHeks> one could use the ondrej ppa .. https://launchpad.net/~ondrej/+archive/ubuntu/php?field.series_filter=bionic
[18:53] <OerHeks> use at your own risc, or upgrade to a higher ubuntu eoan with php7.3? https://launchpad.net/ubuntu/+source/php7.3
[18:53] <SlowJimmy> OerHeks do you know by any chance if that ondrej guys repo is all free software?
[18:53] <SlowJimmy> i mean like an mit or gpl license
[18:53] <SlowJimmy> or like an apache license
[18:54] <SlowJimmy> oh so i can just upgrade the entire distro and get the new php?
[18:54] <SlowJimmy> ok
[18:54] <OerHeks> same license as ubuntu provides, i guess?
[18:55] <OerHeks> not sure there are non free packages in that ppa, never heard talk about that
[19:04] <leftyfb> SlowJimmy: is there some incompatibility with the php available in 18.04?
[19:09] <palooka-jock> Hello all. Wondering if someone might have any ideas - I'm running Kubuntu 18.04 on a dual 30" screens. I like having zero window decorations, so I've gone into System Settings > Application Style > Window Decorations > Window Specific Overrides and added a ".*" regex which is set to no border and hides the window title bar. Most applications work seamlessly when I set them to fullscreen, but I've noticed
[19:09] <palooka-jock> that terminal emulators seem to have large gaps at the bottom, and small gaps on one side. See attached screenshot https://imgur.com/gallery/6lQRLgM. The white at the bottom & left side of both screens is the gap. I mainly use urxvt when noticing this issue but it also occurs in xterm. I've just tried konsole for the first time for some time and that doesn't seem to have the same issue. Any tips?
[19:21] <kenperkins> what's the correct way to permanently disable a sound device? my monitor is hdmi, and ubuntu thinks it's a sound card and keeps switching to it
[19:21] <sarnold> palooka-jock: try fiddling with the -bd command line option (borderColor resource) https://linux.die.net/man/1/urxvt
[19:27] <arooni> question; on ubuntu 18.04 gnome seemed to hang on my t420 so i read a stack exchange somewhere that said to uncomment the line in /etc/gdm3/custom.conf to WaylandEnable=false ;; what does this do
[19:27] <arooni> after i uncommented it it seemed like i could login
[19:27] <arooni> and is it bad to leave it that way?
[19:27] <sarnold> wild guess, that forced x11 instead of wayland; it's probably fine
[19:28] <arooni> am i losing anything on this ?
[19:28] <arooni> with this setting rather
[19:32] <sarnold> probably not; I don't think there's any real user-facing gee-whiz features..
[19:33] <OerHeks> arooni, no, you just lost the wayland session
[19:33] <OerHeks> no problem, so have fun!
[19:34] <arooni> is this a common thing?  i read other people doing it
[19:34] <arooni> i normally booted fine even with that line commented out ; but even after restarting recently it was the only thing that let me in
[19:34] <arooni> dont wanna lose out on cool new features either lolz
[19:36] <OerHeks> no, it is an extreme measure for some boot problems / video, i guess
[19:38] <arooni> whats weird is i just have an integrated intel video card for this laptop
[19:38] <arooni> theres nothing exotic and its the t420 back from 2011
[19:43] <Apachez> any of you who knows the purpose of the /casper/filesystem.size file in ubuntu isos?
[19:53] <genii> Apachez: https://help.ubuntu.com/community/LiveCDCustomizationFromScratch#Compress_the_chroot seems to indicate it's for the installer to know the actual size of a compressed squashfs image, if it will be installed elsewhere
[19:54] <genii> So most likely Ubiquity scans this file to see if the place you're installing to has enough room to hold it
[20:02] <Annoyed> Greetings... having a problem updating a VM running ubutu 16.04.6 LTS desktop. The software updater tool fails with a package operation error box: The installation or removal of a software package failed., and command line apt upgrade bombs out with the following: files list file for package 'libvte-2.91-0:amd64' is missing final newline
[20:02] <Annoyed> Any ideas?
[20:06] <ioria> Annoyed, might be a cache or a /var/lib/dpkg/status  corruption, or an out of space issue
[20:07] <Annoyed> sda1        12G  7.7G  2.9G  74% /
[20:07] <Annoyed> 'bout 3 G free
[20:08] <genii> Annoyed: I might try: echo -e "\n" | sudo tee -a /var/lib/dpkg/info/libvte-2.91-0:amd64.list        ...and then try the apt upgrade command again
[20:09] <ioria> Annoyed, try that ^
[20:12] <Annoyed> ok, that gives different error. no output from the command you suggested, and upgrade now gives : files list file for package 'libvte-2.91-0:amd64' contains empty filename
[20:14] <genii> So that means the file file had no content before we added the newline
[20:14] <ioria> Annoyed, ls /var/lib/dpkg/info/ | grep libvte-2.91-0 | nc termbin.com 9999
[20:15] <Apachez> genii: ok so it should be safe if I forgot to update that then
[20:15] <genii> Probably dpkg package state is in an inconsistent state where it says installed but this file got corrupted/didn't download
[20:15] <Annoyed> result: https://termbin.com/m1hb
[20:15] <Apachez> I was worried startup disk creator somehow used that info to create a static size partition on the usb or something
[20:16] <genii> Fastest fix would be to use --reinstall switch on the package, it will redownload everything for it even those files already exist
[20:17] <genii> Annoyed: I'd suggest: sudo apt-get install --reinstall libvte-2.91-0:amd64
[20:17] <genii> ( I still prefer apt-get, apologies )
[20:17] <Annoyed> I'm not trying to install anything. Just trying to do a system update.
[20:18] <ioria> Annoyed, try the reinstall
[20:18] <Annoyed> The GUI updater tool prompted, I ran it, it dropped a useless error, no details, and then I tried apt update and apt upgrade
[20:18] <genii> The update should be able to proceed normally after the list file for that package actually contains what it's supposed to
[20:19] <ioria> Annoyed, if it fails we do a sudo mv /var/lib/dpkg/info/libvte-2.91-0* /tmp and try again
[20:20] <Annoyed> ok, moving to /tmp allowed the install to proceed, apparently ok, now trying update
[20:21] <ioria> Annoyed, in any case, might be a bad sign about the disk health
[20:21] <Annoyed> It's' a VM
[20:21] <ioria> same
[20:22] <Annoyed> I use ubuntu on VM's for browsing/general internet use... Safer than windows. =)
[20:22] <ioria> vm writes on disk
[20:22] <ioria> not on clouds
[20:22] <Annoyed> yeah, I know... but the upgrade went through that time after your suggestions.
[20:23] <ioria> ok
[20:23] <Annoyed> Gotta reboot it, was a kernel update.
[20:23] <Annoyed> Thanks for your help.
[20:24] <ioria> no prob
[20:24] <genii> Glad to assist
[20:25] <genii> Sometimes strange things like this happen when files are downloaded midway through a repository update, I've seen it a few times previously
[20:34] <genii> Apachez: Yes, if the image you made does not run the installer, the filesystem.size file should not matter
[20:41] <iffraff> Hello,  I here about an issue I'm having.  I have a laptop with external monitors.  When I step away from my computer for some 10 min, I return and need to log in.  After logging in all of my windows are piled up ontop of each other in a corner.  This does not happen if i simply engage the lock screen.  Only if, whatever happens after some 10 minutes happens.
[20:42] <iffraff> This is not the worst thing in the world but multiply it times 1000 which is how many times I've already gone through it and hair will be ripped out.
[20:43] <iffraff> does anyone have any ideas on how I can preserve my window placement?
[20:46] <ioria> iffraff, no idea, try to disconnect the external monitors and wait 10 mins
[20:46] <iffraff> yes it collapses when it's just the laptop too.  now that you mention it
[20:47] <bprompt> iffraff:  is clearly some setting on the window manager, that on the screensaver timeout it comes back in "Cascaded Windows" mode
[20:49] <ioria> iffraff, what release and what DE ?
[20:49] <iffraff> It's not very consistent, sometimes all the windows are piled up somtimes only most of them
[20:49] <iffraff> ubuntu 18.04
[20:49] <bprompt> iffraff:  cheap answer, change the window manager =), I run Kubuntu, so I don't run gnome window manager, but I assume you can poke around the settings with a dconf editor or other gnome configuration tooo
[20:49] <bprompt> s/tooo/tool/
[20:49] <genii> This was a known problem on Unity
[20:50] <ioria> iffraff, did you install the Cascade win extension ?
[20:50] <iffraff> I'm not familiar with those two tools, do I apt install them?
[20:51] <ioria> nope
[20:51] <iffraff> ioria: I didn't intentionally install cascade ext.  I can check thoguh
[20:52] <iffraff> cascade is turned off
[20:52] <ioria> iffraff, but you have it ?
[20:53] <iffraff> actually I searched for in the gnome ext sight, it showed up with the "on/off" toggle on off, but now that I look at my "Installed ext" I don't see it there, so I'm gonna say no
[20:54] <iffraff> so what other windows managers are available for ubuntu?
[20:54] <bprompt> iffraff:  *nix are well know to have a plethora of window managers, pick whichever
[20:55] <ioria> iffraff, you have an interesting issue, but i'am leaving. gl
[20:55] <bprompt> s/know/&n/
[20:55] <bprompt> iffraff:  but there are many, you can check the repositories, some lightweight, some very featured and fancy, is a matter of choice, I use LXQT
[20:56] <genii> iffraff: Are you using Compiz? If so then it can fixed regardless of DE with settings in CCSM
[20:56] <iffraff> bummer well this is not going away so I'll probably be back
[20:56] <iffraff> genii: I have compizconfig, is that what you mean?
[20:56] <genii> ( as per second answer here https://askubuntu.com/questions/493824/remembering-window-positions-and-preferrably-sizes-too-in-ubuntu-14-04 )
[20:57] <genii> iffraff: It's probably a Compiz issue then, I'd try the suggested fix I just gave
[20:57] <iffraff> it's for 14.04 you think it may still apply?
[20:58] <genii> If you're running compiz, then yes, it's still relevant
[20:58] <iffraff> ok, cool.  I'll give it a read
[21:05] <Praeceps> Hey, is there anyway to get the menu that comes up during an do-release-upgrade to come back up again? I need to re-evaluate some configuration choices
[21:07] <leftyfb> Praeceps: you mean the "Software & Updates" application?
[21:08] <genii> Praeceps: Unfortunately not
[21:08] <Praeceps> Looks like some sort of apparmor/libvirt change is causing me issues where libvirt doesn't have permission to kill the qemu pids
[21:09] <genii> leftyfb: No, he means the do-release-upgrade command, which asks at points about merging , keeping, or installing new config files during it's run
[21:09] <Praeceps> genii, Yeah, that
[21:09] <sarnold> Praeceps: are you getting DENIED lines?
[21:09] <Praeceps> sarnold, Yeah - audit: type=1400 audit(1575406918.331:82): apparmor="DENIED" operation="signal" profile="libvirt-e297da73-c8b1-4120-9b0d-0a92ab1ec86c" pid=3753 comm="libvirtd" requested_mask="receive" denied_mask="receive" signal=term peer="libvirtd"
[21:12] <Praeceps> Results in libvirt not being able to fully shutdown the VM
[21:12] <Praeceps> Have to kill the process manually then destroy the vm
[21:12] <Praeceps> Right pain
[21:14] <sarnold> Praeceps: hmm. this is pretty old, the conclusion may be incorrect https://alioth-lists.debian.net/pipermail/pkg-apparmor-team/2018-January/002240.html
[21:14] <sarnold> Praeceps: were you prompted with the 'use existing, install new from maintainer, diff' kind of option for an apparmor policy file for libvirt?
[21:15] <Praeceps> sarnold, Yeah exactly that
[21:15] <sarnold> Praeceps: dang I *hate* those. heh.
[21:15] <Praeceps> Denied it at the time because I had to do all sorts of stuff to get my setup to work but looks like it had an important change
[21:15] <Praeceps> Don't know why tbh
[21:15] <Praeceps> Have ZFS
[21:15] <Praeceps> Could just rollback if I needed too
[21:16] <sarnold> Praeceps: it's *possible* that doing apt-get install --reinstall libvirt  will bring back the prompt
[21:17] <Praeceps> sarnold, Unfortunately not
[21:18] <Praeceps> At least libvirt-daemon
[21:19] <genii> sarnold: dpkg-reconfigure, maybe?
[21:19] <sarnold> genii: does that do the 'changed conffile' dance?
[21:20] <genii> sarnold: It should make a new one based on the answers ( at least if you use -plow )
[21:21] <sarnold> genii: interesting
[21:21]  * genii runs off to answer a phone
[21:21] <sarnold> Praeceps: it feels worth a quick try anyway, dpkg-reconfigure -plow libvirt-somethihng?
[21:23] <Praeceps> dpkg -S says  it's owned by libvirt-daemon-system - doesn't come up with any sort of menu
[21:24] <Praeceps> (with dpkg-reconfigure -plow libvirt-daemon-system)
[21:25] <sarnold> Praeceps: dang. thanks for trying..
[21:26] <Praeceps> I mean I feel like do-release-upgrade has to do the call from something that probably exists already right?
[21:26] <Praeceps> I doubt it's specifically for that
[21:27] <sarnold> Praeceps: indeed, but debian config files are a complicated dance of dpkg having built-in handling for conffiles *and* maintainer scripts to try to work around that complicated handling for config files (note conffiles aren't config files)
[21:27] <jack> help...i'm using "caine", an ubuntu derivative
[21:28] <jack> doesn't have an own chan
[21:28] <jack> so i'm here
[21:28] <jack> bad?
[21:28] <Praeceps> Aha! Got the sucker.
[21:28] <Praeceps> ucf /etc/apparmor.d/abstractions/libvirt-qemu.dpkg-dist /etc/apparmor.d/abstractions/libvirt-qemu
[21:30] <sarnold> Praeceps: YEESSSSS
[21:31] <Praeceps> "update configuration file" - makes sense I guess :L
[21:31] <sarnold> I'm noticing that the profile name changed from /usr/sbin/libvirtd to libvirtd too :/
[21:31] <Praeceps> Yep
[21:31] <sarnold> this may drastically complicate things ..
[21:31] <Praeceps> Potentially I don't know much about apparmor
[21:34] <Iarla> Man.. I changed a setting for my touchpad and made the machine unbootable :) It's fixed now again, but I can't believe something like adding an invalid setting to xorg.conf.d/51-synaptics-quirks.conf could cause that much trouble.
[21:35] <sarnold> Praeceps: so.. here's my current guess.. aa-status ought to report a bunch of profiles for running VMs
[21:40] <sarnold> if Praeceps returns: the idea is to add signal (receive) peer=libvirtd, signal (receive) peer=/usr/sbin/libvirtd,  rules to the profiles in use by the running VMs, apparmor_parser --replace those profiles, and then once that's going, it ought to be possible to stop VMs, restart libvirt, and then resume all the VMs again
[21:47] <guntbert> jack: we don't support derivatives here
[22:23] <corshmock> Does anyone suffer with Ubuntu (Studio) 18.04 and the mouse left and right click pack in?  The mouse still hovers around no problem, but no clicking available.  Nothing but a reboot will fix it temporarily.  Googling tells me it's a known issue, but I haven't seen a proper fix for it yet.  Albeit after some updating it's not as bad, but surely someone has a once and for all fix for this?
[22:35] <Rabid_Raven>  install kubuntu 19.10 with default settings, set up my second hard disk manually and it works with the proper settings in fstab, had sleep problems and assumed it was the result of a small swap file (1GB) in the main hard disk so I created a 24GB partition on the second hard disk, updated the swap file settings and sleep _STILL_ doesn't work. why doesn't sleep EVER work in linux?
[22:35] <Rabid_Raven> actually... it's more like wake. why doesn't _wake_ ever work
[22:57] <dwigton> Periodically, on an x1 carbon gen 6 running 18.04, after a s3 sleep state, all windows are closed. It seems to happen more often with periphials plugged in. Is this an OS thing or Gnome thing?
[23:02] <akk> dwigton: Not sure what all windows closed corresponds to, but on my gen 7, sometimes when I come out of sleep, X gets confused and just gives a black screen
[23:03] <akk> dwigton: and if I try ctrl-alt-Fn, X dies and dumps me back at the console prompt (I don't run a DM, with a DM it would probably give a login screen).
[23:03] <akk> oh, or maybe with a DM it keeps you logged in and restarts X, in which case it might indeed look like all the windows disappearing.
[23:05] <akk> dwigton: For ubuntu I filed bug https://bugs.launchpad.net/bugs/1852158 which links to a couple other probably related bugs in the freedesktop and redhat bug systems.
[23:05] <akk> Seems like Fedora might have a fix for it, but there's been no response on the ubuntu bug.
[23:06] <akk> It's pretty annoying, just happened to me a few hours ago in the middle of a meeting.
[23:11] <sarnold> I'm not sure if I've ever used s3 state on my x1c6
[23:12] <sarnold> I had a very frustrasting few weeks when I was using a usb-c connected monitor to power the thing, every now and then the PCI bus would die and all devices would power cycle and the monitor would turn off and then back on and it was the most annoying thing ever
[23:12] <sarnold> I replaced the dock and that seemed to sort it out
[23:13] <pragmaticenigma> akk: there isn't any movement on it, because it hasn't been resolved in the other referenced bug trackers. Intermittent issues are some of the hardest bugs to fix. My recommendation is to not allow the system to "sleep" and especially do not transition on/off the docking station when the machine isn't in a powered off mode or fully powered on.
[23:13] <akk> I have a usb-c dock and it's a bit flaky, sometimes the monitor disappears for a while, but I thought it was a bad connector.
[23:13] <sarnold> dwigton,akk, try fwupdmgr to install firmware updates, there's a chance that updates have addressed issues, I've heard there's some issues with lenovo firmwares that have been sorted out with gen7 machines, not sure if they have pushed fixes back to gen6 yet or not
[23:14] <akk> Mine's a gen7 and I think it said there weren't any available firmware updates (it's pretty new), but I'll check again.
[23:17] <sarnold> my (unsubstantiated) guess was the monitor couldsn't supply enough power over usb-c, it cut out every time the machine had to do any "heavy lifting", even if it wasn't actually all that heavy
[23:17] <akk> pragmaticenigma: The last nontrivial comment in the redhat bug says it was fixed  there, and the freedesktop bug is marked fixed.
[23:17] <akk> Agreed on intermittent issues being difficult, of course.
[23:18] <akk> What's the alternative to sleep? Hibernate, I guess? I used to do that ages ago but it was super slow (and would be worse with this machine, where it takes ages just to get to the grub screen).
[23:19] <sarnold> I leave my laptop powered on and running all the time, except when I travel, when I shut it all the way down whenever I walk away from it, so that the full disk encryption provides some value
[23:20] <dwigton> sarnold: I have run all the firmware updates through the software center.
[23:20] <pragmaticenigma> akk: reading through both tickets referenced, they were not fixed. They were closed as in one, the original author reported lack of time to further pursue the issue
[23:20] <pragmaticenigma> akk: the other was closed because it was thought to be resolved by not using the i915 driver
[23:21] <sarnold> dwigton: alright, I think that ought to be the same set of things. bummer, I was hoping for an easy win :)
[23:22] <dwigton> akk: sorry, I got distracted. But when I log back in all of my windows, firefox, terminal, etc are just .. not running anymore. No black screen, just Gnome shell as if I just booted.
[23:22] <akk> Oh, you're right, pragmaticenigma, it's a workaround, not a real fix. Guess I should try the workaround.
[23:23] <pragmaticenigma> akk: I second sarnold's technique. I always power off machines when transporting, and to ensure encrypted data can't be recovered because a hibernation/memwory swap file contains the decryption key in an unsecured portion of the disk
[23:23] <dwigton> It is mostly annoying to have vim close. Though it seems to do so fairly cleanly.
[23:23] <sarnold> dwigton: *weird* :/
[23:24] <akk> Shutting down every time I transport the computer or go away for a few hours seems like a huge inconvenience compared to every other Linux machine I've had.
[23:25] <dwigton> sarnold: it seems to b pretty random too. But higher frequency with an external keyboard and almost guarnteed with external monitor on the hdmi port.
[23:25] <jeremy31> akk, clone the HDD to a SSD
[23:25] <akk> It's an SSD already.
[23:26] <sarnold> heh, gen7 x1c is nvme
[23:26] <sarnold> way faster than ssd
[23:26] <sarnold> boot still takes an eternity though :)
[23:26] <jeremy31> I get under 15 second boot times from my SSDs, not sure how much that can be inconvenient
[23:26] <dwigton> Yeah, I am pretty sure my gen 6 is under 20 seconds.
[23:27] <akk> The actual boot is fast, it's getting to the grub screen that takes forever. Maybe it's doing a RAM check or something.
[23:27] <jeremy31> akk, using LVM?
[23:27] <akk> no
[23:27] <akk> This is something happening at the bios level.
[23:28] <SimonNL> no idea how long my boot takes I press power button and walk away
[23:28] <akk> I don't think the bios would know about LVM even if I used it?
[23:28] <jeremy31> akk:  is the SSD the first boot device?
[23:28] <akk> yes, first and only
[23:29] <sarnold> BIOS setup routines are never real quick; I've heard of some servers haing five-minute boot times cut down to *seconds* when the bios is replaced with coreboot or something similar
[23:29] <akk> Basically, it has a black screen with underscore cursor for what seems like an eternity, then the bios info screen flashes for a second, then a half-eternity, then the grub screen.
[23:30] <dwigton> maybe you are an android and mere seconds feel like eternity to you?
[23:31] <cnnx> is there a way to find out if the optical S/PDIF Port of this card would work under ubuntu before i order it?
[23:31] <cnnx> https://www.bestbuy.ca/en-ca/product/startech-startech-com-7-1-channel-sound-card-pci-express-24-bit-192khz-pexsound7ch/10433398
[23:31] <akk> I haven't timed it, and should; I'd guess 20-30 seconds for the first part, maybe 8 seconds for the second part, then 5-10 seconds for ubuntu to boot.
[23:31] <jeremy31> akk: any DVD drive?
[23:32] <sarnold> akk: cripes that's slow
[23:32] <sarnold> I'm just whinging about 20-ish seconds..
[23:32] <sarnold> or at least it feels like 20ish seconds, I've not measured it..
[23:33] <sarnold> cnnx: if you can find pci device identifiers for the thing, maybe..
[23:33] <cnnx> sarnold: ok
[23:33] <akk> jeremy31: No, nothing like that.
[23:34] <dwigton> I personally think ram should have a 1-1 flash mapping to allow shutdown and bootup in a fraction of a second.
[23:34] <sarnold> cnnx: you could try this too https://linux-hardware.org/index.php?view=search