Hi.
My FireFox instantly crashes when launching, using the safe-mode doesn’t help. I suspect it could have something to do with MESA; my gfx card is a bit oldish and had some trouble with newer applications. But SuperTuxKart and most games still do run, so this assumption is a bit shallow to go out and start to kick around my gfx-drivers.
But if I check the details in current crashes, I get: ec8030f7-c20a-464f-9b0e-13a3a9e97384; this, however is not submitted even though both the crash window and submit.log say so.
Any ideas what I could do to fix this? Firefox ESR does work for the moment. I was recommended to come here to ask by the mentioned guy on Lemmy who had no idea anymore himself ;).
You’re a little bit unspecific about which Mozilla Firefox version.
It seems that, the current default Tumbleweed version is 114.0.1 – here on Leap 15.5 it’s 102.12.0esr.
The ESR version on Leap is executing perfectly.
The Tumbleweed version seems to have passed OpenQA and therefore, should execute without any issues arising.
Please tell us which Firefox version you’re using.
Please also tell us, from where you obtained the Firefox package which is causing your crashes.
Hi, thanks for the Welcome and the Replies :).
My current Version is 114.0.1-4.1 from https://download.opensuse.org/repositories/mozilla/openSUSE_Tumbleweed/; had the version (114.0.1-1.2) from the default repo before and switched to the mozilla Repo in an attempt to get rid of the problem (it didn’t help).
@hui: Oh, so it’s not my graphic card? Does this mean it is likely to be fixed? =)
The dev on the bug report provides a recent link to a fresh download of FF to test out . . . this problem happened to me on my Gecko rolling distro install a few days back. So far does not seem like the fix has been made “downstream” from the Firefox offering . . . today I’m in TW and I’m not running the zypper through until there is some “all clear” message on the issue.
It’s up in hui’s post number two, which goes to the bugzilla bug report, and in there is the link that they are checking to see if that fixes the problem. But, I’ll post that link here, have to scroll down in the bug report to find the latest link . . . .
What is not working?? The link? or Firefox?? You might have to register with bugzilla? If it’s Firefox, then as hui said, that is “known” . . . the question will be on the when the fix will be in the tubes.
In brief reading of the posts in the bug report, it seems like aspects of one’s Firefox profile were also messed with . . . so it seems “messy” right now. Hopefully when the actual fix gets into the zypper realm that the fix will be “easy-peasy”???
Well, you could report your experience on the bug report, letting Wolfgang know that that didn’t work for you.
From a fast scan of the bug report it does seem like it’s a bit more complicated than just downloading the file directly from Mozilla’s site (one option) and installing it . . . . It also seemed like the problem upgrade messes with the user profile/config info??? It looks like some careful reading of the bug report posts is required to get it fixed??
Looks like there is another download option posted by Wolfgang that worked for one guy and another post where they ran some additonal commands to something and they are back in biz??
(In reply to Wolfgang Rosenauer from comment #54) > There is another build with a different build change: > https://download.opensuse.org/repositories/mozilla/openSUSE_Tumbleweed/ > x86_64/MozillaFirefox-114.0.1-5.1.x86_64.rpm > > Please try and report if it changes anything. I upgraded my laptop to this version and it opens OK now. My laptop is an ASUS with an Intel(R) Celeron(R) N4500 @ 1.10GHz Running tumbleweed:20230617 and firefox failed to open with the 114 update from the other day. Thanks, Edward
Comment 56 Andreas Stieger 2023-06-19 21:42:06 UTC
-ac_add_options --enable-lto +#ac_add_options --enable-lto that did the trick.
AFAICS, it’s “Work In Progress” …
Please be aware that, once the repair has been done, there’s a wait until the OpenQA tests have been successfully executed.
Which brings me to another issue –
AFAICS, there’s very little chance with Tumbleweed to revert to a previous version of an RPM package.
Apart from, assuming Btrfs and Snapper, reverting to a previous local version …
Does anyone happen to know if, for the case that a new package version misbehaves, Tumbleweed will restore the last previous known good version to the repository/repositories?
@dcurtisfra yes with a bug report or talk direct to folks, I got vagrant reverted last week, but it’s been fixed and updated again…
defolos, yup, vagrant keeps wanting the vagrant password now when I bring up my cluster nodes
“defolos, yup, vagrant keeps…” ← terrific
DimStar can we revert the vagrant version bump?
I don’t have time to look into it this week
defolos: sure… submit a revert SR: osc sr openSUSE:Factory vagrant -r 50 --nodevel openSUSE:Factory -m ‘Revert to 2.3.4’
Just got home after being overseas for several weeks. Updated. And same problem with Firefox. I’m a little late to the party. This link appears to be no longer available:
So right now, I’m dead in the water. Oddly, I looked through my system snapshot and couldn’t locate Mozilla/Firefox. Is there another link to a provisional version?