-
FatalNIX
I think I I think I figured it out, I did in fact need to adjust my repo file a bit.
-
FatalNIX
I did not realize it was disabled.
-
FatalNIX
Going to reboot and test.
-
rtprio
how was your FreeBSD-base repo disabled if you were using pkgbase?
-
FatalNIX
I am so glad I made a boot environment because I broke it horribly :D
-
rtprio
how was your FreeBSD-base repo disabled if you were using pkgbase?
-
seti
using sway on freebsd-15, everything seems to be running smoothly so far but launching firefox specifically it takes AGES
-
seti
my drive is more than fast enough and the PC as well
-
seti
im not the only one who has run into this, apparently its a documented thing with GTK+ applications like firefox
-
seti
"This is due to GTK+ waiting for xdg-desktop-portal to start via D-Bus. This times out because the D-Bus activated service doesn't know what WAYLAND_DISPLAY to connect to."
-
seti
"Alternatively, set GTK_USE_PORTAL=0 in your environment."
-
seti
the former alternative was something with systemd which obviously is a nogo, anyway exporting that in .profile or .shrc for my user doesnt solve it
-
SarahMalik
have you installed an appropriate portal service?
-
seti
SarahMalik: not sure what they would be but i followed the handbook and installed seatd and ran sysrc seatd_enable="YES" \ service seatd start
-
seti
checking in rc.conf seatd is enabled
-
ridcully
seti: have you tried this from your terminal first, that is actually the problem and the env-var is the solution? e.g. `GTK_USE_PORTAL=0 firefox`
-
seti
ridcully: running that from my terminal and its still slow as molasses
-
seti
when starting
-
SarahMalik
seti, that's not a portal
-
SarahMalik
have you installed an appropriate portal service, such as xdg-desktop-portal-gtk out of the packages repository?
-
SarahMalik
and, for extra credit: is dbus running
-
seti
I installed that now, and noticed now that dbus isnt running
-
seti
So i installed the xdg-portal package (checked that its running), enabled dbus and its also running, im exporting GTK_USE_PORTAL=0 in my .profile and launching from terminal GTK_USE_PORTAL=0 firefox yet no dice
-
seti
firefox still takes something like 20 seconds to start
-
seti
-
seti
i might have been presumptious in what they list as first solution because they mention that it applies to systemd or dbus activation environments
-
nedko
seti: HTH. i have no portal installed and i'm on linux with x11 and notionwm, but seeing ridcully's suggestion i tried the env var and it reduced the 20s startup time with few seconds.
-
seti
nedko: I have a fedora install on another identical nvme drive that is also running sway, freebsd is taking 30 seconds to start firefox linux barely took 1
-
seti
timed it just now
-
ant-x
What soft of part of FreeBSD is tcsh? It is there, yet not listed by ``pkg info''. It cannot be uninstalled?
-
SarahMalik
It's part of the base system.
-
ant-x
More than one shell in the base system. OK. So, deintalling it legally without the danger of it's beging reinstated upon upgrade is impossible?
-
vkarlsen
If you use pkgbase, tcsh is in the FreeBSD-csh pkg
-
SarahMalik
Correct. however I don't know if any base system scripts actually use it
-
ant-x
vkarlsen, I think not: there is not pkgbase on my system, FreeBSD 15.
-
SarahMalik
so a custom build with tcsh disconnected could work, maybe
-
ant-x
Perhaps I'll switch to pkgbase if it is at all possible.
-
eoli3n
I still face my "freeze" problem
-
eoli3n
and i still don't find any error, any alert
-
eoli3n
i don't know what to do at all
-
zip
Pi zero 2w obtained: now the fuckery aroundery can happen on a device that can run FreeBSD 15 :)
-
polarian
anyone know how to fix this when make release
bpa.st/KYQA
-
polarian
buildworld and buildkernel was executed
-
polarian
maybe I need to build something else too
-
polarian
hmm maybe I need to make update-packages first
-
polarian
lemme do that
-
rtprio
eoli3n: do other os work without freeze?
-
eoli3n
rtprio good test ! lets try to boot ubuntu iso and let it run, it the problem is here, it should freeze in less than 24h
-
eoli3n
i will try this in next fail
-
eoli3n
because i suspect my syncthing jail to trigger the bug
-
rtprio
can it only run 1 vm at a time ?
-
eoli3n
nop, but ressources CPU and RAM are very limited
-
eoli3n
2 cores and 2G ram
-
eoli3n
i stopped my syncthing jail and waiting for the freeze
-
rtprio
yeah, perhaps try 24h without syncthing, also?
-
rtprio
( i did have a router that couldn't handle the number of tcp connections with torrents and would crash)
-
ant-x
I have set LogLevel debug in /etc/ssh/sshd_config, and restarted sshd. Now, where do I see the debug output by default? Under /var/log/ messages and auth.log are still rather stingy about ssh...
-
eoli3n
rtprio: that's what i'm currently doing : 24h with syncthing stopped
-
eoli3n
"eoli3n i stopped my syncthing jail and waiting for the freeze"
-
lt
Hi all. Anyone aware of any pf regressions on FreeBSD/15 ? I am getting "Fatal double fault" panics on a fresh installed FreeBSD 15. The fault happens the moment "kldload pf" is done
-
rwp
lt, I am just going to ask some clarifying questions. What architecture? On bare metal or a VM? If bare metal is this a known good system hardware or perhaps freshly assembled?
-
lt
is a hetzner bare metal server. AMD64/ AMD Ryzen
-
nwe
-
rwp
lt, I don't know (I am not running 15 anywhere yet) but I might verify that 14 runs correctly and then bisect into it. Sorry. No help from me. :-(
-
luna__
hi
-
wavefunction
lt: just ran `kldload pf` on my intel xeon FreeBSD 15 box. Nothing unexpected. No faults.
-
lt
rwp, wavefunction: I found out and solved. I guess there is indeed a bug in pf. Seems it does not like "groups" on interfaces. does not matter if you use them. especially with wg interfaces. disabling wg made pf work. enabling it again, with my previous conf using groups made it crash again. But as the fault was happening on "kldload pf" I guess something is wrong there. Disabling "group" on my wg interfaces
-
lt
solved the issue, maybe I should file this bug somewhere?
-
rwp
lt is gone but speaking into the air I think it is always good to file a Problem Report concerning behavior like that and it seemed fairly repeatable too.