[3.0.0.8] [Sailfish X] [browser] sailfish-browser crashes: broken, missing, or disappeared libxul.so?

asked 2018-11-10 12:47:47 +0200

mniemi
198 ●5 ●7 ●9

updated 2018-12-10 01:53:03 +0200

carmenfdezb
1051 ●13 ●34 ●30

I happily unlocked and flashed an Xperia XA2 dual sim version and finally (after third try) got it up and running last night (with the help of the additional complementary instructions). The fresh install worked fine and I was able to install a couple of additional apps, too. I kept the sailfish-browser on all the time and was able to nicely browse several sites in a normal manner.

However, this morning I rebooted the Xperia XA2 (for the first time, I guess). After that, the sailfish-browser did not start anymore, and it has kept hanging since that - not starting anymore. As I try to restart it from the command line, there appears to be a "segmentation fault" with the following indication about missing libxul.so:

[nemo@Sailfish ~]$ sailfish-browser
[D] unknown:0 - Using Wayland-EGL
greHome from GRE_HOME:/usr/bin
libxul.so is not found, in /usr/bin/libxul.so
XPCOMGlueLoad error for file /usr/lib/xulrunner-qt5-38.8.0/libxul.so:
/usr/lib/libpango-1.0.so.0: undefined symbol: fribidi_get_par_embedding_levels_ex
Could not start XPCOM glue:/usr/lib/xulrunner-qt5-38.8.0/libxul.so.
Segmentation fault
[nemo@Sailfish ~]$

I wonder what might have caused something like this? Naturally, it may be that some additional apps could have tampered the installation somehow, but that sounds strange, as they were same apps that I had in my previous Jolla 1 and Jolla C, too.

Reinstalling libxul.so somehow would be my initial idea to recover from this, but I do not have a real idea on how to do that. I already removed and reinstalled the sailfish-browser with the commands pkcon remove sailfish-browser and pkcon install sailfish-browser but that did not help.

EDIT: Finally, I ended up reinstalling Sailfish X again to my Xperia XA2 (dual sim) as the installation was a relatively fresh one and no valuable personal data had yet been stored to the device. Therefore, in my case, this error remains a mystery without a real solution.