t; https://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/www/mozilla-firefox/Makefile
> https://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/www/firefox-esr/Makefile
>
> Landry
>
Oh, that's entirely my bad. My ports tree must be out of date.
Disregard this.
Good work staying on top of
rts tree hasn't been updated.
there's no point in panicking, ever. I don't know where you've looked,
but the port is up to date, both in current and stable, and that since
two days, when the security update has been released.
https://cvsweb.openbsd.org/cgi-bin/cvsweb/
Hello ports@, landry@
First off, I wanna apologize if you, Landry have already been panicking
about this. But, if you weren't aware, FF has an actively attacked RCE
vuln right now, and the port in our ports tree hasn't been updated.
https://thehackernews.com/2024/10/mozilla-warns-of-active-exploi
Equivalent diff for tor-browser. I did see a SIGSEGV after a bit of
scrolling around (with swrast_dri.so in the backtrace) and have had
network stop working after using it for a bit until ifconfig axen0
down/up (even local pings didn't respond) - I've seen that before
with older Fi
On Tue, Sep 24, 2024 at 02:28:20PM +0100, Stuart Henderson wrote:
> This fixes things for me (also needs the pledge commit to the kernel).
> aarch64 package at https://junkpile.org/firefox-130.0.1p0.tgz if anyone
> wants to try it.
Confirmed on my m1. I think this is the right app
This fixes things for me (also needs the pledge commit to the kernel).
aarch64 package at https://junkpile.org/firefox-130.0.1p0.tgz if anyone
wants to try it.
OK?
Index: Makefile
===
RCS file: /cvs/ports/www/mozilla-firefox
ild was quicker than I'm used to!
with this + the kern_pledge.c diff, I still get a SIGILL though
(trapno=33554432). no firefox.core though, is there an easy way to
stop the kernel from allowing firefox to trap SIGILL?
$ aarch64-esr-decoder `moo 33554432 | head -1`
ESR 0x
; missing AARCH64_VALID_JUMP_TARGET too).
>
> Attempting to apply those to the version in firefox there are a bunch
> of failures and porting them across will need knowledge of arm asm.
>
> Just starting a build with this to try. I _think_ it's the right
> place but not en
les in ports/multimedia/dav1d/patches/* mostly don't have
explanatory comments in the files, but commit log for many are "Fix
arm64 assembly to be compatible with xonly" (plus there are a few
missing AARCH64_VALID_JUMP_TARGET too).
Attempting to apply those to the version in firefox th
In addition to what sthen posted, I ran into these, the first one smells
like a noexeconly issue. Not sure about the second one (I modified kdump
to print the trap as hexadecimal since I got tired of translating
decimal to hex)
67550 firefox PSIG SIGSEGV caught handler=0x2027faaeb8 mask=0
I'll wait for a bit more input, then I'd be happy to commit this
and bring it into release.
> > On 2024/09/23 20:26, Stuart Henderson wrote:
> > > This is done in a content process:
> > >
> > > firefox(1142): pledge sysctl 2: 7 3
> > > firefox[1142]: pledge "", syscall 202
> > >
> > > Looking at sys/arch/arm64/includ
Theo Buehler wrote:
> On Mon, Sep 23, 2024 at 03:01:17PM -0600, Theo de Raadt wrote:
> > Does this help?
> >
> > Since we are close to release, I'm intentionally making it a seperate
> > block, and we can trust the compiler's common-subexpression-elimination
> > to clean it up. If there was a 3
On Mon, Sep 23, 2024 at 03:01:17PM -0600, Theo de Raadt wrote:
> Does this help?
>
> Since we are close to release, I'm intentionally making it a seperate
> block, and we can trust the compiler's common-subexpression-elimination
> to clean it up. If there was a 3rd entry we would make it a switc
Does this help?
Since we are close to release, I'm intentionally making it a seperate
block, and we can trust the compiler's common-subexpression-elimination
to clean it up. If there was a 3rd entry we would make it a switch().
Index: kern_pledge.c
==
Stuart Henderson wrote:
> > Managed to capture some ktrace -di by pointing it at the running main proc
> > after startup and reloading the tab. Instead of getting killed by pledge, I
> > get a SIGILL instead, trapped by firefox's handler.
> >
> > 23282
On 2024/09/23 20:26, Stuart Henderson wrote:
> This is done in a content process:
>
> firefox(1142): pledge sysctl 2: 7 3
> firefox[1142]: pledge "", syscall 202
>
> Looking at sys/arch/arm64/include/cpu.h I think this translates to
> machdep.id_aa64isar1 (I trie
On 2024/09/23 21:24, Stuart Henderson wrote:
> On 2024/09/23 20:26, Stuart Henderson wrote:
> > This is done in a content process:
> >
> > firefox(1142): pledge sysctl 2: 7 3
> > firefox[1142]: pledge "", syscall 202
> >
> > Looking at sys/ar
This is done in a content process:
firefox(1142): pledge sysctl 2: 7 3
firefox[1142]: pledge "", syscall 202
Looking at sys/arch/arm64/include/cpu.h I think this translates to
machdep.id_aa64isar1 (I tried running it under ktrace but I just get
very fast-running fans and a frozen machi
ped working (recently though, last few weeks). It
> had been working. I can see the ~/Downloads directory and
> contents. Just can't write to it.
>
> Mozilla Firefox 129.0.2
> 7.6 GENERIC.MP#299 amd64
>
> I don't believe I changed my unveil files.
>
> (/etc/
gt;
>> Not sure when it stopped working (recently though, last few weeks). It
>> had been working. I can see the ~/Downloads directory and
>> contents. Just can't write to it.
>>
>> Mozilla Firefox 129.0.2
>> 7.6 GENERIC.MP#299 amd64
>&g
Hello,
sol...@perso.pw (Solène Rapenne), 2024.09.01 (Sun) 13:04 (CEST):
> Le 01/09/2024 à 12:55, Jon Fineman a écrit :
> > When I try and print to pdf/save file to ~/Downloads I get the
> > following message:
> >
> > The folder contents could not be displayed
> > You do not have access to the sp
been working. I can see the ~/Downloads directory and
contents. Just can't write to it.
Mozilla Firefox 129.0.2
7.6 GENERIC.MP#299 amd64
I don't believe I changed my unveil files.
(/etc/firefox)$: grep Downloads *
unveil.content:~/Downloads r
unveil.main:~/Downloads rwc
(/etc/firef
directory and
contents. Just can't write to it.
Mozilla Firefox 129.0.2
7.6 GENERIC.MP#299 amd64
I don't believe I changed my unveil files.
(/etc/firefox)$: grep Downloads *
unveil.content:~/Downloads r
unveil.main:~/Downloads rwc
(/etc/firefox)$:
Any thoughts on what might have changed?
Thanks.
Jon
I think you should give up on this.
I think by talking about "sandbox" in an abstract for what is going on,
it fails to describe the what is going on. "sandbox" is an extremely
unspecific words and everyone brings in their weird understanding.
- the program (firefox) has ext
Le Wed, Aug 14, 2024 at 10:57:46AM +0200, Jan Stary a écrit :
> > Can AMD users play https://www.youtube.com/watch?v=LXb3EKWsInQ in
> > 2160p60 on FF without blowing the CPU?
>
> On this AMD machine (dmesg and vainfo below),
> firefox-129.0 plays this video eating about 1
On Fri, 9 Aug 2024 06:46:57 + (UTC)
"Theo de Raadt" wrote:
> CIVINULL wrote:
>
> > https://www.bleepingcomputer.com/news/security/18-year-old-security-flaw-in-firefox-and-chrome-exploited-in-attacks/
> >
> > I wonder if the sandboxing of Chromium and F
You can try this yourself:
ping 0.0.0.0
ssh 0.0.0.0
or on a webserver machine
nc -v 0.0.0.0 80
It's the same for chrome, because it is the same for *all userland programs*
CIVINULL wrote:
> https://www.bleepingcomputer.com/news/security/18-year-old-security-flaw-in-firefox-and-chrome-exploited-in-attacks/
>
> I wonder if the sandboxing of Chromium and Firefox on OpenBSD will prevent it
> from being affected by this vulnerability.
Sorry, our sandbo
https://www.bleepingcomputer.com/news/security/18-year-old-security-flaw-in-firefox-and-chrome-exploited-in-attacks/
I wonder if the sandboxing of Chromium and Firefox on OpenBSD will prevent it
from being affected by this vulnerability.
On 2024/06/11 23:06, Jan Stary wrote:
> Is anyone able to play songs from Spotify in Firefox?
> I always get to my browser being "unsupported" in one
> way or another. I cannot find th "DRM" toggle to enable
> in Firefox's setting. Is there any othe
Is anyone able to play songs from Spotify in Firefox?
I always get to my browser being "unsupported" in one
way or another. I cannot find th "DRM" toggle to enable
in Firefox's setting. Is there any other way to play that?
Thanks
Jan
Le Fri, Apr 05, 2024 at 11:31:15AM -0700, Heppler, J. Scott a écrit :
> More info.
>
> I did a manual upgrade and used pkg_add -u to update firefox-esr.
> I removed the package and reinstalled. Recursively deleted ~/.mozilla
> and firefox-esr now correctly ID's as Open
On 2024/04/05 11:31, Heppler, J. Scott wrote:
> More info.
>
> I did a manual upgrade and used pkg_add -u to update firefox-esr.
> I removed the package and reinstalled. Recursively deleted ~/.mozilla
> and firefox-esr now correctly ID's as OpenBSD - 7.5
>
> I was in
More info.
I did a manual upgrade and used pkg_add -u to update firefox-esr.
I removed the package and reinstalled. Recursively deleted ~/.mozilla
and firefox-esr now correctly ID's as OpenBSD - 7.5
I was initially concerned that the build info had not been updated. For
some reason pkg_u
This is minor but after upgrading to 7.5
firefox-esr > Help > About Firefox
ID as OpenBSD - 7.4
dmesg:
OpenBSD 7.5 (GENERIC.MP) #82: Wed Mar 20 15:48:40 MDT 2024
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
pkg_info firefox-esr
Information for inst:firef
Lennart Jablonka wrote:
> Quoth Landry Breuil:
> >Le Thu, Mar 28, 2024 at 02:52:52PM +, Lennart Jablonka a écrit :
> >> I’m trying to get himitsu-firefox¹ working on OpenBSD. It’s a Firefox
> >> extension that talks to a daemon² using “native messaging
Quoth Landry Breuil:
Le Thu, Mar 28, 2024 at 02:52:52PM +, Lennart Jablonka a écrit :
I’m trying to get himitsu-firefox¹ working on OpenBSD. It’s a Firefox
extension that talks to a daemon² using “native messaging”: The extension
calls runtime.connectNative(); the browser spawns a himitsu
Le Thu, Mar 28, 2024 at 02:52:52PM +, Lennart Jablonka a écrit :
> I’m trying to get himitsu-firefox¹ working on OpenBSD. It’s a Firefox
> extension that talks to a daemon² using “native messaging”: The extension
> calls runtime.connectNative(); the browser spawns a himitsu-firef
I’m trying to get himitsu-firefox¹ working on OpenBSD. It’s
a Firefox extension that talks to a daemon² using
“native messaging”: The extension calls runtime.connectNative();
the browser spawns a himitsu-firefox-native process, and extension
and native process exchange JSON messages.
The
reg Steuck wrote:
I recently noticed that notification that firefox shows for Google Chat
are displayed as ordinary windows by xmonad as opposed to corner popups.
Is this a recent change or did I simply not notice this behavior before?
Anybody else hit this? Any workarounds?
The windows have
Le Mon, Mar 11, 2024 at 11:52:59AM -0700, Greg Steuck a écrit :
> I recently noticed that notification that firefox shows for Google Chat
> are displayed as ordinary windows by xmonad as opposed to corner popups.
> Is this a recent change or did I simply not notice this behavi
Hi Greg,
On Mon, Mar 11, 2024 at 11:52:59AM -0700, Greg Steuck wrote:
> I recently noticed that notification that firefox shows for Google Chat
> are displayed as ordinary windows by xmonad as opposed to corner popups.
> Is this a recent change or did I simply not notice this behavi
I recently noticed that notification that firefox shows for Google Chat
are displayed as ordinary windows by xmonad as opposed to corner popups.
Is this a recent change or did I simply not notice this behavior before?
Anybody else hit this? Any workarounds?
The windows have somewhat different
I can't say anything about Firefox, but if you're having performance
issues and don't mind using a 3rd party youtube client, check out
www/minitube or www/pipe-viewer (pipe-viewer recently imported a few
days ago, you will have to backport if you're on -stable; I wrote this
por
Hello,
I'm using amd64 snapshots here, bot Chromium and Firefox installed.
I prefer to use Firefox but every time when I play an youtube video in
full screen i have to manually lower down the resolution to 480p /
720p just to avoid "dropped frames" reported in Right click > Stat
On 2024/01/25 16:40, Landry Breuil wrote:
> Le Thu, Jan 25, 2024 at 04:17:18PM +0100, Simon a écrit :
> > Hello Landry,
> >
> > Same Problem exist on AMD64, using 7.4 current #1623 at the moment.
> > Firefox Version 121.0.1
> > But I don't have any more
Le Thu, Jan 25, 2024 at 04:17:18PM +0100, Simon a écrit :
> Hello Landry,
>
> Same Problem exist on AMD64, using 7.4 current #1623 at the moment.
> Firefox Version 121.0.1
> But I don't have any more knowledge to give you more Information.
since i dont have issues wi
Hello Landry,
Same Problem exist on AMD64, using 7.4 current #1623 at the moment.
Firefox Version 121.0.1
But I don't have any more knowledge to give you more Information.
Many Thanks for your awesome work.
Best Regards
Simon
On 25 January 2024 15:35:06 CET, Landry Breuil wrote:
>Le
Le Wed, Jan 24, 2024 at 08:49:27AM +0100, Jan Stary a écrit :
> This is current/arm64 on a MacBook Air (M1),
> running the latest Firefox 121.0.1
>
> Some webpages, such as reuters.com or theguardian.com,
> result in a tab crash, with firefix saying
>
> [Parent 94040, IP
On Jan 24 09:41:52, tobias.hei...@stusta.de wrote:
>
>
> On January 24, 2024 8:49:27 AM GMT+01:00, Jan Stary wrote:
> >This is current/arm64 on a MacBook Air (M1),
> >running the latest Firefox 121.0.1
> >
> >Some webpages, such as reuters.com or theguardian.co
On January 24, 2024 8:49:27 AM GMT+01:00, Jan Stary wrote:
>This is current/arm64 on a MacBook Air (M1),
>running the latest Firefox 121.0.1
>
>Some webpages, such as reuters.com or theguardian.com,
>result in a tab crash, with firefix saying
>
>[Parent 94040, IPC I/O Par
On Mon, Dec 25, 2023 at 08:41:16PM -0500, Jon Fineman wrote:
Landry Breuil writes:
Le Thu, Dec 21, 2023 at 06:25:23AM -0500, Jon Fineman a écrit :
Since upgrading my firefox has been crashing every night, when I am
not on. My desktop isn't set up to sleep, just xscreensaver.
no real
solved in the last snaptshot
On 17/12/2023 14:28, BESSOT Jean-Michel wrote:
Hello
The last firefox(120.0.1) does not download anymore. I just get a
laconic message : Échec.
Bye
Landry Breuil writes:
> Le Thu, Dec 21, 2023 at 06:25:23AM -0500, Jon Fineman a écrit :
>> Since upgrading my firefox has been crashing every night, when I am
>> not on. My desktop isn't set up to sleep, just xscreensaver.
>
> no real idea, but whatever page you
Le Thu, Dec 21, 2023 at 06:25:23AM -0500, Jon Fineman a écrit :
> Since upgrading my firefox has been crashing every night, when I am
> not on. My desktop isn't set up to sleep, just xscreensaver.
no real idea, but whatever page you're leaving open, it's leaking, as
Since upgrading my firefox has been crashing every night, when I am
not on. My desktop isn't set up to sleep, just xscreensaver.
firefox --version
Mozilla Firefox 120.0.1
pkg_info -Q firefox
debug-firefox-120.0.1p0 (installed)
firefox-120.0.1p0 (installed)
kern.version=OpenBSD 7.4-cu
On Sun, 17 Dec 2023 10:13:39 +0100
Jan Stary wrote:
> msyscall f6e75108000 a7000 error
> Segmentation fault (core dumped)
>
> [firefox]20388/413659 pc=f6e7511847b inside f6e8575b000-f6e85766fff: bogus
> syscall
I got a crash like this in irssi on powerpc, beca
Hello
The last firefox(120.0.1) does not download anymore. I just get a
laconic message : Échec.
Bye
firefox-120.0.1p0 has a syscall issue,
so get yourselves the 119 package from the stable tree
and run something like:
firefox --allow-downgrade --no-remote -P
---
firefox-120.0.1p0.tgz
[firefox]89353/227383 pc=7cbba8347bb inside 7cc395c3000-7cc395cefff:
bogus syscall
thunderbird-115.5.2
on a M1 macbook, with firefox-120.0.1.
> > Firefox will not start, complaining that
> >
> > XPCOMGlueLoad error for file /usr/local/lib/firefox/libmozwayland.so.132.0:
> > File not found
> > Couldn't load XPCOM.
> >
> > Indeed, the file does not exist.
11:26AM +0100, Jan Stary wrote:
This is current/arm64 on a M1 macbook, with firefox-120.0.1.
Firefox will not start, complaining that
XPCOMGlueLoad error for file /usr/local/lib/firefox/libmozwayland.so.132.0:
File not found
Couldn't load XPCOM.
Indeed, the file does not exist.
On Sun, Dec 17, 2023 at 10:11:26AM +0100, Jan Stary wrote:
> This is current/arm64 on a M1 macbook, with firefox-120.0.1.
> Firefox will not start, complaining that
>
> XPCOMGlueLoad error for file /usr/local/lib/firefox/libmozwayland.so.132.0:
> File not found
> Couldn't
This is current/amd64, with firefox-120.0.1p0
Firefox segfaults upon start with
msyscall f6e75108000 a7000 error
Segmentation fault (core dumped)
and the following appears in messages:
[firefox]20388/413659 pc=f6e7511847b inside f6e8575b000-f6e85766fff: bogus
syscall
gdb
This is current/arm64 on a M1 macbook, with firefox-120.0.1.
Firefox will not start, complaining that
XPCOMGlueLoad error for file /usr/local/lib/firefox/libmozwayland.so.132.0:
File not found
Couldn't load XPCOM.
Indeed, the file does not exist.
Jan
Prasad MN writes:
> Does not work for me either -- I am on the latest snapshot and
> Firefox fails with the same error as reported on the thread.
> Same error for Tor Browser.
It just takes patience. Or make. Surely you have a backup computer?
The problem was noticed and the patch push
Does not work for me either -- I am on the latest snapshot and
Firefox fails with the same error as reported on the thread.
Same error for Tor Browser.
However on my backup machine -- which has Matthieu's Wayland / Sway ports
installed -- both Firefox and Tor work fine on X.
(machine is al
On Wed, Dec 13, 2023 at 9:37 AM Gabriel Brito wrote:
>
> I have the same issue on 7.4 GENERIC.MP#1485 amd64.
>
> CCing ports and maintainer.
>
> On Wed, 13 Dec 2023 at 12:31, wrote:
>
> > Running OpenBSD -current. Trying to run Firefox results in:
> >
> >
Le Wed, Dec 13, 2023 at 03:33:39PM +0100, Gabriel Brito a écrit :
> I have the same issue on 7.4 GENERIC.MP#1485 amd64.
wait for newer 120.0.1p0 packages, or use the one linked at
https://marc.info/?l=openbsd-bugs&m=170230586407997&w=2
also, reading mail archives before posting about something th
I have the same issue on 7.4 GENERIC.MP#1485 amd64.
CCing ports and maintainer.
On Wed, 13 Dec 2023 at 12:31, wrote:
> Running OpenBSD -current. Trying to run Firefox results in:
>
> /home/oscar $ firefox
> XPCOMGlueLoad error for file /usr/local/lib/firefox/libmozwayland.so.132.0
Le Mon, Dec 11, 2023 at 07:59:05AM +0100, Matthias Schmidt a écrit :
> > Hi,
> >
> > I just upgraded Firefox on -current to firefox-120.0.1 and it fails
> > with:
> >
> > XPCOMGlueLoad error for file /usr/local/lib/firefox/libmozwayland.so.132.0:
> > F
FYI: https://marc.info/?l=openbsd-ports&m=170228767826863&w=2
* Robert Palm wrote:
> Just noticed firefox seems not working:
>
> GENERIC.MP#1483 amd64
>
> tron$ pkg_info firefox
> Information for inst:firefox-120.0.1
>
>
> tron$ firefox
> XPCOMGlueLoad
Just noticed firefox seems not working:
GENERIC.MP#1483 amd64
tron$ pkg_info firefox
Information for inst:firefox-120.0.1
tron$ firefox
XPCOMGlueLoad error for file /usr/local/lib/firefox/libmozwayland.so.132.0:
File not found
Couldn't load XPCOM.
Le Mon, Dec 11, 2023 at 08:58:17AM +0100, Landry Breuil a écrit :
> Le Mon, Dec 11, 2023 at 07:59:05AM +0100, Matthias Schmidt a écrit :
> > Hi,
> >
> > I just upgraded Firefox on -current to firefox-120.0.1 and it fails
> > with:
> >
> > XPCOMGlueLoa
Le Mon, Dec 11, 2023 at 07:59:05AM +0100, Matthias Schmidt a écrit :
> Hi,
>
> I just upgraded Firefox on -current to firefox-120.0.1 and it fails
> with:
>
> XPCOMGlueLoad error for file /usr/local/lib/firefox/libmozwayland.so.132.0:
> File not found
> Couldn't load
Le Sat, Dec 09, 2023 at 11:36:48PM -0800, Greg Steuck a écrit :
> Greg Steuck writes:
>
> > So I was wondering which program is responsible (because my previous
> > "fix" was to restart the X session). Turns out exiting firefox is
> > enough to get the device ba
Hi,
I just upgraded Firefox on -current to firefox-120.0.1 and it fails
with:
XPCOMGlueLoad error for file /usr/local/lib/firefox/libmozwayland.so.132.0:
File not found
Couldn't load XPCOM.
Cheers
Matthias
Greg Steuck writes:
> So I was wondering which program is responsible (because my previous
> "fix" was to restart the X session). Turns out exiting firefox is
> enough to get the device back.
I don't understand how or why firefox decides that it should hold on to
fid
probably https://marc.info/?l=openbsd-tech&m=155102311608275&w=2
On 2023/11/11 15:52, Caspar Schutijser wrote:
> Hi,
>
> Firefox on my arm64 M1 MacBook (dmesg below) crashes with a
> pledge violation when I visit a certain website (no interaction needed,
> just wait a co
Hi,
Firefox on my arm64 M1 MacBook (dmesg below) crashes with a
pledge violation when I visit a certain website (no interaction needed,
just wait a couple of seconds for the page to load). On
my amd64 laptops, there is no such issue.
$ firefox https://mijn.ing.nl/
Exiting due to channel error
Le Sun, Nov 05, 2023 at 03:08:54AM +, unnamed_maker...@aleeas.com a écrit :
> (sorry for the duplicate post - it seems the first attempt was not in plain
> text - oops)
>
> On the latest OpenBSD amd64 release, since Firefox 117 (I think), graphics
> acceleration has been
(sorry for the duplicate post - it seems the first attempt was not in plain
text - oops)
On the latest OpenBSD amd64 release, since Firefox 117 (I think), graphics
acceleration has been broken and the following error messages are produced when
firefox is launched:
Crash Annotation
On the latest OpenBSD amd64 release, since Firefox 117 (I think), graphics
acceleration has been broken and the following error messages are produced when
firefox is launched:
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: vaapitest: ERROR
(t=0.780224) [GFX1-]: vaapitest: ERROR
Crash
On the latest OpenBSD amd64 release, since Firefox 117 (I think), graphics
acceleration has been broken and the following error messages are produced when
firefox is launched:
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: vaapitest: ERROR
(t=0.780224) [GFX1-]: vaapitest: ERROR
Crash
/llvm/llvm-project/commit/2456e11614c10a2e648005e27e3213c77b7ab7a4)
that allows me to fix that if backported to our llvm (a manually fixed
wasm header fixes the build issue).
or with various hacks i can jump to llvm 16 but that might be a bit
early for the ports-tree. I've been able to build a working firefox 1
if it's not an issue happening only on OpenBSD, then
> > > > dealing with upstream is the way to go.
> > >
> > > I used ktrace. It's unveil. The fix is to add "/etc/localtime r"
> > > to /etc/firefox/unveil.content
> >
> >
ions
> > > might help... and if it's not an issue happening only on OpenBSD, then
> > > dealing with upstream is the way to go.
> >
> > I used ktrace. It's unveil. The fix is to add "/etc/localtime r"
> > to /etc/firefox/unveil.content
>
>
dealing with upstream is the way to go.
>
> I used ktrace. It's unveil. The fix is to add "/etc/localtime r"
> to /etc/firefox/unveil.content
many thanks george for the time spend of this and this detailed
analysis. Definitely ok for me to add `/etc/localtime r` to
/
upstream is the way to go.
>
> I used ktrace. It's unveil. The fix is to add "/etc/localtime r"
> to /etc/firefox/unveil.content
>
> The problem happens during dst (daylight saving time, summer time).
> Firefox has its own dst rules, but needs the name of my zo
Using ktrace to figure out which
> files the browser tries to access when handling date-related functions
> might help... and if it's not an issue happening only on OpenBSD, then
> dealing with upstream is the way to go.
I used ktrace. It's unveil. The fix is to add "/etc/localti
On Sat, Aug 5, 2023 at 02:49 Landry Breuil wrote:
> Le Thu, Aug 03, 2023 at 05:28:45PM -0600, Morgan Aldridge a écrit :
> > On 2021-04-29, Marfaba Stewart wrote:
> >
> > > I think this is a Firefox bug and have reported it to Mozilla.
>
> Where have y
Le Thu, Aug 03, 2023 at 05:28:45PM -0600, Morgan Aldridge a écrit :
> On 2021-04-29, Marfaba Stewart wrote:
>
> > I think this is a Firefox bug and have reported it to Mozilla.
Where have you reported it exactly ? https://bugzilla.mozilla.org ? if
so, which bug number ? i dont see
t; to hear it reading out elements, texts, etc.
>
> I'm new to accessibility features and noticed that browsers wouldn't work
> whereas other ports without pledge/unveil would.
>
> Patch is for Firefox and Firefox ESR.
> Will check the Chromes next.
>
> Feedback? Objection? OK?
sure ok :)
nd noticed that browsers wouldn't work
whereas other ports without pledge/unveil would.
Patch is for Firefox and Firefox ESR.
Will check the Chromes next.
Feedback? Objection? OK?
Index: www/firefox-esr/Makefile
===
RCS file: /cvs/p
On 2021-04-29, Marfaba Stewart wrote:
> I'm confused about Firefox's handling of Date objects on OpenBSD.
>
> Why: Some Firefox browser extensions that display dates using
> Date.toLocaleString or Date.toLocaleDateString can cause an incorrect
> date to be displayed. Fo
Greg Steuck writes:
> firefox 113.0 crashes for me on amd64 with the message above and prints
> this to its output when opening a folder full of pictures on
> dropbox.com.
Chances are, this is https://bugzilla.mozilla.org/show_bug.cgi?id=1829641
which is supposedly fixed in 114.
firefox 113.0 crashes for me on amd64 with the message above and prints
this to its output when opening a folder full of pictures on
dropbox.com.
[Parent 10375, IPC I/O Parent] WARNING: process 2097 exited on signal 11: file
/usr/obj/ports/firefox-113.0/firefox-113.0/ipc/chromium/src/base
il 2023 11:38:35 Landry Breuil wrote:
Le Wed, Apr 12, 2023 at 11:11:01AM +0200, Jan Stary a écrit :
This is current/arm64 on an Apple M1 MacBook Air (dmesg below).
While everything mostly works, Firefox keeps crashing.
Reproducibly, it always crashes on calendar.google.com;
_sometimes_ it cr
Le Wed, Apr 12, 2023 at 11:11:01AM +0200, Jan Stary a écrit :
> This is current/arm64 on an Apple M1 MacBook Air (dmesg below).
> While everything mostly works, Firefox keeps crashing.
>
> Reproducibly, it always crashes on calendar.google.com;
> _sometimes_ it crashes when playin
On 12/04/23 10:27 +0100, Stuart Henderson wrote:
> On 2023/04/12 11:15, Jan Stary wrote:
> > On Apr 12 11:11:01, h...@stare.cz wrote:
> > > This is current/arm64 on an Apple M1 MacBook Air (dmesg below).
> > > While everything mostly works, Firefox keeps crashing.
&g
1 - 100 of 1038 matches
Mail list logo
