[10:52] <znf> Hi
[10:53] <znf> How exactly do you add a certificate to the trust root in Ubuntu?
[10:54] <znf> context: we have some clients who are running old crap (16.x) and since yesterday with the expiration of DTS's X1, obviously their app can't connect to our API anymore (as we use LE)
[10:54] <znf> I've deployed a 16.04 VM to try to reproduce and/or provide instructions on how to get the new root accepted, but I'm failing on it
[11:13] <ogra> znf, https://ubuntu.com/security/notices/USN-5089-1
[11:13] <znf> yeah, that's >18.04 tough :)
[11:15] <ogra> well, the linked bug lists xenial as fix released too
[11:16] <znf> ah, didn't notice that, thanks
[15:13] <xnox> znf:  enable ESM and upgrade.
[15:13] <xnox> znf:  Ubuntu 16.04 has all of letsecnrypt stuff fixed in ESM (gnutls, openssl, ca-certificates) https://ubuntu.com/security/esm
[17:22] <Odd_Bloke> Hey folks, when we're performing maintenance on one of our machines, we'd like to take that opportunity to apply apt upgrades.  Specifically, for consistency with how it happens at other times, we'd like to manually run unattended-upgrades.  I know that it's split into separate fetch and install steps: does `unattended-upgrade` run both of those at once, or should we prefer starting apt-daily.service
[17:22] <Odd_Bloke> and then apt-daily-upgrade.service?
[17:26] <xnox> Odd_Bloke:  disabling timers; and running .service units sounds best.
[17:26] <xnox> Odd_Bloke:  but that will not apply everything. i.e. only security; not updates.
[17:27] <Odd_Bloke> xnox: To be clear, we do want it to also run when the timers kick it off: this is just opportunistic to take whatever package install cost we might have waiting while a machine is already in maintenance.  (So I assume we can just leave the timers enabled?)
[17:28] <Odd_Bloke> Yeah, we have additional config in there so it does what we want (which is also why we want to run *it*, rather than applying upgrades another way).
[18:17] <JanC> xnox: wouldn't only security vs. also updates depend on the configuration of unattended-upgrades ?
[18:17] <JanC> as in: that's the default, but you can change it?
[19:20] <Odd_Bloke> Yep, you can configure it (and we do): xnox was describing the default behaviour.


[00:27] <Keybuk> mbiebl: the shutdown messages are normal
[00:27] <Keybuk> that's unrelated
[00:27] <Keybuk> at -> atd - good catch
[00:27] <Keybuk> udev-finish - good catch
[00:28] <Keybuk> the directly after upgrade stuff isn't ideal
[00:28] <Keybuk> not sure why you have a running dbus though
[00:28] <Keybuk> but it's because those are services are can't shutdown, so we can't "inherit" them
[00:28] <Keybuk> they're still running under sysv conditions until you reboot
[01:23] <mbiebl> Keybuk: I'd also suggest to remove dbus-reconnect.conf and run telinit q in dbus.conf's post-start
[02:23] <Keybuk> mbiebl: doesn't work ;)
[02:25] <ion> Why is that?
[02:29] <Keybuk> because telinit q reloads all the configs
[02:29] <Keybuk> and throws away the accumulated "start on" events ;)
[02:29] <Keybuk> it was a bad choice for dbus reload, in hindsight
[02:30] <ion> So, there should be a way to tell Upstart just to reconnect to dbus?
[02:30] <Keybuk> yes
[03:39] <ion> keybuk: rc-sysinit starts again if one runs mountall from a system that has already booted up. Any way to fix that?
[03:40] <ion> The job starts running rcS scripts
[04:11] <ion> keybuk: Why is anacron a task?
[06:35] <PuffTheMagic> can someone point me to some docs on what events i can emit
[06:36] <PuffTheMagic> like how do i start stop services
[06:36] <PuffTheMagic> using initctl emit
[06:37] <PuffTheMagic> or like... cant i get a list of services this way?
[06:39] <mbiebl> ion: anacron is not a daemon
[06:40] <mbiebl> It's triggered by cron (and other event sources)
 and throws away the accumulated "start on" events ;)
[06:43] <mbiebl> Do you intend to approach it differently then or keep the current solution?
[13:33] <ion> mbiebl: Ah. In that case, ‘task’ is right, but something else must be done to prevent ‘start anacron’ from blocking for ages, especially during the installation of the package.
[13:39] <Keybuk> oh, is that what it's doing?
[13:39] <Keybuk> hah
[13:39] <ion> to053953 < ion> keybuk: rc-sysinit starts again if one runs mountall from a system that has already booted up. Any way to fix that?
[13:39] <ion> to054029 < ion> The job starts running rcS scripts
[13:40] <Keybuk> no, I mean anacron
[13:41] <ion> I mean, that’s another issue i talked to you about.
[13:41] <Keybuk> oh
[13:41] <Keybuk> Don't Do That Then
[13:41] <ion> Hehe
[13:42] <Keybuk> mountall will emit events like filesystem, which will start other bits
[13:42] <ion> Indeed
[13:42] <Keybuk> I guess rc-sysinit should have "start on startup and filesystem"
[13:42] <Keybuk> because it should be only run-once
[13:45] <ion> I think there’s a slight design problem with my fsck-queue patch. I’m just installing a virtual system to test. If there’s a LVM VG that resides on /sda1 *and /sda2, the code will probably output {"8:0", "8:0", NULL} which then will get both locked (i.e. added to the lock hash).
[13:46] <ion> That is, i’ll have to make the get-physical-dev-ids code not output duplicates.
[13:52] <Keybuk> *nods*
[14:43] <Keybuk> mbiebl: you were saying something about /forcefsck not working ?
[14:44] <keesj> so anybody has a good dbus-deamon starting service?(that waits for the service to be started?)
[14:44] <Keybuk> keesj: ?
[14:45] <Keybuk> not sure what you mean
[14:45] <keesj> something that checks if the daemon is ready
[14:45] <Keybuk> you don't need to
[14:46] <keesj> I need to sue fork for that?
[14:46] <Keybuk> right, "expect fork" and "exec dbus-daemon --system --fork" are sufficient
[14:47] <keesj> thanks
[14:48] <Md> Keybuk: I have noticed myself as well that /forcefsck does not work since I switched to upstart
[14:48] <ion> Ah, Mount *mnt isn’t nih_alloc’ed. No wonder it segfaulted. :-P
[14:58] <sadmac2> Keybuk: Yesterday you said that in the expression on foo started that started was a sub-state of foo (or sub-job or whatever)?
[14:58] <sadmac2> Keybuk: I was wondering if you'd thought of a way to create more of these sub-states
[14:58] <sadmac2> in terms of syntax etc.
[15:00] <Keybuk> syntax is the wishy bit
[15:00] <Keybuk> but yes, you can create them
[15:00] <Keybuk> you can also create them deliberately inside logs
[15:00] <Keybuk> err inside jobs
[15:00] <Keybuk> e.g. apache logrotate
[15:01] <keesj> I have an other meta physical question, suppose I have a dbus server that I want to launch using dbus activation, would'nt it be nice if is wat a upstart server?
[15:01] <keesj> service
[15:02] <Keybuk> yes
[15:02] <keesj> (so I have respawn and such)
[15:02] <Keybuk> it's relatively trivial to patch d-bus to use Upstart to start services
[15:03] <sadmac2> Keybuk: heres a few thoughts then: Suppose the existence of a stanza called "exclude" which takes as its argument a few sub-states. It prevents those sub-states from being true at the same time
[15:04] <Keybuk> why would you want that?
[15:04] <Keybuk> and how would such a thing be resolved?
[15:04] <sadmac2> Keybuk: if you tried to start one state it would stop any of the others in the list
[15:04] <sadmac2> Keybuk: the "why" I'm getting to :)
[15:04] <Keybuk> isn't that the same as "while not <state>" ?
[15:04] <Keybuk> starting that implies that <state> has to be stopped
[15:05] <Keybuk> (for the same reason that starting "while <state>" implies that <state> has to be started)
[15:05] <sadmac2> Keybuk: for two states yes. for N or more its a bit more difficult. Plus this is a push maneuver. It implicitly /makes/ it true
[15:05] <Keybuk> assuming you're talking about the physical "start" command
[15:05] <Keybuk> which is the only case where we want that kind of behaviour
[15:05] <Keybuk> I don't think we ever want auto behaviour like that
[15:06] <sadmac2> Keybuk: ah, but we do, let me continue
[15:06] <Keybuk> could you explain on the ML?
[15:06] <Keybuk> I'm really busy at the moment
[15:06] <sadmac2> Keybuk: sure. It'll be out of context there since we started the discussion here, but that's our fault to begin with anyway :)
[15:07] <Keybuk> you can provide context ;)
[15:09] <sadmac2> Keybuk: not to mention I'll see you in two weeks anyway :)
[15:19] <Keybuk> indeed
[15:34] <ion> keybuk: Okay, now everything seems to work – i have tested the fsck queue as well (in a virtual machine). Patches updated.
[15:35] <Keybuk> awesome
[15:36] <ion> Actually, i just noticed a missing nih_assert that should be there. Patches updated again. :-P
[15:36] <Keybuk> ion: can you get rid of the LIKELY/UNLIKELY bits
[15:36] <ion> Okay
[15:37] <Keybuk> also no need to nih_warn() on repeating update_mount_dev_ids
[15:37] <Keybuk> if it's not supposed to happen, assert
[15:37] <Keybuk> if it's safe, just return
[15:38] <Keybuk> actually, it's quite easy for that to be called multiple times
[15:38] <Keybuk> e.g. a disk change for an md device
[15:38] <Keybuk> (would you need to recalculate then, I wonder?)
[15:40] <ion> update_mount_dev_ids is called just before fsck is spawned, and the dev_ids are only used for fsck locking.
[15:40] <Keybuk> it looks like you call it in the udev device watcher
[15:40] <Keybuk> in which case
[15:40] <Keybuk> say the fsck is queued
[15:40] <Keybuk> and a new update for the udev device comes in
[15:40] <Keybuk> you'd need to dequeue the existing fsck (I don't think you even check for it right now)
[15:40] <Keybuk> rescan the ids
[15:40] <Keybuk> then queue again
[15:41] <ion> Do md or lvm partitions ever become visible if they are not ready/fully initialized?
[15:41] <Keybuk> yes
[15:41] <Keybuk> though the watcher thing checks for that
[15:41] <Keybuk> but they can *change* remember
[15:41] <Keybuk> imagine:
[15:41] <Keybuk> boot, mdadm initialised, in degraded
[15:42] <Keybuk> user notices while fsck of / is happening
[15:42] <Keybuk> (md is /var maybe)
[15:42] <Keybuk> and pulls the disk out and replaces it
[15:42] <Keybuk> you'll get a change for the queued md
[15:43] <Keybuk> forcefsck - not sure this hook is right
[15:43] <Keybuk> mountall gets passed this as --force-fsck on the command-line, it doesn't check for the file
[15:43] <Keybuk> removing that should go in post-stop of the conf I think
[15:44] <ion> Ok
[15:50] <PuffTheMagic> so is there anyway to start a service using 'initctl emit'?
[15:50] <sadmac2> PuffTheMagic: yes. initctl emit <something> where the service is defined with start on <something>
[15:51] <PuffTheMagic> oh, but no equiv of 'initctl start <serfvicename>'
[15:51] <sadmac2> PuffTheMagic: no
[15:51] <PuffTheMagic> :(
[15:51] <sadmac2> PuffTheMagic: why?
[15:52] <PuffTheMagic> cause stupid palm dev had to use upstart 0.3.x on the Pre....
[15:52] <PuffTheMagic> so there is no dbus interface
[15:52] <PuffTheMagic> and i wanted to make a gui
[15:52] <PuffTheMagic> for starting stopping services
[15:53] <PuffTheMagic> so i have to make a service that wrapps around upstart/initctl
[15:53] <PuffTheMagic> and relays stuff over dbus
[15:53] <PuffTheMagic> and i wanted to just use events
[15:53] <PuffTheMagic> but i guess i could just call initctl start/stop
[15:53] <PuffTheMagic> just seems ugly
[15:55] <PuffTheMagic> is there a libupstart or anything in the older upstarts that will give me more functionality?
[15:55] <sadmac2> PuffTheMagic: there was a time when such a thing as libupstart existed. Not sure if its still rattling around in that code.
[15:56] <PuffTheMagic> well im using 0.3.8
[15:56] <sadmac2> PuffTheMagic: still.
[15:57] <Keybuk> yes, there's a libupstart in 0.3.8
[15:58] <Keybuk> (it's how initctl talks to upstart)
[15:58] <PuffTheMagic> good
[15:58] <PuffTheMagic> so i can use that to do start/stop :D
[15:58] <Keybuk> sadmac2: *cough* isn't "that code" what you're going to be supporting for the next seven years? :p
[15:58] <PuffTheMagic> haha
[15:59] <sadmac2> Keybuk: 7?  I'm betting on it being around in 2040.
[16:00] <sadmac2> I'll retire before 0.3 does.
[16:00] <Keybuk> you could always ship 0.6 instead :p
[16:00] <Keybuk> then, when you have some problem with it, I probably won't just point and laugh <g>
[16:00] <PuffTheMagic> so the palm devs must have static build initctl then cause i see no libupstart on this userland
[16:00] <PuffTheMagic> how lame
[16:01] <Keybuk> PuffTheMagic: upstart always static-builds initctl and init
[16:01] <sadmac2> Keybuk: you overestimate my authority on these issues. notting is the one to bug. maybe plautrba.
[16:01] <PuffTheMagic> oh
[16:01] <sadmac2> Keybuk: 8ball says don't count on it though :(
[16:01] <sadmac2> Keybuk: I'm support engineering now though. I don't build the product. I just get stuck with the consequences.
[16:02] <notting> Keybuk: didn't land in time (heck, i still haven't seen any patches for integrating it yet, and i do not have time to look at it myself right now)
[16:03] <Keybuk> I guess you're not using it any differently than in F10?  No plans to convert more jobs over?
[16:03] <notting> nope. but i'd assume it's still not a no-op to land it
[16:03] <sadmac2> notting: its missing the state transfer thing, which means the ttys-don't-respawn thing will come back. other than that its not hard.
[16:04] <sadmac2> not a no-op, but not hard.
[16:04] <sadmac2> Keybuk: I wasn't planning on moving anything until 1.0
[16:04] <sadmac2> just gonna have to fiddle with them again then anyway.
[16:04] <sadmac2> 1.0/0.10 depending on how stable we feel.
[16:04]  * Keybuk is moving things now, it's fun
[16:38] <ion> keybuk: Patches updated.
[16:46] <ion> Shutdown seems to be delayed by perhaps 10 seconds by this: http://heh.fi/tmp/upstart-rc-stop-cont-stop-cont
[16:50] <ion> LVM seems to be nice enough to compute which physical partitions each logical volume spans, and only report those partitions in /sys/.../slaves instead of e.g. every single partition the volume group uses.
[18:25] <ion> keybuk: Did you receive the above messages?
[18:26] <Keybuk> ion: I can't answer that question ;)
[18:27] <Keybuk> shutdown: the "10 seconds" is killall5 running
[18:27] <Keybuk> the upstart output is just a side-effect of what killall 5 is doing
[18:27] <Keybuk> some other process is the one not stopping
[18:29] <ion> Ok
[18:29] <ion> Why SIGSTOP?
[19:04] <ion> Can you review the new patches, btw?
[22:26] <mbiebl> ion, Keybuk: who is responsible for mountall?
[22:26] <ion> Dunno about responsible, but Keybuk is the author. :-P
[22:27] <mbiebl> ok, there is a bug wrt to ntfs mounts
[22:27] <mbiebl> I have a ntfs-3g auto mount in my fstab and subsequently mountall fails
[22:27] <mbiebl> which stops the boot process
[22:28] <mbiebl> I think there are two issues here: 1.) failing to mount ntfs(-3g) mount points
[22:29] <mbiebl> 2.) the mount point is non-critical (mounted as a shared partition under /mnt/data)
[22:29] <mbiebl> the boot should not fail because mount failed for a non-critical mount point
[22:34] <mbiebl> Keybuk: and a more cosmetic issue: the output of mount differs between the old-style mounting using the sysv initscripts and mountall
[22:34] <mbiebl> http://pastebin.ca/1561541
[22:50] <mbiebl> Keybuk: btw, is there a bug tracker for this sort of issues or should I send it to the m-l or via pm?


[00:01] <ravage> leftyfb: i did not read the whole conversation but ListenStream=<IP_ADDRESS>:22 results in a lister "<IP_ADDRESS>:22"
[00:02] <ravage> *listener
[00:04] <leftyfb> ravage: ooooo , that did it   (BindIPv6Only=no does NOT work )
[00:05] <leftyfb> "If the address string is a string in the format "v.w.x.y:z", it is interpreted as IPv4 address v.w.x.y and port z."
[00:05] <leftyfb> from https://www.freedesktop.org/software/systemd/man/systemd.socket.html
[00:06] <leftyfb> so basically openssh has just thrown it's hands up and left it all up to systemd, including documentation
[00:08] <leftyfb> ravage: the examples I kept finding were only specifying a port for ListenSteam so I didn't know the ip was an option as well
[00:08] <leftyfb> ListenStream*
[00:08] <ravage> Mystery solved now at least :)
[00:08] <leftyfb> yep, thanks. Good call
[00:11] <pycurious> what is an easy way to create a .deb file for installation that installs a system service?
[00:11] <leftyfb> !packaging | pycurious
[00:12] <leftyfb> ravage: wait, that DIDN'T actually do the trick, I was looking in the wrong place
[00:13] <pycurious> leftyfb: it still looks painfule?
[00:13] <leftyfb> pycurious: YMMV
[00:14] <pycurious> are there any wrappers around that readme - that can easily create deb packages from my source code? I just need to copy some files in the right locations and run systemctl enable
[00:17] <sarnold> pycurious: I've heard good things about https://github.com/jordansissel/fpm
[00:22] <aberrant> wait
[00:22] <aberrant> ListenStream=<IP_ADDRESS>:22 goes in sshd_config?
[00:22] <leftyfb> no
[00:22] <aberrant> oh.
[00:22] <leftyfb> but it doesn't matter, it doesn't solve the issue anyway
[00:23] <leftyfb> openssh doesn't handle the config for this sort of thing (listening on ipv6) when you have socket activation enabled
[00:23] <leftyfb> it's done in systemd as part of the ssh.socket
[00:24] <leftyfb> I'm still trying to nail this down because it's going to become important for me in a couple years when I move to 24.04
[00:24] <aberrant> and there's no way to tell systemd not to listen on v6?
[00:24] <leftyfb> I'm sure there is, I just haven't found it yet
[00:24] <aberrant> ok
[00:24] <leftyfb> but I'm on a mission now :)
[00:24] <aberrant> thank you for looking into it
[00:24] <ravage> leftyfb: what exactly doesnt work with it?
[00:24] <leftyfb> ravage: openssh is still listening on ipv6
[00:24] <ravage> it was ::22 before i made the change and now its <IP_ADDRESS>:22
[00:25] <aberrant> how is it listening on v6 when *there's no v6 interface defined*?
[00:26] <aberrant> I mean, you have to bind to an address and a port. What address is it using?
[00:26] <leftyfb> that won't matter
[00:26] <leftyfb> ok, hold on, that gives me an idea
[00:26] <ravage> https://p.haxxors.com/p89h6076.txt
[00:27] <ravage> am i missing something here?
[00:27] <aberrant> ravage: do a netstat -anop please?
[00:27] <leftyfb> ravage: also lsof -i :22
[00:27] <leftyfb> oh wait
[00:27] <bougyman> um, don't you mean `ss -anop` ?
[00:27] <ravage> thats what i did
[00:28] <leftyfb> aberrant: what release of ubuntu are you on?
[00:28] <bougyman> netstat deprecated last century.
[00:28] <aberrant> bougyman: I'm old-school. I use netstat.
[00:28] <aberrant> leftyfb: 22.10
[00:28] <leftyfb> :/
[00:28] <aberrant> bougyman: only on linux systems, perhaps.
[00:29] <bougyman> afair, ubuntu is a linux system.
[00:29] <bougyman> I can't believe we even still ship netstat.
[00:29] <aberrant> yes, but I use more than linux. :P
[00:29] <aberrant> in any case.
[00:30] <aberrant> what address is this thing binding to in order to listen?
[00:30] <aberrant> and ravage: how did you disable v6 binding?
[00:30] <bougyman> It's listening?  TMTOWTDI
[00:31] <bougyman> well the -l is specifically listening stuff.
[00:31] <aberrant> I appreciate you trying to educate me in linux-specific commands but I've got 30+ years of muscle memory to overcome.
[00:31] <aberrant> just bear with my old-school commands. That's not the problem that needs to be solved right now.
[00:31] <bougyman> You must be one of the remaining ps -ef folks, too :)
[00:32] <aberrant> no
[00:32] <aberrant> ps auxww
[00:32] <bougyman> ps awwfux, here.
[00:32] <ravage> got disconnected
[00:33] <leftyfb> ravage: https://pastebin.ubuntu.com/p/dB78ysHGQV/
[00:33] <aberrant> ravage: what version of ubuntu?
[00:33] <ravage> leftyfb: add an empty ListenStream= line before your override line
[00:33] <leftyfb> TF?
[00:33] <ravage> that should tell systemd to ignore whats in the original file
[00:34] <aberrant> ok, I'm gonna try that. That's two files, right?
[00:34] <aberrant> ssh.socket and override.conf?
[00:35] <leftyfb> ravage: https://pastebin.ubuntu.com/p/G5rxySf3x9/
[00:35] <ravage> mhm
[00:35] <aberrant> ok, my ssh.socket looks pretty much the same as that.
[00:35] <ravage> but if you do edit --full on the socket it works?
[00:35] <ravage> i did not use any override
[00:35] <aberrant> ravage: how did you do this?
[00:36] <ravage> sudo systemctl edit --full ssh.socket
[00:37] <aberrant> ravage: then just the ListenStream= before the other one?
[00:37] <ravage> you only need ListenStream=<IP_ADDRESS>:22
[00:38] <ravage> in the [Unit] section unsetting stuff works like i told leftyfb
[00:38] <ravage> never tried it in the socket section
[00:38] <leftyfb> no matter what combination I try it doesn't work
[00:38] <aberrant> ok, that did it
[00:38] <leftyfb> :/
[00:38] <aberrant> now I need to do the same thing for nfs and its helpers.
[00:39] <leftyfb> aberrant: sudo systemctl cat ssh.socket   # can you pastebin this for me please?
[00:39] <aberrant> leftyfb: sure, but I did exactly what ravage suggested: systemctl edit --full ssh.socket, commented out ListenStream=22 and added ListenStream=<IP_ADDRESS>:22
[00:40] <leftyfb> yeah, I did that too but it's not working
[00:40] <leftyfb> I'd like to see the output
[00:40] <aberrant> leftyfb: https://pastebin.com/e2r5s66j
[00:42] <aberrant> leftyfb: did that help?
[00:43] <aberrant> weird. It's working on one RPi but not the other.
[00:44] <leftyfb> https://pastebin.com/raUrKXBN
[00:44] <leftyfb> this is the output of mine
[00:45] <leftyfb> exactly the same as your minus a space in the commented out line
[00:45] <leftyfb> not working
[00:45] <aberrant> yeah. It's working on my first RPi but not my second.
[00:45] <aberrant> exactly the same.
[00:46] <leftyfb> https://pastebin.ubuntu.com/p/pqm23mP4M3/
[00:46] <leftyfb> something is missing
[00:46] <leftyfb> aberrant: how did you disable ipv6 elsewhere?
[00:46] <aberrant> leftyfb: one sec
[00:47] <aberrant> leftyfb: https://pastebin.com/3vnYgr7A
[00:47] <aberrant> leftyfb (/etc/sysctl.conf)
[00:48] <aberrant> I miss the days of /etc/rc :)
[00:48] <aberrant> at least I knew wtf was going on.
[00:50] <leftyfb> got it
[00:50] <aberrant> share!
[00:50] <leftyfb> hold on, validating
[00:50] <leftyfb> container is acting up now
[00:50] <aberrant> bonus points if you can get nfs and rpc.statd to stop trying to use v6
[00:56] <aberrant> jeez. I got it on my first system but doing the exact same thing on the second and .. nothing
[00:56] <leftyfb> aberrant: I rebooted and it's working. I tried all the different iterations. It only seems to work if you edit with --full.  Missed the start of the debugging session, interested in trying to help.
[00:59] <aberrant> arraybolt3: I think we've got it (at least for ssh). The problem is this: when you disable ipv6 systemwide using sysctl.conf, daemons still "bind" (not sure how) to v6 addresses.
[01:00] <arraybolt3> Oh fun. No clue how to work with that kind of thing, sorry! Glad you're making progress!
[01:00] <aberrant> ssh, nfs, and rpc.statd are three that I know of. We fixed ssh, but nfs and rpc.statd are still binding to v6.
[01:00] <aberrant> it was not intuitive.
[01:01] <aberrant> as soon as I find a distro that is systemd-free that works reliably on an RPi, I'm gonna seriously consider it. I just don't understand these new-fangled features.
[01:04] <murmel> aberrant: devuan has no pi stuff?
[01:04] <arraybolt3> Alright, I know I can google this, but I'd like to get this right the first time and am hoping for someone to lead me through it. I am trying to avoid ever fully rebooting a particular desktop, and would like to simply kexec when I need to reboot. Trouble is this system uses the proprietary NVIDIA drivers, which throw a *fit* when you try to do this. I know the general idea of how to get around
[01:04] <arraybolt3> this (drop down to a text console and shut most everything else off, unload NVIDIA drivers, then kexec), but I don't know the exact procedure and am wondering if someone can lead me through step-by-step.
[01:06] <arraybolt3> (For those wondering why I'm trying to do this, I have a ton of HDDs installed in this desktop and would like them to not ever spin down, plus they add a good amount of time to the boot process. I'm hoping to dodge the delay and spindown-spinup cycle by using kexec.)
[01:07] <aberrant> murmel: devuan's package repo is pretty sparse.
[01:08] <aberrant> might try alpine.
[01:09] <leftyfb> aberrant: systemd is pretty good. Just different. Once you get used to it, it’s better than the old alternatives. In your particular case, it was a matter of openssh throwing it’s hands up for a lot of its configs and handing it off to systemd.
[01:09] <murmel> aberrant: was pretty sure they pull the rest of the packages from debian, as they only edit the systemd stuff
[01:10] <leftyfb> I’m not sure what’s up with this listenstream business and why an override won’t work
[01:10] <leftyfb> Let’s not discuss other distros here please
[01:10] <aberrant> sorry
[01:10] <aberrant> leftyfb: what about nfs and rpc.statd?
[01:10] <aberrant> they're doing the same thing.
[01:13] <arraybolt3> Hmm... I've managed to shut off X, but "sudo modprobe -r nvidia" is just telling me "modprobe: FATAL: Module nvidia not found."
[01:14] <arraybolt3> Same results trying to unload nvidia_drm.
[01:14] <bougyman> sudo lsmod
[01:14] <bougyman> maybe it already unloaded.
[01:16] <arraybolt3> Used lsmod, I was able to see them. I just decided to try rmmod, which appears to have worked.
[01:17] <arraybolt3> Yep, success! NVIDIA seems to be working right after running the final "systemctl kexec". Woot! Screen flashed alarmingly for a bit at first, but it seems to have worked.
[01:17] <arraybolt3> I now see the NVIDIA modules loaded properly.
[01:17] <arraybolt3> And the new kernel is loaded! Alright!
[01:18] <aberrant> wow. That's pretty sick.
[01:18] <bougyman> Sweet.
[01:18] <arraybolt3> It was a lot easier than expected.
[01:19] <arraybolt3> Just logged out, switched to a TTY, ran "sudo systemctl stop sddm", then kexec loaded the new kernel and initrd, rmmod'd all the NVIDIA drivers, then "systemctl kexec" and BAM, screen went nuts and then rebooted properly.
[01:19]  * arraybolt3 now needs to script that whole mess
[01:20] <bougyman> I have no wish to ever do that. It's cool that it can be done, though.
[01:20] <arraybolt3> (This is on Lubuntu 22.04.)
[01:20] <bougyman> I live in the cloud, where everything fails all the time, and you have to be ready for that.
[01:20] <murmel> arraybolt3: hope you share your script ;)
[01:20] <bougyman> Hotpatching kernels is the antithesis of immuatble infrastructure :)
[01:21] <arraybolt3> murmel: Sure thing :)
[01:21] <arraybolt3> Well that was too much fun. I'm gonna write the script now.
[01:25] <arraybolt3> murmel: https://termbin.com/42hic - This assumes you're using SDDM, so this probably won't work on standard GNOME. Log out, switch to a TTY, then run the script and it should speed-reboot your system. It should work even with an NVIDIA card with proprietary drivers. Use caution, don't break anything. I just successfully rebooted my desktop with it.
[01:29] <arraybolt3> I wonder how viable it would be to use kexec to hot-reboot into a different Linux installation. :P Anyway, I'm going far off-topic.
[01:41] <jhutchins> arraybolt3: Lilo will do that.
[01:44] <superkuh> Has development started on Ubuntu 24.04? Alternately is there a different channel where that question would be more appropriate?
[01:44] <murmel> #ubuntu-next
[01:45] <superkuh> Thanks.
[01:45] <murmel> but I hope we are talking 23.04 not 24.04 :)
[01:45] <superkuh> ... I kind of hoped 23.04 was already well on the way.
[01:45] <jhutchins> 25.25
[01:46] <superkuh> lts or nothin' for me.
[01:46] <murmel> sure but the next lts isn't developed for a while superkuh
[01:46] <superkuh> Okay. Thanks again.
[02:12] <Pr070cal_> hi guys
[02:13] <Pr070cal_> i just installed 20.10
[02:13] <Pr070cal_> kubuntu
[02:13] <Pr070cal_> how do i start kde on a new console tty2
[02:14] <murmel> Pr070cal_: did you actually installed an eol release?
[02:14] <Pr070cal_> no 20.10
[02:14] <sarnold> Pr070cal_: that's five months out of date, probably better to just grab a new 22.04 image -- maybe kubuntu -- and install that instead
[02:14] <Pr070cal_> oh sorry 22.10
[02:16] <Pr070cal_> so how do i start kde on 22.10 on a new console
[02:17] <Pr070cal_> sartx wont start a window manager
[02:18] <Pr070cal_> i mean startx
[02:18] <Pr070cal_> startplasma-wayland also wont start window manager ?
[02:18] <Pr070cal_> ctrl + alt + f2 tty2
[02:19] <sarnold> what's your ~/.xinitrc look like?
[02:19] <Pr070cal_> i want to start manually from tty2
[02:19] <Pr070cal_> i used to do it all the time
[02:19] <jhutchins> Pr070cal_: Running multiple X sessions is a somewhat rare topic and you might not find much here.  Possibly better to search the web.
[02:20] <Pr070cal_> but i had to run startx && something else like window manager
[02:20] <jhutchins> Pr070cal_: We used to be a lot closer to multi-user multi-session environments than single user systems.
[02:25] <arraybolt3> Pr070cal_: Does the Switch User feature of KDE work? (Heads up, if you try to sign in to the same user twice it seems to go haywire, I have no idea if it works with multiple users. Save your work and be prepared to reboot before trying this.)
[02:26] <Pr070cal_> ok
[02:26] <Pr070cal_> how do i start a new kde session
[02:26] <Pr070cal_> from console tty2
[02:40] <lord_daemon> I just installed haveged and rng-tools and restarted the machine. Why is entropy still showing only 256. Command: cat /proc/sys/kernel/random/entropy_avail
[02:43] <sarnold> lord_daemon: check your poolsize; it's probably also 256. the entropy_avail can't be higher than the poolsize
[02:51] <lord_daemon> sarnold, cat /proc/sys/kernel/random/poolsize
[02:51] <lord_daemon>  256
[02:53] <lord_daemon> sarnold, sysctl kernel.random.poolsize=4096
[02:53] <lord_daemon> works?
[02:54] <sarnold> lord_daemon: good question, I wonder if there's a maximum size..
[02:56] <xxy> how to fix "libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)" error
[02:56] <sarnold> oh, that's read-only, it'll take a recompile to change it, and it might even require a new algorithm
[03:05] <lord_daemon> I read here that you can't change newer kernels anymore, well, I'll assume it's safe because I don't have the knowledge to compile my own kernel =)
[05:08] <hiya> bluesceada: but it still works fine for me, just that notifications do not work
[05:19] <desktop> Hi, can i remove the text labels on lubuntu on the panel
[05:21] <arraybolt3> desktop: I think so, one moment...
[05:22] <arraybolt3> desktop:
[05:22] <arraybolt3> OK, I have figured out how to do it.
[05:22] <desktop> how ?
[05:23] <arraybolt3> desktop: Right-click on the taskbar, and click "Configure Panel".
[05:23] <arraybolt3> In the window that pops up, click Widgets (it's in the menu on the left-hand side).
[05:23] <arraybolt3> Next, in the list of items that you'll see, click "Task Manager".
[05:24] <arraybolt3> Let me know when you get that far.
[05:24] <desktop> i remove task manager?
[05:24] <arraybolt3> desktop: No, just click it.
[05:24] <desktop> i did
[05:24] <arraybolt3> desktop: Next, there's a column of buttons on the right-hand side of the screen.
[05:24] <desktop> yep
[05:24] <arraybolt3> The bottom-most button should look like a circle with three dots in it.
[05:24] <arraybolt3> Click that button.
[05:25] <arraybolt3> Does this pop up a window "Task Manager Setting" for you?
[05:25] <desktop> yes
[05:25] <arraybolt3> Alright, in the Appearance section, there's an option "Button style". Set it to "Only icon".
[05:26] <desktop> thank you
[05:26] <arraybolt3> You may also want to check the "Window grouping" check box while you're right here, if you're going for a Windows 7-like feel.
[05:26] <arraybolt3> Then you can just click "Close" in both the Task Manager Settings window and the Configure Panel window.
[05:27] <desktop> got it
[05:28] <arraybolt3> 👍 Nice! Glad to be able to help!
[05:43] <cosmicrajiv> hi all. why ubuntu denied install itself alongside win11 if windows encryption in on?
[05:47] <Zaphida> Hi guys, I'm trying to pipe gzip output to adb shell but gzip is just dumping its output to stdout. https://pastebin.com/yeDnCRWd I am trying to flash postmarketOS (a linux distro) to an ASUS intel tablet following this guide https://wiki.postmarketos.org/wiki/ASUS_MeMO_Pad_7_(asus-me176c)
[05:50] <samy1028b> comicrajiv: I'm assuming you mean Windows BitLocker is enabled on your drive?
[05:51] <samy1028b> if so, you won't be able to read/write that drive as it is proprietary Windows encryption.
[05:51] <cosmicrajiv> yes
[05:52] <tomreyn> Zaphida: https://pastebin.com/yeDnCRWd -> "This page is no longer available. It has either expired, been removed by its creator, or removed by one of the Pastebin staff."
 if so, you won't be able to read/write that drive....... so must turn off the windows encryption to install ubuntu alongside it or i have to install ubuntu alone?
[05:52] <tomreyn> Zaphida: are oyou actually doing this on ubuntu?
[05:53] <Zaphida> tomreyn yes
[05:53] <Zaphida> on jellyfish
[05:53] <tomreyn> cosmicrajiv: you will need to turn off / undo bitlocker encryption.
[05:53] <cosmicrajiv> ok
[05:54] <Zaphida> tomreyn strange, let me repost without the binary data.
[05:54] <tomreyn> cosmicrajiv: consider alternatives, too, though, such as using virtualization
[05:54] <tomreyn> Zaphida: see !paste for the pastebin we currently recommend here
[05:54] <tomreyn> (it is not pastebin.com)
[05:54] <Zaphida> !paste
[05:55] <cosmicrajiv> yeah, your are right. i am going to install ubuntu alone and do virtualization of win11 from that.
[05:55] <Zaphida> thanks
[05:55] <cosmicrajiv> going to say good bye to windows:)
[05:57] <Zaphida> tomreyn https://dpaste.com/B8H9367GQ
[05:58] <Zaphida> cosmircajiv goodbye windows it was not a pleasure
yeah;)
[06:01] <cosmicrajiv> why ubuntu 22.04.1 recomments nvidia 525.xx when 515.xx is the production version?
[06:02] <cosmicrajiv> i checked using ubuntu-drivers.
[06:02] <cosmicrajiv> should i follow the recommendation or just install the production version?
[06:04] <tomreyn> Zaphida: while the gzip command certainly returns the compressed version of your image file to stdout, apparently adb shell does not have a way to handle this input. sure, you are running zcat inside the adb shell, but that doesn't mean that adb passes input it gets via stdin into that shell
[06:06] <tomreyn> cosmicrajiv: can you explain the term "production version" in this context?
.. check this page https://www.nvidia.com/en-us/drivers/unix/
[06:07] <cosmicrajiv> now its 525.xx
[06:08] <tomreyn> so?
[06:08] <cosmicrajiv> i was checked yesterday and it shows 515.xx
[06:08] <tomreyn> oh ok
[06:09] <tomreyn> https://docs.nvidia.com/grid/index.html also refers to "december", so it's probably a recent change
[06:09] <cosmicrajiv> so i was just asking that should i always install what ubuntu-devices recommends?
[06:12] <Zaphida> tomreyn strange that the postmarketOS has this as the command to use if fastboot flash fails. well, I don't think I want compressed output, I think need to write the raw data of the image to the device, so I need to output the uncompressed output. I could be wrong
[06:12] <cosmicrajiv> tomreyn: which should i install https://pastebin.com/raw/SGEvtcCw
[06:12] <Zaphida> depends on how it's supposed to be stored. maybe it gets uncompressed on boot
[06:12] <tomreyn> cosmicrajiv: you should use what matches your requirements, is supposedly compatible to your hardware, and is actually compatible to your hardware.
[06:12] <tomreyn> !nvidia
[06:13] <Zaphida> cosmircajiv https://www.youtube.com/watch?v=iYWzMvlj2RQ
[06:14] <desktop> why does my game still runs badly after installing nvidia drivers
[06:15] <tomreyn> Zaphida: the zcat would have undone the compression, if it had received the data through adb
[06:15] <cosmicrajiv> Zaphida: i saw it years ago. but the problem is most of the computer manufacturers still ships with nvidia.
[06:16] <tomreyn> desktop: if you have a lot more details, someone may be able to suggest what to do there
[06:18] <cosmicrajiv> what is the difference between nvidia-driver-525-open and nvidia-driver-525?
[06:19] <tomreyn> the -open one has permissively licensed kernel modules
 so should it contains all the features that the one without "open" contains?
[06:22] <tomreyn> i guess not yet, but that's something nvidia are working on
[06:23] <cosmicrajiv> ok. so if ubuntu-devices recommends that one then i shoul go with the same version without the "open"?
[06:24] <cosmicrajiv> should*
[06:25] <tomreyn> yes, probably. ubuntu-drivers only, initally, follows nvidias' recommendations on what is supposedly compatible to what, so this can still result in booting without graphics, if you're unlucky.
[06:27] <tomreyn> but you can then boot to recovery and, if you have network connectivity, switch to a different nvidia proprietary driver, or, if you don't, switch to nouveau by uninstalling *nvidia* packages
[06:27] <cosmicrajiv> ok
[06:29] <Zaphida> tomreyn well I did this same thing on windows with gzip.exe and I got this: https://snipboard.io/XJdBPT.jpg
[06:29] <Zaphida> err sorry https://snipboard.io/nqd6t8.jpg
[06:32] <tomreyn> Zaphida: you are looking for help with android and adb, which i cannot provide
[06:33] <tomreyn> there are certainly more dedicated channels to this topic, though
[06:33] <tomreyn> !alis
[06:46] <Zaphida> tomreyn yes
[10:36] <jdaviescoates> I really really dislike the screenshot tool that came bundled with Ubuntu 22.04 - is there anyway I can revert to the screenshot set-up that Ubuntu 20.04 had?
[10:36] <administrator__> geh
[10:36] <administrator__> hej
[10:36] <administrator__> sa
[10:36] <administrator__> d
[10:36] <administrator__> af
[10:36] <administrator__> sd
[10:41] <SteelRose> jdaviescoates: try ksnip or flameshot
[10:41] <lotuspsychje> jdaviescoates: the old one is gnome-screenshot
[10:41] <lotuspsychje> think flameshot is good for wayland these days
[10:41] <jdaviescoates> > I really really dislike the screenshot tool that came bundled with Ubuntu 22.04 - is there anyway I can revert to the screenshot set-up that Ubuntu 20.04 had?
[10:41] <jdaviescoates> OK, so I've installed the good old gnome-screenshot which has got me almost  there, but now I also need to revert what happens when I press the PrintScreen button on my keyboard so that it simply prints the screen with no further interaction instead of opening the annoying new screenshot tool which frustrates me no end.
[10:41] <jdaviescoates> Thanks SteelRose lotuspsychje
[10:42] <lotuspsychje> jdaviescoates: check your hotkeys or dconf-editor to edit key values
[10:43] <lotuspsychje> jdaviescoates: theres also an app input-remapper that will allow you to change keys
[10:43] <jdaviescoates> thanks lotuspsychje I'll have a poke around
[11:01] <whysix_> Is there any way to disable cloud-init on initial boot? Seems to be stuck and I just want to provision this manually over KVM its the 22.04 LTS release.
[11:08] <whysix_> I can see port 22 is open on the box but I cant actually ssh into it.. I havent set any keys or anything
[11:09] <EriC^^> whysix_: ssh -vvv might help to see why
[11:10] <whysix_> well it has no keys
[11:10] <whysix_> its an ubuntu live iso
[11:10] <whysix_> 22.04
[11:10] <whysix_> I just want it to run a regular install lol
[11:13] <EriC^^> ah, did not know it's an installer
[11:13] <whysix_> this should be the easy bit lol
[11:13] <whysix_> i just want rid of this cloud-init shit
[11:33] <vincenzo> hello, I am trying to debug why at some point, under a number of simultaneous login attempts in the order of thousands, my ubuntu server became totally unresponsive over any tcp port, even after reboot, and only stopping ufw permitted a new ssh login
[11:33] <vincenzo> that was a bit traumatic, is it a default rule of ufw to block all ports under too many connections? I did not know. And also: do such blocks survive reboot? If so how to fix this behaviour?
[11:35] <vincenzo> is there a log of such limits when they are applied
[11:38] <SteelRose> whysix_: https://blog.rylander.io/2020/12/23/how-to-remove-cloud-init-from-ubuntu-server-20-04/ <-- have you tried that?
[11:39] <SteelRose> vincenzo: do you have fail2ban installed?
[11:39] <bob_x1> hello everyone. what is a correct line for main repository in sources.list for cosmic release ?
[11:39] <whysix_> SteelRose, im little confused I dont have a terminal prompt yet
[11:39] <whysix_> is there a way to run this before boot or something?
[11:40] <whysix_> Its just stuck on cloud init... and rotating / \ symbol
[11:40] <SteelRose> whysix_: you can boot into single-user mode, apply one of the changes there and reboot
[11:40] <whysix_> it doesnt fallback to just.. running the iso lol
[11:40] <whysix_> ohhh
[11:40] <whysix_> how?
[11:41] <SteelRose> whysix_: do you have a running system already or are you installing a new one from scratch?
[11:41] <whysix_> new one from scratch
[11:41] <vincenzo> @SteelRose:no I dont have fail2ban
[11:41] <whysix_> its not remote
[11:42] <SteelRose> vincenzo: any firewall up and running? what does the logs say?
[11:42] <SteelRose> whysix_: what do you use to deploy it? ISO image or Infrastructure-as-Code tools, such as Terraform?
[11:43] <vincenzo> SteelRose: yes I had ufw enabled as per default ubuntu-server configuration. I am unsure where to find its log, though
[11:43] <SteelRose> vincenzo: journalctl -u ufw.service
[11:44] <bob_x1> is there a way to download deb packages for cosmic release directly from ubuntu package directory ?
[11:45] <whysix_> SteelRose, just an ISO
[11:46] <SteelRose> whysix_: it's been a while since I used an ISO to deploy Ubuntu but I don't remember seeing that cloud-init stuff when I installed 20.04 LTS on my work laptop... hmm...
[11:47] <vincenzo> SteelRose, I only see start and stop messages there. Are there other means, e.g. direct iptables
[11:47] <vincenzo> does it have a different log
[11:48] <SteelRose> vincenzo: try: iptables -L -v <-- as root, of course
[11:49] <vincenzo> ah yes, but now the firewall is disabled (otherwise I cant connect)
[11:49] <ogra> bob_x1, cosmic (18.10) is long EOL ... upgrade to a newer version (and use LTS if you do not want it to EOL after 9 months)
[11:49] <ogra> !eol | bob_x1
[11:50] <SteelRose> vincenzo: is that issue happening on a regular basis? or only after several connections?
[11:50] <ogra> bob_x1, see the last link the bot posted
[11:50] <bob_x1> ah thanks i will read
[11:54] <bob_x1> ogra: now i have a certificate expired error after apt update command
[11:54] <bob_x1> is it possible to ignore this error ?
[11:54] <bob_x1> currently it is not critical
[12:08] <vincenzo> SteelRose, on a regular basis I got sort of short blocks that led me to further investigation
[12:08] <vincenzo> Further investigation was in the form of "watch -n 1 iperf ..." which led to a permanent block
[12:23] <SteelRose> vincenzo: perhaps the -n 1  was the culprit ...
[12:23] <SteelRose> vincenzo: I'd install and configure fail2ban as it also provides logs for its activity
[13:14] <whysix_> SteelRose, yeah im stumped.. I just want this page to fk off lol..
[13:14] <whysix_> https://imgur.com/l3fxUtv.png
[13:14] <whysix_> There must be a way to bypass this
[13:15] <whysix_> I installed the last LTS release on boxes and never done this..
[13:15] <whysix_> LOL weird must have heard me
[13:15] <BluesKaj> Hi all
[13:15] <whysix_> last time I ran all night with nothing.. now its timedout and started regular install
[13:15] <whysix_> how odd
[13:21] <SteelRose> whysix_: install 20.04 LTS instead and then do a distro-upgrade...
[13:21] <SteelRose> that's my proposal... I haven't installed 22.04 yet
[13:21] <SteelRose> hi BluesKaj
[13:22] <BluesKaj> hey SteelRose
[13:32] <mybalzitch> my god wayland is just awful
[13:33] <pikapika> mybalzitch, trigger happy development is annoying
[13:38] <pikapika> SteelRose, don't
[13:38] <pikapika> firefox is a snap in 22.04
[13:39] <SteelRose> pikapika: ??
[13:39] <pikapika> if you upgrade to 22.04 you will find firefox is a snap package
[13:39] <SteelRose> pikapika: I'm not upgrading to 22.04 ... and don't use FF anyway :-)
[13:39] <pikapika> oh ok you were answering someone, not describing what you want ot do
[13:40] <SteelRose> pikapika: exactly
[13:53] <johnfg> hi folks
[13:54] <johnfg> I have GSconnect installed on this system (all updates installed), and KDEconnect on my phone.  All's working pretty well, except for mounting the phone on this system.
[13:55] <johnfg> I get no feedback when I select 'mount', but am not seeing the phone anywhere.
[14:01] <SteelRose> johnfg: I use KDEconnect on my phone and on my desktop. All works flawlessly... no idea about what GSConnect is
[14:14] <geosmile> also, how do i record every command used as root into a log file (with timestamp)? - perhaps even ship that file to a central location?
[14:17] <ravage> geosmile: https://nixhive.com/log-sudo-commands/
[14:46] <johnfg> SteelRose: It's the extension in GnomeShell that interacts with KDEconnect.
[14:47] <SteelRose> johnfg: thanks! I googled it right after I showed my ignorance here :-D
[14:48] <Fayn> Hi. My output audio device resets to wrong one after each reboot (or logging out and in again) in Ubuntu 22.04. Is there some place I can use to persistently configure the correct device?
[14:49] <Fayn> And a second issue I have is with Steam snap. In steam games microphone does not work. Push to talk button seems to do nothing and for example in CS:GO there isn't even any option to select input device in audio settings.
[14:49] <Fayn> mic does work elsewhere like in Discord
[14:51] <SteelRose> Fayn: I'd recommend updating/reinstalling the firmware
[14:51] <Fayn> For the record it's samson meteor mic.
[14:58] <rajn> hi
[15:09] <Fayn> SteelRose: you mean the linux-firmware package? or something else
[15:10] <Fayn> that's already up to date
[15:11] <SteelRose> Fayn: fwupdmgr get-updates  <-- try this
[15:14] <Fayn> Looks like that's up to date as well, thanks anyway.
[15:17] <ogra> Fayn, for the steam snap, try #ubuntu-desktop ... the people packaging it are in that channel
[15:18] <ogra> Fayn, could well be that your audio-record plug is simply not connected for the snap ... try "snap connections steam" to see if it is
[15:19] <Fayn> Plug shows steam:audio-record but Slot is "-"
[15:20] <ogra> sudo snap connect steam:audio-record
[15:20] <ogra> that should connect it ... then try again if your mic works in the app
[15:35] <Fayn> ogra: that fixed it, thanks \o/
[15:36] <ogra> Fayn, awesome ... once there is a stable steam snap i think it will auto-connect such interfaces
[15:53] <maxence> hi
[15:54] <maxence> hello
[15:55] <ravage> hello
[15:55] <maxence> where are u from ?
[15:56] <leftyfb> !ot | maxence
[16:31] <blackhawk> I am stuck at login screen. I know there is something wrong with the Xauthority file but i'm not able to access the cli from the login screen.
[16:31] <blackhawk> I can drop to the root shell prompt but can't navigate my way to the Xauthority file from there
[16:33] <ioria> blackhawk, why not ?
[16:33] <blackhawk> Can you please tell me the exact location for the Xauthority file ?
[16:34] <ioria> blackhawk, usually, your home... but it's not used anymore on recent editions
[16:35] <blackhawk> I'm 16.04 but on ESM so supported till 2026. I know 16.04 is abandoned but some help would be appreciated
[16:36] <ioria> ok...
[16:36] <nteodosio> If you are so certaint that the problem is that file, then just rm /home/username/.Xauthority
[16:36] <nteodosio> Then once it fails again post the Xorg log :)
[16:37] <blackhawk> A'right. I found the file in /home/username.
[16:39] <blackhawk> The internet lead me to conclude that being stuck on the login screen was due to problems related to the Xauthority file
[16:40] <blackhawk> I recently had tried to setup a RDP server with xrdp using xfce4 for the environment
[16:46] <leftyfb> blackhawk: if you're on ESM, then you have support through Canonical
[16:48] <leftyfb> blackhawk: that said, you should REALLY upgrade to a release that isn't over 6 years old
[16:48] <blackhawk> through cannonical means ubuntu one advantage, something like that right ?
[16:49] <leftyfb> blackhawk: https://ubuntu.com/support/contact-us
[16:49] <blackhawk> Thank You, appreciate that
[16:50] <jhutchins> blackhawk: Rather than deleting it, rename it.
[16:52] <blackhawk> I check for the permissions of the file and they seem to be just fine.
[16:53] <blackhawk> I think somehow, the package ( DE) ubuntu-desktop had gotten removed. A simple "sudo apt install ubuntu-desktop" solved the problem.
[16:54] <blackhawk> Thanks for the help though, didn't need to reach out to the support in this case :-)
[16:55] <blackhawk> https://www.maketecheasier.com/fix-ubuntu-login-loop/#:~:text=Instead%2C%20press%20Ctrl%20%2B%20Alt%20%2B,provide%20your%20password%20when%20asked. Found this guide really helpful
[16:55] <ioria> that cmd just installs a meta-pkg
[16:57] <forgotmynick> hello chaps. i have a server with oracle cloud. for some reason when the server starts i can't seem to connect to nginx. at first i thought it was something to do with the iptables but after removing each rule until no rules, and when flushing all rules, it still didn't work. however, restarting nginx made it work. so after restarting the server and trying again, this time i only restarted nginx and it worked. consistently
[16:57] <forgotmynick> every time the servers restarted, i have to restart nginx in order for it to work. so when it doesn't work, i can see packets are reaching the server using tcpdump: `16:56:03.424258 IP XXX.XXX.XXX.XXX.50498 > <IP_ADDRESS>.80: Flags [S], seq<PHONE_NUMBER>, win 64240, options [mss 1460,sackOK,TS val<PHONE_NUMBER> ecr 0,nop,wscale 7], length 0 and 16:56:03.424298 IP <IP_ADDRESS>.80 > XXX.XXX.XXX.XXX.50498: Flags [R.], seq 0, ack<PHONE_NUMBER>,
[16:57] <forgotmynick> win 0, length 0` -- what am I doing wrong?
[16:57] <forgotmynick> ```
[16:58] <blackhawk> Another question is that while using xrdp to create a remote server, can I use ubuntu-desktop as the desktop environment ?
[16:58] <ioria> only if logged out
[16:59] <blackhawk> okay, i get that. So hows the idea of getting the ubuntu-minimal meta-pkg and using it as a DE for the RDP server ? Does it still require me to log out of my system ?
[17:00] <ioria> ubuntu-minimal is not a DE
[17:01] <ioria> xfce is a good solution, imo
[17:03] <blackhawk> me using xfce4 imo was the cause I was stuck at the login screen.
[17:07] <Renevant> Hello all! Could anyone point me to any resource that would list expected outbound communications from Ubuntu Server 20.04?
[17:18] <cartdrige> easier is to list running services and check listening ports with netstat.
[17:20] <Renevant> Understood. I was hoping there was a list of typical expected, but if that's the way to go, I appreciate the advice. I'll look into it, thank you cartdrige!
[17:21] <ogra> Renevant, by default there are no open ports on an ubuntu install
[17:21] <ogra> only apps you install later will open any ....
[17:22] <cartdrige> Renevant, sudo service --status-all; netstat -anpo
[17:35] <oerheks> !netplan
[19:30] <RiverGolem1> Hi guys
[19:43] <OpenCZ> test
[19:44] <chraist> OpenCZ: Test test
[19:44] <OpenCZ> that was to test if i could chat here
[19:44] <leftyfb> OpenCZ: proper use of IRC test Failed
[19:45] <OpenCZ> sorry im a bit new
[19:45] <goddard> so just upgraded from 22.04 and it appears my vpn isn't connecting
[19:45] <goddard> how can i see the connection information to figure out what its problem is?
[19:45] <goddard> any way to trigger from the terminal?
[19:46] <OpenCZ> Did you change servers on the vpn?
[19:46] <goddard> no
[19:46] <OpenCZ> try that, that might work
[19:46] <leftyfb> goddard: nmcli
[19:46] <goddard> it doesn't have multiple servers
[19:46] <goddard> leftyfb:  thanks
[19:47] <OpenCZ> goddard: try a different vpn, could be the current one thats the issue
[19:48] <goddard> OpenCZ:  appreciate that help but that isn't the issue
[19:48] <RiverGolem1> what protocol are u using
[19:48] <RiverGolem1> what VPN are u using
[19:48] <RiverGolem1> and how are u connecting
[19:48] <RiverGolem1> Example answer: Private Internet Access VPN, Connecting via TCP Port 80, OpenVPN
[19:48] <goddard> just need to know how to connect to an existing gnome vpn so i can debug myself because 20 questions problem won't work
[19:48] <goddard> its not a commerical vpn provider
[19:49] <RiverGolem1> Are you connecting via Terminal or Network Manager
[19:49] <goddard> before my upgrade i just used gnome shell
[19:49] <RiverGolem1> Ive never used GNome VPN
[19:49] <goddard> now it isn't working
[19:49] <RiverGolem1> Gnome shell as in Terminal?
[19:50] <goddard> its
[19:50] <goddard> nmcli con up VPNNAME
[19:50] <RiverGolem1> Ive never used that vpn method
[19:50] <RiverGolem1> Ive only used openvpn or wireguard
[19:50] <RiverGolem1> in terminal, or GUI VPN apps
[19:50] <goddard> RiverGolem1:  it is openvpn
[19:50] <goddard> using nm
[19:50] <RiverGolem1> Whats nm
[19:51] <goddard> network manager
[19:51] <RiverGolem1> hmmm
[19:51] <goddard> hence nmcli
[19:51] <OpenCZ> Goddard: so openvpn is having issues on ubuntu 22.04 on your part?
[19:51] <leftyfb> RiverGolem1: do you need help with something?
[19:51] <RiverGolem1> MAybe the .ovpn server config file is old
[19:51] <RiverGolem1> leftyfb, not really, just trying to help this mate
[19:51] <leftyfb> goddard: I would start looking through your NetworkManager logs
[19:52] <RiverGolem1> sometimes the vpn config files are re-made to account for new server certificates, settings etc
[19:52] <leftyfb> goddard: journalctl -fu NetworkManager   # watch that while you connect
[19:52] <goddard> yep looks like its just a timeout
[19:52] <RiverGolem1> try downloading a fresh VPN config file
[19:52] <goddard> not as descriptive as i would hope for
[19:52] <RiverGolem1> Do you have an exotic firewall setup or Intrustion prevention ssystem, some endpoint security
[19:52] <leftyfb> RiverGolem1: we try to troubleshoot issues here as opposed to throwing out multiple assumed causes
[19:52] <RiverGolem1> Or custom DNS
[19:53] <RiverGolem1> These are possible issues he could be having
[19:53] <leftyfb> RiverGolem1: there an almost infinite number of possibilities. It's more helpful to troubleshoot the issue as opposed to naming possible causes
[19:53] <OpenCZ> I do got one question though, why does openbox window manager glitch out on Ubuntu ( tried it with both 19.04 and 22.04 LTS ) or is it the configs being funny
[19:53] <RiverGolem1> example "ah yes I am using a custom DNS" which happens to not resolves IPs in a ceterain datacenter, etc
[19:54] <RiverGolem1> II dissagree with your troubleshooting method
[19:54] <RiverGolem1> Im covering all possible options
[19:54] <leftyfb> RiverGolem1: while ignoring the fact that goddard has already stated the issue
[19:54] <RiverGolem1> "just a timeout" isnt the answer
[19:54] <RiverGolem1> "just a timeout" is just the beginning, what is causing the timeout?
[19:55] <RiverGolem1> Network firewall, Local firewall, custom DNS, etc
[19:55] <OpenCZ> ill wait untill this is finished
[19:55] <RiverGolem1> hence my questions
[19:55] <RiverGolem1> 'openbox window manager' how did u isntall it?
[19:55] <OpenCZ> sudo apt-get install openbox
[19:56] <OpenCZ> and the alternative command
[19:56] <RiverGolem1> Can Is ee a screenshot of the glitch
[19:56] <OpenCZ> ill have to reinstall it
[19:56] <RiverGolem1> Perhaps OPenBox just isnt compatable with Ubuntu
[19:56] <leftyfb> RiverGolem1: I prefer to use actual troubleshooting steps like pinging the endpoint or trying to connect to it using a different device. It serves no purpose when you ask "are you running X firewall or Y security or Z DNS or LMNOP etc" There
[19:57] <RiverGolem1> Yeah it does
[19:57] <RiverGolem1> because those questions are open
[19:57] <leftyfb> There's troubleshooting and then there's spitballing
[19:57] <RiverGolem1> I dont have answers yet
[19:57] <RiverGolem1> Thats why I ask
[19:57] <OpenCZ> i dont think its compatability issues, i think its an issue with config because fluxbox and blackbox works well, but i specificly want openbox for themes
[19:57] <RiverGolem1> Try updating your OpenVPN version
[19:57] <leftyfb> :/
[19:57] <RiverGolem1> Usually the stock version is outdated
[19:58] <RiverGolem1> And yes, also ping the endpoint and try to connect from another device
[19:58] <OpenCZ> ill be back
[19:58] <RiverGolem1> on the same, and a different network
[19:58] <leftyfb> goddard: do you require further assistance?
[19:58] <oerheks> he is running latest LTS, so outdated openvpn software is unlikely
[20:00] <RiverGolem1> even latest LTS can have outdated packages, for exaple I had to update libfuse to get appimages to open
[20:01] <OpenCZ> ok im back
[20:01] <OpenCZ> i got the screenshot
[20:02] <goddard> leftyfb: i got the start of something but gotta figure out what changes between ubuntu version maybe before i completely just delete it and try to re-create it
[20:03] <OpenCZ> anyone know if its possible to upload images here?
[20:03] <OpenCZ> because i got the screenshot of openbox glitching
[20:03] <leftyfb> goddard: I would look further up in the logs. A timeout for vpn can happen even when auth or the handshake has failed
[20:03] <goddard> postimages OpenCZ
[20:03] <leftyfb> OpenCZ: imgur.com
[20:03] <OpenCZ> thanks
[20:03] <RiverGolem1> link dat shiz
[20:05] <OpenCZ> this is the link ( imgur ) should work: https://imgur.com/a/ewdrg6b
[20:05] <cbreak> anyone noticed ubuntu 22.10 (kubuntu here to be exact) not booting into X?
[20:05] <leftyfb> cbreak: after an update?
[20:06] <cbreak> I had to roll back to my update state from 2022.12.01, yes
[20:06] <cbreak> I updated a few times since then, but didn't reboot until now
[20:06] <leftyfb> cbreak: look to see if an oracle kernel got installed
[20:06] <cbreak> well, the rollback removed anything that happened :/ Is that a plausible option?
[20:06] <OpenCZ> RiverGolem1: this is the image: https://imgur.com/a/ewdrg6b
[20:07] <RiverGolem1> Firstly, report that problem
[20:07] <RiverGolem1> maybe the devs can see and fix it
[20:07] <sarnold> OpenCZ: YOU BEAT SOLITARE!
[20:07] <RiverGolem1> as the GUI says 'report problem'
[20:07] <OpenCZ> sarnold: ive been trying to beat mines now
[20:07] <oerheks> OpenCZ, this only happens when a system program problem is detected?
[20:07] <sarnold> OpenCZ: hehehehe
[20:08] <RiverGolem1> Try sending this screenshot to the OPenBox devs
[20:09] <OpenCZ> ok, but the error message ive been getting for quite some time and keeps comin back
[20:09] <cbreak> leftyfb: if it happens again, I'll take a look which kernel was booted
[20:12] <OpenCZ> could openbox be having a fit due to the kernel?
[20:13] <OpenCZ> or is it just universal across ubuntu
[20:13] <jhutchins> OpenCZ: Remind us what platform you're running it on?
[20:13] <OpenCZ> ran openbox on 22.04 and 19.04
[20:14] <OpenCZ> kernel version 5.0.0-40-gen
[20:15] <leftyfb> OpenCZ: ubuntu 19.04 is no longer supported. That one should be upgraded regardless
[20:15] <OpenCZ> its for the laptop im using
[20:15] <OpenCZ> its a bit crappy for 22.04
[20:15] <RiverGolem1> as in low power?
[20:15] <leftyfb> 19.04 isn't going to be any better
[20:16] <RiverGolem1> Try Lubuntu, is works great on Low-spec laptops! Im using a Celeron N4500 CPU
[20:16] <leftyfb> OpenCZ: later versions do sometimes improve performance
[20:16] <RiverGolem1> its just barely fast enough
[20:16] <RiverGolem1> To run Windows 11, but Linux is perfect
[20:16] <leftyfb> OpenCZ: as for the 22.04, you should install linux-generic-hwe-22.04
[20:18] <desktop> Can someone help me figure out why my games still run badly after installing nvidia drivers
[20:19] <oerheks> desktop, op what specs, what ubuntu, and what game platform?
[20:19] <oerheks> c/op/on
[20:19] <desktop> lubuntu and gtx 1060
[20:19] <leftyfb> desktop: ( cat /etc/os-release ; uname -a ) | nc termbin.com 9999
[20:19] <desktop> im not sure what is a game platform
[20:20] <OpenCZ> crappy as in fetures usually freeze it
[20:20] <oerheks> poor specs, you do not have memory?
[20:20] <OpenCZ> i just got an RTX 3070
[20:20] <desktop> i have 16g of ram and an i5
[20:20] <desktop> it an old pc but it works fine on windows
[20:21] <leftyfb> desktop: ( cat /etc/os-release ; uname -a ) | nc termbin.com 9999
[20:21] <desktop> leftyfb: https://termbin.com/1vu5
[20:21] <OpenCZ> my laptop specs is an I5 8gb ram with 256GB SSD with on-board graphics and its unable to handel a modern linux distro
[20:21] <leftyfb> desktop: what game is having an issue and how so?
[20:22] <desktop> warframe , it just looks like it doesnt have alot of fps
[20:22] <leftyfb> OpenCZ: that's not true.
[20:22] <desktop> like when im moving it takes alot of time
[20:22] <leftyfb> desktop: how did you instal warframe?
[20:22] <desktop> from steam
[20:22] <OpenCZ> leftyfb: about what
[20:23] <OpenCZ> i tested it a few times on it
[20:23] <desktop> i think it might not even be using my graphics card
[20:23] <leftyfb> OpenCZ: the specs you gave will run a "modern linux distro" just fine. Regardless, it's offtopic here unless you want help with it
[20:24] <oerheks> so the gameplatform is steam..
[20:24] <leftyfb> desktop: open the "additional drivers" utility
[20:24] <desktop> leftyfb: okay, what now ?
[20:24] <OpenCZ> sorry i must of gotten off topic and not realise it
[20:25] <leftyfb> desktop: what does it show you?
[20:25] <desktop> theres a list of all nvidia drivers
[20:25] <desktop> im currently using 515 proprietary
[20:26] <desktop> the game also get stuck on processing vulkan shaders and i have to skip it
[20:26] <leftyfb> then you're probably running through your GPU
[20:26] <leftyfb> desktop: maybe try a steam support chat?
[20:27] <desktop> i think i installed intel drivers somehow
[20:28] <oerheks> unlikely, intel is supported in the kernel
[20:28] <oerheks> and you have latest stable kernel.
[20:29] <desktop> i didnt know that it was supported by the kernel and i installed them i think
[20:32] <desktop> I get an error when im trying to enable 515 drivers
[20:32] <desktop> pk-client-error-quark: The following packages have unmet dependencies:
[20:32] <desktop>   libnvidia-gl-515: Depends: libnvidia-egl-wayland1 (>= 1:1.1.7) but it is not installable
[20:32] <desktop>  (268)
[20:32] <leftyfb> !paste | desktop
[20:33] <desktop> https://dpaste.com/39AVKFLR6
[20:34] <leftyfb> desktop: you should be trying to install libnvidia-egl-wayland1 1:1.1.9-1.1
[20:34] <desktop> how can i install it
[20:35] <desktop> apt install ?
[20:35] <leftyfb> desktop: ( sudo apt update ; apt-cache policy libnvidia-egl-wayland1 ) | nc termbin.com 9999
[20:36] <desktop> https://termbin.com/6wq6e
[20:37] <leftyfb> desktop: cat /etc/apt/sources.list | nc termbin.com 9999
[20:37] <desktop> https://termbin.com/o0sz6
[20:37] <leftyfb> you're missing the main repo
[20:38] <desktop> whats the command to install it
[20:38] <leftyfb> "# Automatically generated by Calamares on 2022-12-05."   you ran something that messed with your repo's and essentially broke your system
[20:39] <desktop> do i need to reinstall
[20:39] <leftyfb> no
[20:39] <oerheks> no, in /usr/share/doc/apt/examples/sources.list   there is the original
[20:39] <oerheks> universe is disabled there, also partner.. but easy to enable again in software updates
[20:40] <desktop> so what do i do
[20:41] <leftyfb> desktop: sudo curl -s https://termbin.com/e827 -o /etc/apt/sources.list && sudo apt update
[20:41] <desktop> sudo curl : command not found
[20:41] <leftyfb> :/
[20:42] <leftyfb> desktop: edit /etc/apt/sources.list and replace it's contents with https://termbin.com/e827
[20:43] <leftyfb> desktop: then I would recommend:  sudo apt update && sudo apt install linux-generic-hwe-22.04 && sudo apt full-upgrade    # then reboot
[20:43] <EriC^^> desktop: sudo wget -qO /etc/apt/sources.list https://termbin.com/e827     perhaps?
[20:45] <ioria> i think partner is gone, for  22.04 and on
[20:46] <desktop> leftyfb: i did wget and it worked
[20:46] <desktop> do i run your command now
[20:46] <leftyfb> ioria: http://archive.canonical.com/ubuntu/pool/partner/
[20:46] <leftyfb> desktop: yes
[20:46] <cambrian_invader> how do I determine what permissions are provided by a snap plug?
[20:47] <desktop> and i reboot ?
[20:47] <leftyfb> desktop: that was the instruction
[20:47] <leftyfb> cambrian_invader: you might try #snappy
[20:47] <ioria> leftyfb, yep, it's 2022 now
[20:48] <leftyfb> yep, hasn't been updated in over a year. I never took the time to notice
[20:48] <ioria> for the record, https://www.omgubuntu.co.uk/2022/01/ubuntu-is-axing-the-partner-repo-nobody-uses
[20:57] <morgan-u2> OK I just started discord, which is never "really" off, and chrome died. So what do I do with the journalctl -f output?  -- I was told to look for something unusual but ask I have said I have no clue what that would look like.  Thanks for any help.
[21:02] <morgan-u2> apparmor="DENIED" is basically all it says, from snap.dicord.com or .... also org.freedsiktop.Tracker3.Miner.Extract' ... requested by ':1.9' (uid=1000 pid=2468 comm-"/usr/libexec/tracker-miner-fs-e " label-"unconfirned"0
[21:03] <morgan-u2> so I was saying it was all apparmor but then I saw that tracker miner thing.  but a real one wouldnt name itself that would it??
[21:03] <morgan-u2> can I find the exact time chrome died so I can look at the jornal then?  --  clearly I am a noob
[21:10] <morgan-u2> restarting chrome, which makes the dock shiver.
[21:11] <morgan-u2> even with only one tab and a Restore pages? dialog box.
[21:42] <goddard> well i've tested and i am able to ping the vpn server, but my connection request times out.  Not sure what changed between 22.04 and 22.10, but must be a version change switched something?  I don't know.  So far the console and logs only report timeout.
[21:43] <leftyfb> goddard: I would try setting up a new VPN connection profile from scratch
[21:44] <goddard> i'm importing from .ovpn file and i did try doing it just how i originally did it
[21:44] <leftyfb> goddard: I did also recommend watching the NetworkManager logs while trying to connect
[21:44] <goddard> no i didn't catch that let me try
[21:44] <leftyfb> goddard: don't import it. Try setting it up manually
[21:44] <leftyfb> goddard: using the nm vpn wizard
[21:49] <goddard> ahh
[21:49] <goddard> journalctl -f -u is much better
[21:49] <goddard> OpenSSL: error:0308010C:digital envelope routines::unsupported
[21:49] <goddard> guessing this
[21:50] <leftyfb> there's probably a cipher that has been disabled
[21:51] <goddard> maybe something similar to this - https://stackoverflow.com/a/74416513/1325621
[21:52] <leftyfb> goddard: https://ask.fedoraproject.org/t/openssl-error-when-connecting-to-vpn-via-networkmanager-fedora-36/21123/9
[21:52] <goddard> yep haha :D
[21:54] <goddard> wow cool
[21:54] <goddard> thanks leftyfb
[21:54] <goddard> it works