We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Sök i support

Akta dig för supportbedrägerier: Vi kommer aldrig att be dig att ringa eller skicka ett sms till ett telefonnummer eller dela personlig information. Rapportera misstänkt aktivitet med alternativet "Rapportera missbruk".

Läs mer

Centos 7.6.1810 + firefox.x86_64 0:60.9.0-1.el7.centos => GLib-GObject-CRITICAL **: ...: g_object_ref: assertion 'object->ref_count > 0' failed

more options

Hello !

I have a physical machine with Centos 7.6.1810 and Firefox 60.9.0-1.el7.centos installed.

I start a Xvfb, and try to start firefox, and get this output: Running without a11y support!

 (firefox:7740): GLib-GObject-CRITICAL **: 23:18:17.497: g_object_ref: assertion 'object->ref_count > 0' failed
 Segmentation fault

I tried to install a virtual machine with same OS, over VirtualBox in a Win10. Same OS, same firefox rpm. I start a Xvfb and try to start firefox, and works fine.

So my physical machine has something that makes Firefox to crash and do not start.

Can someone help me ?

Hello ! I have a physical machine with Centos 7.6.1810 and Firefox 60.9.0-1.el7.centos installed. I start a Xvfb, and try to start firefox, and get this output: '' Running without a11y support! (firefox:7740): GLib-GObject-CRITICAL **: 23:18:17.497: g_object_ref: assertion 'object->ref_count > 0' failed Segmentation fault'' I tried to install a virtual machine with same OS, over VirtualBox in a Win10. Same OS, same firefox rpm. I start a Xvfb and try to start firefox, and works fine. So my physical machine has something that makes Firefox to crash and do not start. Can someone help me ?

Alla svar (1)

more options

I have compared packages installed in the physical machine and the virtual.

I have upgraded some packages in the physical machine, in order to match the version installed in the virtual machine.

With this procedure, Firefox starts in the physical machine.

An older version of a package was the cause of the problem. The suspicious package is "gtk3", but I'm not sure. I upgraded over 15 packages.