00:30:07 <SponiX> Anyone else use signal-desktop and have it hang from time to time?
00:31:24 <darwin> when I tried signal-desktop it crashed my entire network and entire X GUI
00:50:10 <rtprio> i onl signal on my phone so my employer can't monitor it
01:02:56 <SponiX> glad to see I'm not the only one it is a hot mess for
01:03:11 <Martouf> SponiX: indeed, hangs from time to time and the emoji picker doesnt work
01:22:31 <HER> anyone else get this audio crackling problem after some days without powering down ?
01:22:48 <HER> after a reboot all is good
01:22:58 <HER> not sure whats the root cause
01:25:15 <Martouf> it could be that your sound hardware might actualy be haunted
01:32:05 <HER> could be
01:32:08 <HER> who knows
01:33:07 <Martouf> pretty sure my wifi is also haunted, occasionally it will not work unless my laptop is fully powered off
01:35:23 <SponiX> Martouf: your wifi works when the laptop is fully powered off?
01:35:28 <SponiX> that is strange for sure
01:35:51 <HER> yeah really strange
01:45:26 <Martouf> im telling you haunted!
01:47:23 <HER> Martouf: yeah
01:47:45 <HER> i need an exorcist
04:14:07 <megaTherion> Hi, Im looking for the bhyve equivalent to qemu's (Linux) kvm=off option which basically hides the hypervisor signature to the guest os
05:07:14 <rtprio> megaTherion: i don't think such an option exists
05:15:31 <megaTherion> rtprio: ok so one still needs these nvidia patches
05:16:19 <rtprio> what problem does hiding the hypervisor solve?
05:16:39 <megaTherion> rtprio: that the driver loads, it wont if it detects an VM/hypervisor
05:17:11 <rtprio> oh- that's rather lame of them
05:17:13 <megaTherion> stupid shenanigans but what can you do
05:39:43 <rtprio> save your nvidia cards for nonvirtualized machines, i guess
05:41:06 <megaTherion> rtprio: nah, bhyve just needs some patches - it works on proxmox. I prefer VMs and room/electricity otherwise I'd need 10 machines here
05:43:08 <rtprio> 🤷
05:51:51 <megaTherion> rtprio: https://dflund.se/~getz/Notes/2024/freebsd-gpu/
09:26:44 <getz> Haven't tested it for 14.2 but it applies cleanly so probably works
09:41:50 <[tj]> megaTherion: can you create a bug with a request for this and mention I asked you to do so in the description (thj⊙fo)
09:42:09 <[tj]> I've learned only committers can tag people so you can't assign it to me
11:07:23 <DarkPlutonium> Q. Under what circumstances would ZFS sort of .... revert automatically to a state a few hours ago, post-reboot?
11:11:17 <DarkPlutonium> I'm asking because I had the weirdest situation yesterday. My server was misbehaving weirdly (failed connections, weird SSL errors, etc), so I rebooted it as part of diagnosing the problem.
11:11:19 <DarkPlutonium> After rebooting, it turns out all the changes to a certain (*NOT* read-only) jail from that particular day were simply dropped/reverted, as it they had never happened.
11:11:23 <DarkPlutonium> Turns out the reboot wasn't going to help anyway, as the physical server the VPS was on was overloaded (could that somehow cause it?), but.
11:11:25 <DarkPlutonium> FTR, zpool scrub rapaired 0B with 0 errors.
11:21:57 <SKull> DarkPlutonium: VM hosts having problems leads to all kinds of problems on VPSs
11:22:34 <SKull> DarkPlutonium: my VPS reported defective harddrive sectors becuase of that
11:22:57 <DarkPlutonium> Amazing.
11:23:04 <SKull> DarkPlutonium: and one time i've lost ALL my data because my hoster messed up that bad
11:23:09 <DarkPlutonium> I've had that problem too (with a dedicated, but)
11:23:10 <DarkPlutonium> Damn.
11:23:13 <DarkPlutonium> I had that too.
11:23:23 <DarkPlutonium> Both disks in a zfs mirror failed simultaneously. Fortunately I had backups.
11:23:37 <DarkPlutonium> They're migrating my server, at least.
11:24:33 <SKull> i'm on contabo. i was very pleased with them for over a decade, until they started expanding like crazy
11:24:45 <SKull> now i would not recommend them anymore
11:27:18 <DarkPlutonium> Incidentally, I'm on Contabo too. Ha.
11:30:36 <DarkPlutonium> Used to use Hetzner. Considering going back, despite having some issues historically (including those 2 HDDs)
13:47:45 <neirac> if someone using steam-utils, I tried to compile from ports today and is not working https://pastebin.com/bi5WHqBN , I managed to make it compile passing -m64 but I wanted to confirm
14:00:59 <neirac> where I could find the latest changes in Linux compatibility? I remember that work was being done to allow support for linux coredumps but I don't seem to find that
15:34:00 <skered> Anything interesting (for the better?) change with the pkg builders?
15:34:19 <skered> For the past three days I've been able to run `pkg upgrade` and there things to be upgraded.
15:34:45 <skered> Normally it's at least a couple days between having an updated repo.
15:35:16 <skered> Or are changes small right now such that rebuilds are able to happen within a day.
17:34:24 <voy4g3r2> i have a poudriere question, i currently have it setup to get for jails but the documentation.. that i have found.. talks about disabling the freebsd.org and was curious is there a way to have the jail look at the poudriere packages, if it does not find it .. then default to freebsd.org pkg
17:41:50 <voy4g3r2> never mind.. looks like priority is what i am suppose to use
17:53:26 <ketas> is this feature or bug, nullfs mounting nosuid fs enables suid again?
17:53:30 <rtprio> megaTherion: so you can passthru gpu? man when will this get merged
18:02:29 <ketas> if i mount_nullfs -o nosuid, now it's off but mount happily says (nullfs, local, noatime, nosuid, nfsv4acls) in both cases!
18:07:16 <megaTherion> rtprio: I hope soon, it might work with AMD GPUs already (I've none) but nvidia requires special patches
18:07:35 <megaTherion> also it works with Intel integrated but well who wants those for gaming
18:07:44 <rtprio> were those patches to allow gpu passthru, or obscuire the hypervisor, or both
18:08:19 <megaTherion> afaik there are these change of the hypervisor ident and something to BAR 0 loading .. but Im not too deep into the technical details
18:08:32 <megaTherion> the patch file isn't really that long
18:46:37 <cparman> I can't believe I got xrdp configured on FreeBSD 14 and able to RDP from my Mac Mini to the FreeBSD VM, what a wild trip it has been.
18:46:57 <megaTherion> that hard?
18:47:04 <cparman> It was
18:47:19 <megaTherion> I think I once had such configuration but Im not sure if it was on FreeBSD or Linux
18:47:27 <cparman> for me it was, but for you.....donno
18:47:48 <megaTherion> on one Linux box I simply use vnc, other than that my BSDs are headless anyways
18:50:52 <cparman> It was hard in a sense that I kept mis-typing xrdp_sesman_enable="YES" as xrdp_sesman_enabled="YES" in /etc/rc.conf and Is kept on seeing SSL error messages in the console for hours late last night :)
18:51:06 <rtprio> the whole sesman was annoying with it
18:51:27 <cparman> Late last night my eyes were very tired :)
19:08:43 <thumbs> 22
19:28:14 <polarian> unless I am going mad, I can not see a way to get the licence of a package using pkg-info
19:28:29 <polarian> pkg-info(8) sorry
19:31:51 <polarian> also I was looking for a quick neofetch alternative, and I came across https://github.com/Macchina-CLI/macchina and they list "FreeBSD" here, but yet its not within the port collection...
19:32:05 <polarian> https://www.freshports.org/search.php?query=macchina&search=go
19:32:41 <polarian> Anyone know why before I complain about misinformation, would hate to make a fool of myself :P
19:51:34 <polarian> also for 14.1-RELEASE -p6 is called -p5 :/
19:51:45 <polarian> someone forgot to bump the patch identifier?
19:54:23 <armin> I'm a bit surprised there is no Palemoon/Floorp/Arcticfox browsers in pkg&ports...
19:56:25 <rtprio> i've never heard of those browsers before
19:56:39 <SponiX> polarian: the userland needed the patch and the kernel didn't -- I think - that is why they are mismatched
19:56:58 <rtprio> SponiX: yes, that's right.
19:57:13 <SponiX> armin: ports/packages pretty much just cover the essentials...
19:58:00 <polarian> SponiX: ah, that makes sense
19:58:07 <polarian> armin: you are free to write a port yourself :P
19:58:33 <polarian> if it means that much for you, but as far as I am aware palemoon is written for Linux/Windows and just dropping such a huge codebase onto BSD tends to not go too well
20:01:22 <dvl> polarian: yes, that's how it works and we hope to get it fixed early in 2025.  it's poor for vuln scanning.
20:01:55 <polarian> dvl: "we" you part of the team then?
20:02:05 <polarian> sorry I have no clue who was elected :P
20:02:10 <polarian> apart from d ch
20:02:15 <dvl> polarian: I'm the one complaining.
20:02:18 <polarian> oh...
20:02:57 <dvl> polarian: https://lists.freebsd.org/archives/freebsd-questions/2024-December/006036.html
20:04:25 <dvl> polarian: The issue you mention causes many false positives and alert fatigue. I'd like it fixed. :)
20:04:40 <polarian> dvl: ah so it is considered a bug that freebsd-update doesn't reliable update all patch versions due to it only rebuilding the vuln section
20:04:47 <polarian> ok cool
20:04:52 <polarian> at least its been worked on :)
20:04:54 <dvl> polarian: no, it is the design.
20:05:07 <dvl> polarian: everything is fully patched
20:05:31 <dvl> if you see the -6 in freebsd-version -ukr, you got it all.
20:05:47 <dvl> I know it's confusing and it's awkward, but if we can fix it....
20:06:59 <armin> polarian: doesn't mean too much or something, I could definitely try how far I get :)
20:07:27 <polarian> I see two -p5's and one -p6
20:07:29 <polarian> :/
20:07:50 <polarian> this could be due to me failing to rollback properly as 14.2-release broke my laptop
20:08:34 <polarian> although as I rolled back to a snapshot it shouldn't be a factor
20:08:34 <dvl> polarian: seems right, let me check.
20:09:14 <dvl> [20:08 r730-01 dvl ~] % freebsd-version -urk
20:09:14 <dvl> 14.1-RELEASE-p5
20:09:14 <dvl> 14.1-RELEASE-p5
20:09:14 <dvl> 14.1-RELEASE-p6
20:09:40 <polarian> I have noticed it over and over again since I updated, iirc the dmesg states booting FreeBSD-RELEASE-p5 instead of -p6 and I thought "well thats weird" and just assumed someone forgot to bump the release version
20:09:47 <polarian> yeah same :)
20:09:49 <polarian> ok cool
20:09:54 <polarian> I am not vulnerable or anything, you scared me a second :P
20:10:02 <polarian> the way you said it I thought you meant "all must be -p6"
20:10:54 <dvl> I understand
20:20:19 <kevans_> polarian: yeah, updates only affect the version number for the components they touch
20:22:31 <polarian> kevans_: yikes, that is confusing :(
20:22:52 <kevans_> it gets even worse in kernel-land
20:23:06 <kevans_> iirc a patch that only affects a module that isn't built into GENERIC won't bump the kernel version
20:29:53 <polarian> Isn't that the case in this case :P