[05:25] <lotuspsychje> good morning to all
[05:26]  * Bashing-om Present - but not much count lotuspsychje  .
[05:30] <lotuspsychje> hey Bashing-om
[05:30] <lotuspsychje> bad night huh?
[05:30] <lotuspsychje> lets wake them up a bit
[05:31] <lotuspsychje> i cant stand a sleeping chan lol
[05:32] <Bashing-om> lotuspsychje: Ho kay ,, but I  fear me drooping eyes will be an end :)
[05:33] <lotuspsychje> dont fight the rules of nature
[05:35] <Bashing-om> lotuspsychje: :) When you do ^ , the pay back is something else .
[05:37] <lotuspsychje> yeah
[06:05] <lotuspsychje> morning TJ-
[06:06] <TJ-> g'morning :)
[06:07] <TJ-> LOL... oh you sure know how to make me laugh
[06:10] <lotuspsychje> what?
[06:11] <TJ-> sdfgsdfg | wow, I was damn close to depression. This keyboard is like my penis
[06:11] <TJ-> lotuspsychje | sdfgsdfg: please keep this channel familly friendly
[06:11] <TJ-> Not many better ways to be family-friendly than that! As in, making a family :D
[06:12] <lotuspsychje> lol
[06:12] <lotuspsychje> some guys...need support then put in such info lol
[06:12] <lotuspsychje> dont get it
[06:12] <TJ-> it's an expression born from deep frustration :)
[06:13] <lotuspsychje> seems like it
[06:14] <lotuspsychje> TJ-: your back to irc for a while now?
[06:14] <TJ-> I've been doing some hacking
[06:17] <Bashing-om> good nite guys . gotta get the shut eye .
[06:17] <TJ-> g'night Bashing-om
[06:17] <lotuspsychje> nite nite mate
[06:19] <TJ-> I've just about finished a support script for weechat (IRC client) called "follow". It allows you to track a support conversation in a separate window (it pulls out the messages from the channel so you only see the thread from the people involved in the issue). Avoids getting lost in multiple conversations and comments
[06:20] <lotuspsychje> cool
[06:21] <TJ-> I often get lost or miss comments when there's multiple conversations ongoing. This way, the per-topic buffer is highlighed whenever there's some new topic-related comment
[06:22] <lotuspsychje> use highlights?
[06:27] <TJ-> highlights doesn't really help. messages can have scrolled off-screen; I may be helping several people at once. The main thing is being able to rapidly reread the thread evn it has lasted hours
[06:27] <lotuspsychje> kk
[06:28] <TJ-> and the bonus is being able to share the thread/log it as one conversation, so it will be easy to find it even weeks later and recap wuickly
[07:21] <ducasse> good morning, all
[07:32] <TJ-> g'morning
[07:33] <ducasse> hi TJ-, all well?
[07:33] <TJ-> started early; tiring already :)
[07:36] <ducasse> get tea/coffee! :)
[07:36] <TJ-> Done!
[07:37] <TJ-> been writing a weechat irc client script that follows support conversations in a separate window per topic. a few issues to solve but almost done
[07:39] <ducasse> yes, i just read the backlog. sounds handy :)
[07:39] <ducasse> from what i can tell, it seems logind captures shutdown events like presses of the power button etc - do you know if it's possible to find out where it got those events from?
[07:40] <ducasse> as in, 'was the power button pressed or did someone run systemctl poweroff?'?
[07:40] <TJ-> I'd presume it monitors the input devices
[07:42] <TJ-> "man 8 systemd-logind" and the inhibitor info at https://www.freedesktop.org/wiki/Software/systemd/inhibit/
[07:45] <ducasse> i'll check that link, i'm trying to find out why a machine reboots with no other traceable reason than a 'powering down' event from logind in the journal
[07:46] <TJ-> ducasse: is it a battery-powered system?
[07:46] <ducasse> nope
[07:49] <ducasse> no temperature issues etc either, no other problems. i suspect it might be cat-induced...
[07:49] <TJ-> can you increase the log-level for logind to debug "systemd.log_level=debug" ?
[07:50] <ducasse> i've actually done that after the latest event, now waiting for it to happen again
[07:55] <ducasse> thanks for the suggestions, i think i just need to wait for more log info now. it might be an electrical problem, although i sort of doubt that.
[08:08] <TJ-> the system doesn't have a firmware-programmed sleep timer?
[08:18] <ducasse> there is an option for it in the firmware, but it's not set. it doesn't happen on any schedule either.
[08:23] <TJ-> I was wondering about an idle timeout
[08:25] <ducasse> no, nothing like that
[08:26] <TJ-> does the kernel.log  or syslog show any hardware or network events when it happens?
[08:27] <ducasse> no, that's part of what's weird - the only log message is logind saying "powering down".
[08:28] <TJ-> which log file is that in? I'll check on my systems
[08:28] <ducasse> i got it from journalctl, but hang on
[08:30] <TJ-> is systemd-logind.service doing more verbose logging now, with log_level=debug ?
[08:31] <ducasse> yes, it certainly seems so
[08:33] <ducasse> Sep 27 18:15:40 odin systemd-logind[1284]: System is powering down.
[08:33] <ducasse> that was the last one
[08:33] <ducasse> nothing else around that time
[08:37] <TJ-> nothing in the other logs just prior to that timestamp?
[08:37] <TJ-> You'd think it'd be obvous that the log should report the source of the event seeing as it is a rather critical action
[08:37] <ducasse> i've checked _everything_ in the journal (and everything under /var/log) - nothing
[08:38] <ducasse> yes, i agree, but that's all there is
[08:38] <TJ-> might be worth seeing if pressing the power button causes it, and what logging you get as a result.
[08:39] <TJ-> that way if it happens randomly in the future you know what to look for in the log-file to determine if it is the power button or not
[08:40] <ducasse> i'll try that, but the power button should be disabled by the logind config.
[08:41] <TJ-> good test then :)
[08:41] <TJ-> just don't hold it down and cause a hard power-off!
[08:41] <TJ-> could it have been an automatic upgrade requiring a restart?
[08:43] <ducasse> if it is, i want to track down what does it and nuke it from orbit :)
[08:46] <TJ-> might be worth looking for that timestamp in the /var/log/{apt,unattended-upgrades}/
[08:48] <ducasse> i'll check, but all updates etc are handled manually on that system.
[08:49] <ducasse> i'm thinking of booting it into arch for a while to see if it happens there as well
[08:50] <TJ-> ducasse: is it bare metal?
[08:51] <ducasse> yep
[08:51] <TJ-> server, or desktop ?
[08:51] <ducasse> desktop
[08:51] <TJ-> so something in the DE could be responsible
[08:52] <ducasse> no de, very minimal setup. just i3 and a bunch of scripts.
[11:16] <BluesKaj> 'Morning all
[11:27] <lotuspsychje> good afternoon to all
[11:45] <lotuspsychje> hey BluesKaj
[11:45] <BluesKaj> hi lotuspsychje`
[11:47] <lotuspsychje> dax: can we have an !update trigger where it says users need their systems always up to date?
[12:05] <lotuspsychje> dax: or mention to update on !usn?
[12:30] <Ben64> ubuntu installer frozen :O
[12:31] <lotuspsychje> Ben64: wich version
[12:31] <Ben64> 16.04
[12:31] <Ben64> it's asking if i want to force uefi install, with two options -- go back and continue
[12:31] <Ben64> both do nothing
[12:32] <lotuspsychje> Ben64: singleboot ubuntu?
[12:33] <Ben64> yeah completely new system
[12:33] <lotuspsychje> Ben64: disabled fastboot & secureboot in bios?
[12:33] <Ben64> didn't see either of those
[12:33] <lotuspsychje> sounds like uefi block freeze on partition
[12:34] <Ben64> eh looks more like a software bug
[12:34] <Ben64> button that does nothing
[12:34] <lotuspsychje> legacy
[12:35] <lotuspsychje> i had freezes before on uefi settings partition
[12:35] <Ben64> well maybe i shouldnt have said freeze
[12:36] <Ben64> stuck might be better
[12:36] <Ben64> buttons dont work, system still functions
[12:36] <lotuspsychje> kk can take a long time on partition screen
[12:36] <lotuspsychje> i would retry from beginning
[12:36] <Ben64> it's after that
[12:36] <Ben64> just wants me to confirm what i already told it to do
[12:36] <Ben64> (which i hate)
[12:37] <lotuspsychje> :p
[12:37] <Ben64> like when you go to shutdown -> the computer will shut down in 60 seconds
[12:37] <Ben64> no, do it now
[12:37] <lotuspsychje> sudo halt -p does a good job
[12:38] <lotuspsychje> 16.04 halts pretty quick on machines that i tested
[12:40] <BluesKaj> lotuspsychje, have you noticed lshw-C doesn't seem to work since systemd ?
[12:41] <BluesKaj> googling it doesn't give much
[12:44] <Ben64> got past that dialog box when doing "try ubuntu" then installing
[12:45] <Ben64> 2800MB/s read speed on boot drive :O
[12:54] <lotuspsychje> yay Ben64
[12:54] <Ben64> but now i have to figure out how to make 16.04 usable for me :(
[12:58] <Ben64> or be risky and go for 18.04
[13:03] <lotuspsychje> Ben64: usable how
[13:03] <Ben64> i like things set up a certain way
[13:04] <lotuspsychje> ah
[13:04] <Ben64> which includes notunity
[13:04] <lotuspsychje> beaver daily not out yet?
[13:06] <lotuspsychje> BluesKaj: no issues here with lshw?
[13:07] <Ben64> it is out
[13:07] <Ben64> but not stable
[13:09] <lotuspsychje> cool
[13:09] <BluesKaj> odd lotuspsychje sudo lshw -C network has no output here
[13:10] <BluesKaj> bet it looks for network-manager, but I thought lshw looks at hardware
[13:10] <lotuspsychje> BluesKaj: your on kde right?
[13:10] <BluesKaj> yup
[13:11] <lotuspsychje> does that use network-manager also?
[13:11] <BluesKaj> it used to work before systemd it seems
[13:11] <BluesKaj> yes NM too
[13:11] <lotuspsychje> weird, never noticed here on unity
[13:12] <lotuspsychje> !info lshw
[13:13] <lotuspsychje> BluesKaj: can you check versions/apt-cache policy?
[13:13] <BluesKaj> but I don't use NM, befor susyemd it was the interfaces file and resolc.conf , now it's /etc/systemd/resolved and netplan
[13:13] <lotuspsychje> ah
[13:13] <BluesKaj> resolv.conf
[13:14] <BluesKaj> lotuspsychje, apt-cache policy lshw shows Installed: 02.18-0.1ubuntu3
[13:15] <lotuspsychje> lookin good
[13:15] <lotuspsychje> might be indeed that it searches for nm and doesnt give output?
[13:16] <BluesKaj> weird, lshw is supposed to scan the hardware, why would it look at software?
[13:16] <lotuspsychje> the -network option is the medium it goes trough
[13:17] <BluesKaj> it shows my system hardware with sudo lshw -C system
[13:18] <BluesKaj> well some of it , no mention of ethernet/networking
[13:19] <lotuspsychje> manage doesnt mention network-manager in some way
[13:19] <lotuspsychje> *manpage
[13:39] <BluesKaj> yeah I'm looking at the manpage
[14:01] <lotuspsychje> BluesKaj: would the guest account use netplan or nm as default?
[14:01] <lotuspsychje> otherwise you could test from there?
[14:03] <BluesKaj> lotuspsychje, nm is usually default, not sure but think netplan is for non-nm users
[14:03] <lotuspsychje> kk
[14:04] <BluesKaj> it replaces the static settings users had in the interfaces and resolv.conf files before systemd
[23:31] <TJ-> !hwe
[23:31] <TJ-> !info coreutils