Avoid updating Firefox to versions 114.0 and 114.0.1 in Tumbleweed

Due to a bug, Firefox versions 114.0 and 114.0.1 in Tumbleweed are crashing at startup as described here in the bugzlila report,

Bugzilla – Bug 1212101 - Firefox 114.0 and 114.0.1 immediately crashes at startup

So, please avoid updating Firefox to these version in Tumbleweed until this bug is fixed.

2 Likes

Thanks for the information - for those who don’t know, would the recommendation be to use YaST to flag updates as ‘taboo’ before doing a zypper dup?

Yes, that would be a good idea.

1 Like

This seems again like a special case, as not all systems are affected. Im also using Firefox 114.0.1 from https://download.opensuse.org/repositories/mozilla/openSUSE_Tumbleweed/ as mentioned in the bugreport. Also using KDE Plasma but on my machine it doesn’t crash…

So not a general problem for all users…

2 Likes

I’m on Xfce and this bug is bugging me :beetle:

A problem for many users :fire: :fox_face:

Appreciate the post !

114.0.1 works here - two TW desktops and two laptops, KDE Plasma (X11).
FF 115 b also works fine.

I just updated to openSUSE Tumbleweed 20230612 and received

# zypper se -si firefox
Loading repository data...
Reading installed packages...

S  | Name                               | Type    | Version     | Arch   | Repository
---+------------------------------------+---------+-------------+--------+------------------------
i+ | MozillaFirefox                     | package | 114.0.1-1.1 | x86_64 | openSUSE Tumbleweed Oss
i  | MozillaFirefox-branding-upstream   | package | 114.0.1-1.1 | x86_64 | openSUSE Tumbleweed Oss
i  | MozillaFirefox-translations-common | package | 114.0.1-1.1 | x86_64 | openSUSE Tumbleweed Oss

which works flawless for me (I’m not using https://download.opensuse.org/repositories/mozilla/openSUSE_Tumbleweed/ but Tumbleweeds “default” OSS-repository).

I have now that firefox version after zypper dup today in tumbleweed xfce and so far so good.

Is this an issue also affecting the Flatpak version in Tumbleweed?

For one of the previous problems, Bug 1837201 I did read it was dependent on the what is stored on your PC so the cache?

We assume the reason for this to be old metadata files on disk containing origin types that are now unsupported.

That is different for every user so I think it is hard to say.

For people that like to experiment it is a good experiment to create new Firefox user and see if they can reproduce the problem with that.

1 Like

Thank you, very informative.

As not all 114.0 users are affected by this, could be related to graphic card drivers?

This bug affects machines running different CPUs, GPUs and DEs. So, sadly one can’t pinpoint the blame at a particular CPU, GPU or DE.

I have actually tried to temporarily remove the .mozilla folder, without success.
Laptop with Intel N6000.

Yup, that doesn’t seem to fix this issue. Other people have also tried firefox-114.0.1.tar.bz2 from Mozilla and that has resulted in the same error.

I wonder if it is the Intel gen 11 CPU and newer and 6.3.6 CPU with ibt enabled are the Firefox issue as my gen 10 does not have any issue with Firefox.

Indirect Branching has to be set in a Table and passed to the kernel for permission to work if ibt is enabled - virtualbox will not run unless ibt=no is set in the kernel. I wonder if that is the Firefox issue as well. Try booting with ibt=no on bootup.

you can follow that here:

@larryr I installed MozillaFirefox (rpm not flatpak) on MicroOS Aeon (X11), its an N100 cpu with ibt (not disabled) and it runs fine…

 inxi -Fxxz
System:
  Kernel: 6.3.7-1-default arch: x86_64 bits: 64 compiler: gcc v: 13.1.1 Console: pty pts/0 DM: GDM
    Distro: openSUSE MicroOS
Machine:
  Type: Desktop Mobo: AZW model: MINI S v: 10 serial: N/A UEFI: American Megatrends LLC.
    v: ADLNV104 date: 02/06/2023
CPU:
  Info: quad core model: Intel N100 bits: 64 type: MCP arch: Alder Lake rev: 0 cache: L1: 384 KiB
    L2: 2 MiB L3: 6 MiB
  Speed (MHz): avg: 775 high: 800 min/max: 700/3400 cores: 1: 800 2: 800 3: 700 4: 800
    bogomips: 6451
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Alder Lake-N [UHD Graphics] driver: i915 v: kernel arch: Gen-12.2 ports:
    active: HDMI-A-1 empty: HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:46d1
  Display: server: X.org v: 1.21.1.8 with: Xwayland v: 23.1.2 compositor: gnome-shell driver: X:
    loaded: modesetting alternate: fbdev,intel,vesa dri: iris gpu: i915 tty: 173x18
  Monitor-1: HDMI-A-1 model: AAA res: 1920x1080
  API: OpenGL Message: GL data unavailable in console for root.
Audio:
  Device-1: Intel driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:54c8
  API: ALSA v: k6.3.7-1-default status: kernel-api
  Server-1: PipeWire v: 0.3.71 status: off with: 1: pipewire-pulse status: active 2: wireplumber
    status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
Network:
  Device-1: Intel driver: N/A port: N/A bus-ID: 00:14.3 chip-ID: 8086:54f0
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: kernel pcie:
    speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 01:00.0 chip-ID: 10ec:8168
  IF: enp1s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: N/A driver: btusb v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 1-10:3
    chip-ID: 8087:0026
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Drives:
  Local Storage: total: 1.14 TiB used: 349.49 GiB (29.9%)
  ID-1: /dev/nvme0n1 vendor: Silicon Power model: SPCC M.2 PCIe SSD size: 238.47 GiB
    speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 39.9 C
  ID-2: /dev/sda vendor: Western Digital model: WDS500G2B0A-00SM50 size: 465.76 GiB
    speed: 6.0 Gb/s serial: <filter>
  ID-3: /dev/sdb model: N/A size: 465.76 GiB type: USB rev: 3.1 spd: 5 Gb/s lanes: 1 serial: N/A
Partition:
  ID-1: / size: 237.97 GiB used: 24.86 GiB (10.4%) fs: btrfs dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 511 MiB used: 5.2 MiB (1.0%) fs: vfat dev: /dev/nvme0n1p1
  ID-3: /home size: 237.97 GiB used: 24.86 GiB (10.4%) fs: btrfs dev: /dev/nvme0n1p2
  ID-4: /opt size: 237.97 GiB used: 24.86 GiB (10.4%) fs: btrfs dev: /dev/nvme0n1p2
  ID-5: /var size: 237.97 GiB used: 24.86 GiB (10.4%) fs: btrfs dev: /dev/nvme0n1p2
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 50.0 C mobo: 45.0 C
  Fan Speeds (RPM): fan-1: 1771
  Power: 12v: N/A 5v: N/A 3.3v: 3.26 vbat: 3.04
Info:
  Processes: 252 Uptime: 0h 6m Memory: available: 15.39 GiB used: 2.34 GiB (15.2%) Init: systemd
  v: 253 default: multi-user Compilers: N/A Packages: pm: rpm pkgs: N/A note: see --rpm
  Shell: Bash v: 5.2.15 running-in: pty pts/0 inxi: 3.3.27

Your cpu does not have ibt hardware - only newer Intel i9, i7, i5 and i3 gen 11, 12 and 13 have ibt hardware.

Ibt enabled in the kernel does nothing on older cpu’s - on newer cpu’s it prevents indirect branches - often a way to get elevated privileges that malware use to bypass security.

I suspect it can break any application that uses indirect branches - I suspect Firefox might use it to do DRM.

@larryr yes it does, it’s a gen 11…

lscpu

Architecture:            x86_64
  CPU op-mode(s):        32-bit, 64-bit
  Address sizes:         39 bits physical, 48 bits virtual
  Byte Order:            Little Endian
CPU(s):                  4
  On-line CPU(s) list:   0-3
Vendor ID:               GenuineIntel
  BIOS Vendor ID:        Intel(R) Corporation
  Model name:            Intel(R) N100
    BIOS Model name:     Intel(R) N100 To Be Filled By O.E.M. CPU @ 2.8GHz
    BIOS CPU family:     1
    CPU family:          6
    Model:               190
    Thread(s) per core:  1
    Core(s) per socket:  4
    Socket(s):           1
    Stepping:            0
    CPU(s) scaling MHz:  22%
    CPU max MHz:         3400.0000
    CPU min MHz:         700.0000
    BogoMIPS:            1612.80
    Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm
                          constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx 
                         est tm2 ssse3 sdbg fma cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid
                         _fault epb cat_l2 cdp_l2 ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erm
                         s invpcid rdt_a rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_a
                         ct_window hwp_epp hwp_pkg_req umip pku ospke waitpkg gfni vaes vpclmulqdq rdpid movdiri movdir64b fsrm md_clear serialize arch_lbr ibt flush_l1d arc
                         h_capabilities
Virtualization features: 
  Virtualization:        VT-x
Caches (sum of all):     
  L1d:                   128 KiB (4 instances)
  L1i:                   256 KiB (4 instances)
  L2:                    2 MiB (1 instance)
  L3:                    6 MiB (1 instance)
NUMA:                    
  NUMA node(s):          1
  NUMA node0 CPU(s):     0-3
Vulnerabilities:         
  Itlb multihit:         Not affected
  L1tf:                  Not affected
  Mds:                   Not affected
  Meltdown:              Not affected
  Mmio stale data:       Not affected
  Retbleed:              Not affected
  Spec store bypass:     Mitigation; Speculative Store Bypass disabled via prctl
  Spectre v1:            Mitigation; usercopy/swapgs barriers and __user pointer sanitization
  Spectre v2:            Mitigation; Enhanced / Automatic IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS Not affected
  Srbds:                 Not affected
  Tsx async abort:       Not affected

See the flags, ibt…

It was a guess as to why - Intel did not say the the Celeron and N100 had ibt in their press release - so they do have ibt but do they have efficient core processors like the i5 i7 and i9 - as far as I can tell no i3 do.
The i[3,5,7,9] also have a new type of core called “efficient cores” and they can cause issues as well for threaded programs.