00:02:02 looking at xev's output, it doesn't seem to be receiving any XF86MonBrightness{Up,Down} keypresses, it only sees XF86WakeUp upon pressing the fn key 00:39:08 I have a super weird error on pfctl inside the jail. apparently, my pf is still working and I got this error everytime I run: # pfctl -sr 00:39:11 Assertion failed: (elems <= maxelems), function pf_nvuint_32_array, file /usr/src/lib/libpfctl/libpfctl.c, line 147. 00:41:00 rwp, guess what... VT-d was disabled in the BIOS... it was hidden under "System Agent Configuration". The "Enable Virtualization Technology" switch only enabled VT-x 00:41:07 now passthru is working :> 00:47:55 is there any way to stop files from being saved into /tmp from inheriting "wheel" as the group 00:54:52 tm512: who is writing the files? 00:55:18 tm512: you have to map the keys if you want brightness and shit to work 00:56:02 wheel gets inherited regardless of which user writes to /tmp 00:56:41 then it sounds like /tmp has the wrong chmod 00:56:58 drwxrwxrwt 9 root wheel 10 Feb 16 00:46 /tmp 00:59:12 also I *can't* map the keys for brightness control. as I said, only XF86WakeUp gets sent to the X server when the fn key is pressed. no distinct events are sent for the fn+brightness combos 00:59:29 supposedly the firmware is supposed to handle this 01:00:06 the mode and ownership for /tmp is the exact same on my system 01:00:44 `file /tmp` says ? 01:01:01 is the person writing files a member of wheel? 01:02:40 "sticky, directory", and as for being a member of wheel, my main user is, the user I'm running firefox under is not 01:03:42 files saved in /tmp from firefox get browser:wheel and then my main user basically loses write privileges to those files 01:12:48 jbo, Very good! I don't know why those are always vendor disabled by default. 01:13:08 I'm 100% okay with it being disabled by default (and that is what I would expect) 01:13:19 I am not okay with the convoluted graphical menu crap we have nowdays 01:13:44 tm512, In *BSD systems files always inherit the group of the parent directory. In Linux/SysV that is what the sgid bit on directories does. But it's the default for BSD. 01:14:56 tm512, Why doesn't the file ownership stay the owner of the file? 01:15:42 Isn't your browser running as your uid? That's where things are getting disconnected. 01:16:22 And alternately you could change the tmp to be $HOME/tmp so that it is written into a tmp directory in your $HOME and then the group would be your group. 01:17:56 well as I said I'm running firefox as a separate user, as an alternative to FF's lack of sandboxing on FreeBSD 01:20:41 Well, if it is running as a separate user then that separation of user thing is going to be working to keep you separated. :-/ 01:21:38 But anyway the group setting to the group of the parent directory is core BSD behavior since forever. It's part of the landscape. 01:23:24 I added myself to the browser user's group, I guess I need these files to be set g+w by default though 01:23:39 seems like a lot of extra effort 01:24:12 maybe capsicumizer would be a better solution though it seems like development on that has been abandoned, the github repo was archived iirc 01:25:19 bit distracted from this now since I'm back to getting "fault errors on pipe A" when I run picom. I'm starting to get worried that this laptop has faulty hardware, because the laptop is also back to making weird noises at bootup. maybe these things aren't related though and I'm making spurious correlations 01:26:33 The laptop fan might be failing, a typical problem, and at boot the bios usually turns the fan on at high speed before reducing the fan speed. That's the only thing that would make noise on newer machines. 01:27:00 Older machines with a cdrom/dvd would seek the mechanism. If you have one of those. Those are becoming more rare as time goes by. 01:27:15 rwp: it seems to be playing through the speakers 01:27:53 drm-515-kmod pretty reliably gets picom to throw fault errors. I thought things were working fine here on drm-510-kmod, but now it's throwing them 01:28:04 Weird noises through the speaker at boot time? I guess I have heard clicks and such from sound cards as drivers are loaded. 01:29:02 rwp: looks like a safe and effective way to get rid of open source 01:29:42 it's like buzzing/whining accompanied by popping at the end of the tone. one time, it was an incredibly loud tone blaring from the speakers that tbh scared the shit out of me 01:33:27 hernan, It seems like the Law of Unintended Consequences being known ahead of time to everyone else making these Known Consequences but apparently Ignored Consequences by the politicians. 01:34:15 rwp: in another safe and effective measure, they want to get rid of farmers (and the food that peolpe eat, which comes from farmers).. certainly the politicians are not coming up with that nonsense by themselves.. they cant think 2+2. They are receiving orders from above.. the groups that already control everything, every company, every pharma, every main stream media, every politician. Do you know the 3 01:34:22 company names ? that control everything? 01:36:04 so these sounds play when the machine first starts, before the BIOS splash shows, and then again while FreeBSD is enumerating disks during boot 01:36:25 I'm wondering if one of these drives is faulty and messing with the rest of the hardware 01:36:55 the sounds don't show up reliably though, they'll go away for a while before coming back 01:38:32 hernan, I don't believe in conspiracies when incompetence is sufficiently explanatory. 01:39:56 tm512, I can't imagine how a storage device (SSD? Surely not a spinner...) would be able to affect other hardware. Other than by shorting out the power supply which is just about it. It's a power connection plus a SATA data connection. It's not like that can reach out to other parts of the machine. 01:40:34 "Sufficiently advanced cluelessness is indistinguishable from malice." 01:41:18 tm512: picom backend=glx, vsync=true ? 01:42:04 rwp: this laptop came with both a SSD and HDD 01:42:09 might also want to toggle the use-damage flag 01:42:20 I haven't actually used the HDD for anything yet 01:42:23 rwp: its no conspiracy, see for yourself in under 1 minute (the top 3, top 4 holders that own most of these companies) https://finance.yahoo.com/quote/BKNG/holders/ https://finance.yahoo.com/quote/META/holders https://finance.yahoo.com/quote/MSFT/holders https://finance.yahoo.com/quote/AAPL/holders https://finance.yahoo.com/quote/AMZN/holders https://finance.yahoo.com/quote/TSLA/holders 01:42:24 Title: Booking Holdings Inc. (BKNG) Stock Major Holders - Yahoo Finance 01:42:29 https://finance.yahoo.com/quote/PFE/holders 01:42:30 Title: Pfizer Inc. (PFE) Stock Major Holders - Yahoo Finance 01:43:11 topcat001: it's basically the default configuration with shadows and fading disabled, but yes using GLX and with vsync enabled 01:43:28 I might also have glx-no-stencil enabled 01:43:29 tm512, I am a craphound and routinely buy older used equipment. And routinely remove spinning hard drives and replace them with solid state drives. It's a cheap upgrade. Spinning drives on mobile equipment was always problematic but it was just the best available option at the time. Time has passed and now better options exist cheaply. 01:45:36 rwp: I was planning on leaving the HDD in and using it for storing media but if I want to test the hypothesis that something is faulty regarding the storage, I guess my one option right now is to pull the HDD 01:46:17 if the noises persist, I suppose I could load a spare SATA SSD into the space where the HDD was, and clone my FreeBSD install over to it, before removing this M.2 SSD 01:46:29 If you are not yet using it then that would be an easy test. It's going to be making noise at power on reset time as it seeks the head. That might be part of the noise you are hearing. 01:47:11 I need to relocating. BBIAB. 01:47:13 this thing is making noises that do not sound anything like a hard drive 01:48:34 the sound is punctuated by popping noises that sound a lot like the end of an audio buffer not aligning with the phase of a waveform 01:48:40 It's haunted! It's either poltergeists or gremlins. 01:49:46 or like the kind of popping that I think would happen if the waveform had a DC offset? basically what happens when the DAC hits a brick wall where the signal centers back to 0 01:53:05 also if it were the HDD I'd expect to hear it every time the machine starts up or every time I access the HDD while it's idling, but I just don't 01:54:06 it's all in your head 01:54:33 got a video of this though man, my tablet's microphone is terrible. a lot of this sound is just drowned out by noise 01:55:01 computer is wideband emi generator 01:55:06 anyway 01:55:16 platter hdds are still useful though right 01:55:29 maybe not as OS drives. but like for general storage 01:55:53 cheap, don't lose data over time? 01:56:02 actually that sucks in flash 02:03:06 https://www.youtube.com/watch?v=QVndKgz87gg here's a video with the noises, though yeah this mic did not pick it up with the clarity I would've liked. the "fault errors" spam makes a cameo at the start when I reboot the machine 02:03:08 Title: ThinkPad noises - YouTube 02:14:06 tm512: those pops? 02:15:23 i hear something in bg too 02:26:19 ketas: the pops are coming from the laptop, but there's a high-pitched whine between the two pops 02:26:31 hmm mic sucks then 02:26:41 or my phone speaker 02:27:21 the whine isn't unusual sadly :/ 02:28:04 i guess only fix is usb sound card 02:30:10 i heard pssssh pop? 02:30:12 the noise isn't persistent, it only happens right before the BIOS splash, and right as FreeBSD starts detecting disks. and it's intermittent. it doesn't happen on every boot 02:30:18 only 02:31:23 if it happens before bios 02:31:32 that's shitty 02:31:48 but otherwise no noise? 02:34:11 i guess they optimized protections out 02:35:34 not just before BIOS, but when FreeBSD detects disks as well. this doesn't seem like something normal or expected, it seems like something is malfunctioning 02:36:47 it's not disks 02:37:05 it also inits sound 02:37:51 i guess that's that card doing init 02:38:15 not unusual to heard something but still 02:38:22 that's too much 02:38:34 yet, just hw is like that :/ 02:40:27 I know the video is pretty blurry, but the sound shows up precisely when FreeBSD spits out info about the connected disks. it does not seem to coincide with sound hw initialization 02:40:48 hmm 02:41:07 but only on init? 02:42:19 so perhaps on that platform, doing init for storage causes sound to make weird output 02:43:10 again, it's only occasional. it seems like maybe it only starts happening when I haven't had the laptop powered off for a while, but that's speculation from an admittedly small dataset 02:43:20 weird 02:44:12 but only "cosmetic" issue? 02:45:01 this isn't the only noise I've heard it making, either, though the other noises it makes, I think it only happens right before the BIOS splash, and not when FreeBSD is booting. those other noises are louder, sometimes significantly so 02:45:24 one time it blared a sawtooth-wave like tone 02:46:11 I don't know if it's only "cosmetic", I'm worried it's a sign of some serious issues 02:46:50 kinda worried that the GPU fault error messages I'm getting have some relation to this, because those are also intermittent at least on drm-510-kmod 02:47:03 eh 02:47:10 dropped it? 02:47:21 it could be anything 02:48:26 I haven't dropped this laptop at all, but it was a refurb, so I dunno its history 02:49:50 anyway, huh, it did seem like there was a loose screw inside the laptop. when I heard that noise inside of it I thought it was a broken clip. though if that were short-circuiting anything I'm guessing the whole machine would be powering off at random 02:50:06 wtf 02:50:55 you never know actually 02:52:44 had one nos t60, did drop it a bit, nothing immediately, but i guess i just used it up too, i replaced inverter, then it lost bt, losed wifi if moved, lost fp, eventually stopped booting without any reason 02:55:52 i should take it apart and look 03:00:22 I guess to see if the drm fault errors are hardware related, *maybe* I could spin this thing up with Linux 5.10 or 5.15 and see if the same version of picom triggers the same messages? though maybe that's not definitive since the GPU drivers aren't identical 03:03:11 I can't even tell if this loose screw even belongs to this laptop, or if the refurbisher was just sloppy. the bottom cover screws are all accounted for 03:03:33 tm512: See if you can find a teardown video. It'll show you all the screws. 03:14:02 tm512: so this laptop just has some screws loose 03:14:10 :p 03:19:34 tm512: regarding your noise issue, I also use FreeBSD on some older machines, but use a Ubuntu live USB to check the hardware in such cases. 03:20:25 mason: it seems like the screw was supposed to be holding down something that covers the M.2 drive. a heat sink? it's entirely missing in my laptop 03:22:44 topcat001: the noises occur before the BIOS splash even shows, so I already know it's not OS-dependent 03:23:27 I was talking about trying Linux specifically in relation to this issue where picom causes my dmesg to be spammed with fault errors 03:42:02 still getting noises even with the HDD removed, though now they're different 03:54:00 ketas: so closely examining the video, it does seem like the noise is when the sound hardware gets initialized. or at least it coincides with the messages about hdacc/hdaa/pcm 03:54:19 hrm, can I blacklist the driver from even loading in order to test? 03:55:27 i think it's in 03:56:58 also, here's a video that much better showcases the noise though it's a bit more buzzy this time, compared to the first vid: https://www.youtube.com/watch?v=0PB8YesP36Y 03:56:59 Title: more ThinkPad noises - YouTube 03:58:36 iirc there is no way to disable built in module 03:59:58 this noise also plays when I wake the machine up from suspend, though nothing gets printed regarding the sound hardware 04:00:08 what the 04:00:15 ! 04:00:57 I'll see if there are settings in the BIOS to disable the sound hardware entirely. might still play before the splash screen, but if it no longer plays while booting into FreeBSD, that narrows things down 04:01:01 but why use fbsd to fix it 04:01:16 I dunno what you mean 04:01:36 it does same in bios 04:04:13 what I'm talking about is preventing FreeBSD from initializing the sound hardware, see if that shuts it up. if it doesn't, then it probably isn't related to the sound hardware 04:14:25 tm512: ah ok so the noise is an electrical issue it seems. 04:15:49 tmiw: which DDX driver are you using in X? 04:16:12 sorry tm512 ^^ 04:17:33 BTW even in Linux I sometimes get the fault errors, but they are very rare. Maybe one every couple of months. 04:17:48 pretty sure I'm using modesetting, though I did try intel without success 04:18:06 which intel igpu is this again? 04:18:10 I dunno that I tried every combination of drm version and modesetting/intel though 04:18:30 it's a comet lake mobile iGPU, the CPU is an i3-10110U 04:18:36 rule of thumb is old = intel, new = modesetting 04:18:45 10th gen, ok 04:19:22 most likely the bsd driver needs an update (not a useful comment sorry) 04:21:54 both Linux 5.10 and 5.15 came out a while after 10th-gen intel 04:22:57 and in this case, the 5.15 drivers seemed to be worse regarding the fault errors, at least on 5.10, for a while I wasn't dealing with any fault errors 04:24:09 but yeah, this is more than just a few, it completely fills up dmesg's buffer within like 10-15 seconds 04:26:24 Ubuntu 20.04 LTS has kernel 5.15, for comparison 04:27:48 It would be relatively quick to install on an external USB drive to check with some simple WM+picom 04:30:47 I was thinking Void Linux which has a much more vanilla kernel. I'm worried that there are a lot of confounding variables though, even though it sounds like FreeBSD tries to make the fewest number of changes possible to the Linux drivers in order to get them working 04:36:08 cool 04:37:23 maybe I'll just have to try 15-CURRENT in order to get drm-61-kmod, though I don't really want to 04:44:07 so picom's xr_glx_hybrid backend doesn't produce the fault errors, though this is not optimal as far as performance goes 04:44:39 oh nevermind picom just didn't launch 04:45:50 have to specify --legacy-backends to get picom to use that backend, and when I get it to launch the fault errors show up 04:59:20 btw, drm-61-kmod won't work with an Intel Arc GPU (or at least an Arc A770) since loading the i915kms module kernel panics for me, even when I already provided the correct firmware bins by hand. Don't get your hopes up there 05:04:31 this is a bit older than the Arc GPUs, I think 05:21:42 alright, well, this seems rather odd. I uninstalled 510, reinstalled 515, went to check it with both the modesetting and intel DDX drivers, both gave fault errors, so I moved back to 510, and the errors are no longer occurring even though nothing has changed 05:22:01 I am pretty worried that this laptop isn't doing too good 05:27:31 are you trying to revive an old laptop? 05:31:01 not really old. it's a ThinkPad E14 from 2019, I bought it as an upgrade from my previous laptop which is actually quite old now 06:01:47 wasn't prepared so I only caught the last bit of it, but here's that loud tone, one of the other sounds this laptop is making. though this one is less common. it plays from before the BIOS splash and continues playing until partway through the fbsd boot process as shown in the video: https://www.youtube.com/watch?v=sK_A9MKgNOg 06:01:49 Title: worse ThinkPad noises - YouTube 06:22:25 tm512: I believe the most vanilla Linux kernel is the one you can get from kernel.org. 06:30:05 remiliascarlet: but then you're stuck compiling from source 06:31:08 And? 06:32:04 and there's no need for me to do that when Void provides essentially vanilla kernel builds 06:32:41 especially pointless for some throwaway install just to test the i915 driver 06:33:13 The Linux distro I'm using is CRUX, so I already got used to having to compile my own kernel on every release, not even a big deal once you know your hardware configuration. 06:36:35 faced with the choice between compiling a huge piece of software from source and grabbing a binary that someone has already compiled, I'll generally take the latter 06:37:57 Void's Linux 5.15 package makes no modifications to the i915 driver, it's a good fit for this test 06:41:09 with the drm-510-kmod drivers, I would really like to know what makes picom cause the fault errors on some boots, but not on others. I'm also quite confused about how replacing 510 with 515, booting into 515, then downgrading back to 510 and rebooting seems to bring the system into a state where the fault errors don't happen 07:05:14 how set are you in picom ? 07:08:14 as long as I'm using X11, quite set 07:09:07 I *suppose* I could try the TearFree option on the intel DDX driver, but in my experience I'm not sure that's ever done what it's supposed to do 07:09:58 at least in recent years, I get screen tearing even with TearFree turned on 07:10:15 i will say, with configuration i've had to do a lot less horsing around with wayland 07:10:20 i'm partial to sway, myself 07:21:11 I would prefer to actually figure out what the issue is instead of attempting to side-step it especially since I'm concerned that the fault errors are a manifestation of a hardware issue (along with the noises this laptop makes). I dunno if those errors are something that would be seen if the hardware was malfunctioning, though 07:23:14 ah that noise is weird 07:26:26 I've got like 9 days left in the 30 day return period from the ebay seller, so I'm gonna have to do what I can to troubleshoot, and if there's nothing I can do I'm going to have to make an annoying decision 07:28:51 I don't want to have to return this. rather annoying process especially since this isn't just an envelope I can carry down to the neighborhood drop-box, and I'm pretty sure the seller doesn't have a replacement ThinkPad E14 they can send me, and I've got FreeBSD running fairly well on this thing, outside of needing wifibox and having these fault errors 07:30:12 but like suspend/resume? basically flawless outside of that seemingly common issue with GLX dropping hardware acceleration whenever there's a VT switch. just had to toggle the suspendswitch sysctl to sort that out, though 07:35:09 maybe I could keep the machine and get a partial refund for being sent malfunctioning hardware that might give out on me sooner than it otherwise would 07:40:49 I think I'm gonna try out 15-CURRENT w/ drm-61-kmod in a separate boot environment to see if that has any effect on the fault errors (I still don't even know what those are, tbh, or what effect they're having). I might also start pulling more hardware out of this thing to see if I can pin the noises to any particular component. clearly isn't the HDD 07:43:13 I'll take out the M.2 SSD, though first I'll need to clone my install over to a separate SSD which I'll probably just put in the now vacant 2.5" bay. I'm guessing I just clone the ZFS datasets over, but what about the bootloader. what's analogous to grub-install for FreeBSD's bootloader? 07:44:10 I could pull the wireless card and the battery as well 08:24:52 You'll want to use gpart(8) to partition your disk before doing zpool create and subsequently zfs sending your datasets. 08:25:50 Your partitioning will depend a bit on how your firmware is configured to boot, but it either involves GPT with UEFI ESP or GPT with UEFI-CSM. 08:27:24 zfs-send(8) will make the transfer itself quite simple, at least. 08:28:24 kinda regretting that it took me this long to get aboard the ZFS train tbh 08:28:34 tm512: do all OSes beep like that on boot? 08:30:51 rtprio: I've only had FreeBSD on this (well, Windows 11 was on it briefly, before I installed over it) but since the noises also occur during what seems to be POST and occasionally during the UEFI splash screen, gives me the impression that it's not related to the OS 08:32:04 I only booted into Win11 just to make sure the machine wasn't DOA, and I didn't get further than the part where it was demanding I bring the machine online and log in to a MS account 08:36:08 if I'm putting in a 2.5" SSD maybe I'll just install Linux first. hell, I could just pull the drive from my previous laptop, wouldn't even have to go through install/setup, I'd just have to configure picom to use glx instead of xrender (previous laptop is so old that it doesn't meet picom's GL requirements) 13:12:09 I have a super weird error on pfctl inside the jail. apparently, my pf is still working and I got this error everytime I run: # pfctl -sr 13:12:13 Assertion failed: (elems <= maxelems), function pf_nvuint_32_array, file /usr/src/lib/libpfctl/libpfctl.c, line 147. 13:25:11 spmzt: that's a bug, you should file it at https://bugzilla.freebsd.org 13:25:12 Title: FreeBSD Bugzilla Main Page 13:25:33 I will, thanks 14:06:00 lw 14:08:39 having a bit of a problem with IPv6. i set up addresses on freebsd and on my machine, but i can ping my machine from freebsd but not freebsd from my machine 14:08:52 i don't have any firewall configured in the freebsd host... wth? 14:13:31 hjf: if you are sure that you don't have any firewall enabled, check if you recv the icmpv6 packet from your machine on your freebsd? (and if does it reply to your machine and the machine somehow ignore it?) 14:13:32 dump the traffic on both hosts, check the routes 14:13:41 jbo 14:14:14 lw! 14:18:30 jbo: not to be rude, because i appreciate that you commit all my ports, but you could say your actual quesion rather than just saying my nick when you ping me :-P 14:19:39 lw, well I have no reason :p 14:19:44 #feelingLonely 14:24:33 ok tcpdump shows it receives the ARP request but doesn't respond 14:24:34 jbo: do you want some ports to commit so you feel less lonely? 14:24:59 ff02::1:ff00:2: ICMP6, neighbor solicitation, who has fd10:c467:a267:1000::2, length 32 14:25:15 jbo: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277020 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277017 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276347 - these are all trivial 14:25:22 Title: 277017 – multimedia/libmpeg2: set LICENSE to GPLv2+ 14:25:55 hjf: but not the icmpv6 echo? 14:26:13 do you have a ll address ? 14:27:34 ifconfig $IFACE inet6 auto_linklocal 14:28:04 sysctl net.inet6.icmp6.nd6_onlink_ns_rfc4861=1 14:28:08 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263288 14:28:10 Title: 263288 – IPv6 system not responding to Neighbor Solicitation 14:45:54 lw: done. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277093 14:45:56 Title: 277093 – pf: Assertion failed: (elems <= maxelems), function pf_nvuint_32_array on stable/14 with RACK 15:09:01 Question, i have installed VirtualBox after using it, some time gui's (from firefox to thunar) start to freeze (also on the screen) for more then 2minutes 15:10:00 then everthing is laggy as hell, then normal again. After some time it starts to freeze again. I could trigger that espacially with qt-gui's 15:10:53 it's FBSD14 with the amdgpu driver. 15:12:19 has anyone else the same problem? When not loading the vbdrv-module everything is snappy again 15:18:01 lw, you're able to run factorio in wine?! :o :o :o 15:18:14 jbo: can't everyone do that? 15:18:38 lw, factorio is the only game I care about these days and the only reason why I still boot windows sometimes. but has gotten rare because booting windows. 15:19:06 jbo: it's working fine for me in wine-devel 9,2 (not in ports, patch in bugzilla) 15:19:25 i had one complete system hang but since then it seems to be ok 15:19:34 lw, let me get back to you on that over the weekend or something 15:22:35 jbo: just make sure you install d3dcompiler_47 from winetricks, wine's shader compiler can't compile Factorio's shaders 15:55:40 lw, testport just failed on 277020 15:55:53 jbo: log? 15:56:49 lw, local build, have to copy pasta 15:57:03 lw, https://pastebin.com/VXHaixUL 15:57:04 Title: tools/install-sh -m 644 include/windows.graphics.directx.direct3d11.idl /wrkdir - Pastebin.com 15:57:35 that's odd. i'll try testport again later 15:58:14 that was on a 13.2-RELEASE jail 15:58:48 i only support -current, but this error doesn't look release-specific 15:59:30 shouldn't we have a warning/error in the makefile if OS versions are restricted? 15:59:58 i don't think this error is related to OS release, it's just weird 16:00:52 that I get 16:21:04 lw, same error happened on 14.0-RELEASE (just as info) 16:29:35 i'm trying to run Flatout, it's free on gog right now. their nix version is basically just windows build packaged with old version of wine. when i try to run it, i get this error: 16:29:36 wine: failed to initialize: libm.so.6: failed to map segment from shared object: Cannot allocate memory 16:30:10 any ideas if there is a fix/workarond for this? or is it trying to do something freebsd just won't allow? 16:45:39 jbo: i'll have a look later, feel more in a play games mood than debug ports mood right now :-) 16:51:45 lw, that is legit. I'll leave a note in the PR. no stress from my side. 16:52:28 btw, Factorio did with with wine-devel 9.1 (which is in ports) so don't feel like you have to commit this just to play it 16:52:35 s/did with/did work with/ 17:02:45 lw: what tools do you use to debug something like that where it's a program on top of wine 17:03:05 johnjaye: i've never had the need to debug something running under wine 17:03:50 ok. i don't know much about debugging on freebsd for that kind of thing. 17:07:02 if i did need to do that, perhaps i'd start by seeing if WinDbg works under wine 17:19:34 jbo: testporting wine-devel on -current now 17:19:54 i don't have a testport script for 14 or 13, but if it doesn't fail maybe i'll make one 17:20:06 lw, in general, please also test for all currently supported -release versions when submitting port updates 17:20:20 (in general - if it's something that only works on -current then... you know the drill). 17:20:44 makes committer's life easier and your submissions will land earlier :) 17:20:46 jbo: that's a lot more effort than you might think. like, to test mediaelch on 14 i'd need to create a whole X/Wayland environment 17:20:57 lw, not for testport 17:21:08 testport != 'test a port' 17:21:13 all it does it test that it builds, not that it works 17:21:14 hence I say testport and not test port ;) 17:21:28 note: if you are the _MAINTAINER_ of a port you are expected to also do runtime tests. 17:21:29 well, you said 'test'... 17:21:40 true 17:21:42 s/test/testport 17:21:55 committers don't care about runtime issues (technically). that is the maintainer's job. 17:22:17 i didn't see anything in the porter's handbook about this, it seems more reasonable to me to wait for users to report problems on odler releases, if there are any 17:22:46 which aspect are we talking about right now? 17:22:53 runtime testing 17:23:02 i'd like to help out if possible. I've used Windbg but just for really basic things. 17:23:24 like, i did not test mediaelch or sublime-music on 13 because i don't have a complete install of 14/13 sitting around just to do that 17:23:37 if that's requirement to maintian a port... i will probably just not maintain ports :-/ 17:24:41 obviously if i was maintainer of something like Qt or glib then yes, i would do more testing and probably ask for exp-run before submitting patches 17:25:01 but the amount of testing required can vary based on port, right? 17:26:36 lw, https://docs.freebsd.org/en/articles/contributing/#adopt-port 17:26:37 Title: Contributing to FreeBSD | FreeBSD Documentation Portal 17:26:55 > Build, install and test your port on as many platforms and architectures as you can. 17:27:04 "as you can" - I know what you're going to say ;) 17:28:00 so you have to have virtual machines or something right to do that? 17:28:14 everybody has a different solution/setup for that I think 17:28:26 also depends the ports 17:28:32 jbo: i find this quite hilarious because the only port i took over maintainership of (rather than submitting as a new port) has been broken for months because no one can be bothered to commit a fix for devel/py-urwid 17:28:40 if it s non-GUI upstream with a built-in testing framework you can do a lot with testport 17:28:45 if no one else cares about this, why should i... 17:29:02 lw, that is not the spirit we're looking for :) 17:29:17 jbo: it's not the spirit i'm looking for either because i'd like my port to work 17:29:46 but apparently we don't care if everything that depends on urwid is just broken? 17:30:01 i mailed ports@ (twice) and python@ about this, no response 17:30:55 I cannot speak for python(@). I actually ran into an issue that would need some python patching which I wanted to ask you whether you'd be able to handle that :D 17:31:04 (platform detection crappery) 17:33:34 that aside (but let me be clear that this whole thing has really soured me on maintaining anything, tbh), the way i see it is, it's not feasible for me to test my port on every architecture (i386, amd64, arm64, armv7, riscv64) x every release (13, 14, current), but if someone reports a problem on some release, i will look ingo that and fix it is possible 17:36:26 i actually submitted this a month ago https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276347 (trivial patch to mark the port as BROKEN since it is) and not even that is committed 17:36:28 Title: 276347 – net-im/toot: mark as BROKEN since devel/py-urwid is broken 17:36:54 so, idk, what is the right spirit here 17:37:05 wait, you're the maintainer of it? 17:37:15 of net-im/toot, yes 17:38:34 can you update that BROKEN= message to specify the py-urwid version rather than "current"? 17:39:18 "Does not work with devel/py-urwid-X.Y currently in ports" 17:39:21 or something like that 17:39:26 the version of py-urwid doesn't actually matter, the issue is that setuptools_scm is broken 17:39:42 this is the fix: https://reviews.freebsd.org/D39288/new/ 17:39:44 Title: ⚙ D39288 devel/py-setuptools_scm: update to 8.0.4 17:40:17 but someone could fix this for py-urwid specifically by committing the fix in bug 274411 17:40:18 274411 – devel/py-urwid Update to 2.2.x breaks several python packages https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274411 17:40:44 I don't know the standard/requirements for BROKEN= values but personally I'd suggest putting a message in there referencing that diff or whatever. but I'll ask somebody who knows. 17:42:10 tbh i would rather someone would fix urwid, i don't understand how there's been a patch for this serious bug since November and no one cares 17:42:11 I currently don't have enough experience to mingle with python@. If it would be a "person" maintainer I wouldn't mind looking into maintainer-timeout but python@ might have different ideas for reasons I am not aware of. 17:42:27 i thought adding a BROKEN= tag would be a trivial change in the mean time, not something that requires a review by itself 17:43:28 BROKEN= does not require a review on your end but I am still under mentorship. My belt is being loosened lately but I have not been given permission to touch something like that without mentor approval yet :) 17:44:30 for example, the wine-devel PR I could commit without mentor review by now 17:45:05 lw, so you e-mailed python@ about this? 17:45:42 uuuf, 274411 is not even that big of a "patch" 17:46:13 unfortunately, I don't know the python ecosystem well enough to call a shot here. I'd try to get in touch with python@ 17:46:42 jbo: i mailed ports@ in December https://lists.freebsd.org/archives/freebsd-ports/2023-December/005096.html and in January i mailed python@ cc: ports@ https://lists.freebsd.org/archives/freebsd-python/2024-January/005480.html 17:46:44 Title: devel/py-urwid and devel/py-setuptools_scm (PR# 274411) 17:47:20 "stymied" holy f* 17:47:23 new word day 17:48:48 the TL;DR is that I'll not interfere with python@'s business. 17:49:19 I can ask around tho 17:49:30 that's fair, i don't expect you to fix this. but you can see why this makes me laugh a bit when someone asks me to test my patches on 3 different freebsd releases, right? :-) 17:49:38 jbo: didn't you do stumpwm? 17:50:02 Demosthenex, nope. I never wrote a single line of lisp. I'm a perl guy :p 17:50:08 PERL! 17:50:09 Demosthenex, and I'm a user of bspwm 17:50:16 must have been another j name 17:50:31 i was chatting with the maintainer of stumpwm port ;] 17:50:47 lw, well the testing stuff should be unrelated to this, tbh. but I get your point of course. I just think it's irrelevant :p 17:51:07 Demosthenex: that's jrm@ 17:51:08 Demosthenex, that would be jrm 17:51:33 lw, do you feel like using your anger for something helpful? :D I'd have a little something that needs fixing and I'm not a python guy. 17:52:01 jbo: sure, but i need more vodka + a cigarette first, feel free to type your question in the mean time :-) 17:52:35 lw, devel/emscripten.... upstream ships with emrun.py and that does platform detection which currently only handles Windows, Linux and MacOS. I did quick-n-dirty just default to LINUX=True yesterday but that is not proper and they apparently do gpu checks with glxinfo and all that crap. 17:52:47 * jrm waves to Demosthenex 17:52:50 yay! 17:52:54 lw, https://github.com/emscripten-core/emscripten/blob/main/emrun.py 17:52:55 Title: emscripten/emrun.py at main · emscripten-core/emscripten · GitHub 17:53:09 i appreciate your time packaging something so exotic ;] 17:53:36 the secret is that usually (!) the exotic stuff is much easier to maintain because it has less bloat :p 17:54:06 https://cgit.freebsd.org/ports/tree/www/chromium/files .... 17:54:08 Title: files « chromium « www - ports - FreeBSD ports tree 17:55:57 jbo: yeah, stumpwm should be one whole single binary file ;] 17:56:11 given common lisp programs are typically distributed as a image file 17:56:18 I did not mean to diminish jrm 's efforts of course! 17:59:10 The StumpWM port/package is back to a single bundled binary. For a few years I switched to a tiny package that had a few deps (SBCL and a few CL libraries), but dealing with the FASL stuff was a pain. 17:59:39 jbo: ah i do not know anything about emscripten 17:59:46 isn't that llvm thing? 18:00:07 lw, yeah but that's irrelevant. emrun just spawns a webserver to serve an HTML file generated by em++ 18:00:41 lw, emscripten generates webassembly from anything that has an LLVM frontend 18:00:49 jbo: well, you know the Internet is only supported on three platforms nowadays (Windows, macOS, Linux), so it sounds like they did it right 18:00:59 (do i seem bitter about this? i am) 18:01:11 alright, I'm gonna stop bothering you for now :) 18:01:28 i would help but i know absolutely nothing about emscripten, sorry 18:01:42 if you have more obscure C++ questions i can probably help with that 18:01:44 you don't have to - but it's totally fine :) 18:02:03 lw, yeah, I am trying to use coroutines for the first time :D 18:05:53 co_<3 18:14:27 jbo: testport showed the same issue with emulators/wine-devel 9.2, odd, i will investigate this later 18:16:52 Hello , I have crash when I want to use Pluma with MATE desktop , on AMD64 18:18:45 what kind of crash? 18:19:19 lw, ack 18:20:04 Demosthenex: I don't know but I have a core dump 18:21:24 i mean did the WM crash, did X crash, did the whole kernel crash and reboot? 18:21:30 But I don't know to use this core file. 18:22:28 you'd typically open it in the corresponding debugger (lldb,gdb, ...) along with the binary (ideally with debug symbols) and start investigating :D 18:23:33 Demosthenex: No , when I clic on , it's await and avort and I have a coredump, Pluma.core 18:25:12 jbo: Sorry , I don't know this, I'm beginner on freebsd. But I want to learn to make this. 18:26:38 dwho: ok, so youhave X11 running, and MATE desktop up. you try to launch and application (pluma) and it coredumps 18:27:08 generally you need to be a C developer to read a core dump, but you should certainly try to open it and see if there's an obvious cause 18:28:32 Demosthenex: Yes 18:29:39 I read the Pluma.core with ghex but I don't to extract info. 18:31:01 you need a debugger, not hex dump 18:31:03 I haven't the knoledge to exploit core. 18:32:24 https://docs.freebsd.org/en/books/developers-handbook/tools/#_examining_a_core_file_with_lldb 18:32:25 Title: Chapter 2. Programming Tools | FreeBSD Documentation Portal 18:32:40 https://docs.freebsd.org/en/books/developers-handbook/tools/#_examining_a_core_file_with_gdb 18:32:42 Title: Chapter 2. Programming Tools | FreeBSD Documentation Portal 18:33:11 dwho: that's a place to start. also check your logs in /var/log, the messages file may have something useful 18:33:44 Thanks, I read this and I learn. 18:35:11 having a single failed app is an easy place to start 18:36:48 Demosthenex: Yes I read /var/log/message and I have "exited on signal 11 (core dumped)" 18:37:09 progress! 18:38:31 I learn to will have the knowledge to exploit coredump, thanks fpr help. 20:02:25 lw, you're running jellyfin, right? 20:07:07 Does Plex have hardware acceleration with FreeBSD and a Nvidia 3060 GPU? 20:35:24 Hello I want to use wireshark without root but I use a user with wheel group and 20:37:42 I modyfing /etc/devfs.conf with append own bpf* root:network and perm bpf* 0660 20:38:33 but my user don't capture with wireshark ? 20:58:03 @SponiX I believe my Plex box has acceleration with an Nvidia card. Not the 3060, though. I'll double check. 20:59:28 dwho, is your user a member of the "network" group? 21:00:25 Yes, my plex box has it enabled. 21:00:54 beowuff: thanks, I appreciate you checking for me. I am still on the fence about migrating from Linux to FreeBSD 21:03:02 The FreeBSD plex server lags behind when Plex is updated a few days, but the devs maintaining the port seem to be on top of things pretty well. 21:03:16 I haven't had issues. 21:41:17 hello 21:41:30 has anybody managed to compile LocalAI in freebsd ? 23:47:09 wow, csh might get functions, finally: https://github.com/tcsh-org/tcsh/pull/77 23:47:10 Title: Introduce 'function' built-in. by Krush206 · Pull Request #77 · tcsh-org/tcsh · GitHub