xdg-open will open the default browser. This is likely an issue with that app having firefox hardcoded, or detecting it and using it when detected or some stuff.
I’ve had mac rando on on fedora in the past and am running Graphene with it on by default, no breakages so far in about 2-2.5yr
People that dont have problems dont have a lot to add in terms or arguments :D
There are 2 types of MAC rando, and GrapheneOS uses full per-connection rando by default.
If you are in networks where access is controlled via the MAC, this will break. Static randomized (in grapheneOS “per network”) like on Fedora dont have this issue at all, this should really be default always.
But it does not protect against certain levels of tracking.
Also randomized MACs may fill up certain router softwares and cause DHCP to fail because it tries to remember every connected device “for security” (FritzBox in my case).
Thing is though, it exhibited the desired behavior on Fedora 39 Gnome, if it was just how SABnzbd rolled I’d expect it to do it back then too, but since it’s new behavior I suspect it’s something else.
Yeah it does clog up the router a bit but I think in my case they auto-clean the older ones out.
I may do that, but honestly instead of doing any testing I kinda just immediately said “fine, you don’t wanna do it? Uninstall howbout now?” So idk if I have much valuable data for them.
xdg-open will open the default browser. This is likely an issue with that app having firefox hardcoded, or detecting it and using it when detected or some stuff.
People that dont have problems dont have a lot to add in terms or arguments :D
There are 2 types of MAC rando, and GrapheneOS uses full per-connection rando by default.
If you are in networks where access is controlled via the MAC, this will break. Static randomized (in grapheneOS “per network”) like on Fedora dont have this issue at all, this should really be default always.
But it does not protect against certain levels of tracking.
Also randomized MACs may fill up certain router softwares and cause DHCP to fail because it tries to remember every connected device “for security” (FritzBox in my case).
Thing is though, it exhibited the desired behavior on Fedora 39 Gnome, if it was just how SABnzbd rolled I’d expect it to do it back then too, but since it’s new behavior I suspect it’s something else.
Yeah it does clog up the router a bit but I think in my case they auto-clean the older ones out.
Strange. Make sure to contact the devs though, as KDEs settings always worked for me reliably.
I may do that, but honestly instead of doing any testing I kinda just immediately said “fine, you don’t wanna do it? Uninstall howbout now?” So idk if I have much valuable data for them.