Page 1 of 1
[Linux] browser not launching, "couldn't load XPCOM"; package issue?
Posted: 2024-10-01, 20:56
by shupliance
Operating system: Nobara 40 (Fedora 40)
Browser version: 33.3.1
32-bit or 64-bit browser?: 64-bit
Problem URL: ?
Browser theme (if not default): N/A
Installed add-ons: N/A
Installed plugins: (about:plugins): N/A
when i attempt to run the browser, i receive the following terminal error: XPCOMGlueLoad error for file /home/username/Desktop/software/palemoon/libxul.so: libdbus-glib-1.so.2: cannot open shared object file: No such file or directory Couldn't load XPCOM
i've installed/updated the packages for gtk3 and tried to for whatever libdbus-glib-1.so.2 is, but nothing seems to be working and i get the same error out of it every time. the browser has not yet opened on this machine, it's been doing this since the first boot. i don't know what i could possibly be missing, and i've looked through every thread i could find on related issues, which were mostly on windows, so here i am! please help
Re: [Linux] browser not launching, "couldn't load XPCOM"; package issue?
Posted: 2024-10-03, 03:57
by andyprough
What happens if you open a terminal and go to the directory where you downloaded and unpacked the Pale Moon tarball? Can you run Pale Moon from the terminal from that directory?
For me I would run the following two commands:
If that doesn't open the Pale Moon browser for you, then what is the error that spits out in your terminal? Is it still the same error? And what is the output from the following command (run it in the ~/palemoon/ directory, or wherever you unpacked the Pale Moon tarball):
Re: [Linux] browser not launching, "couldn't load XPCOM"; package issue?
Posted: 2024-10-03, 04:12
by shupliance
andyprough wrote: ↑2024-10-03, 03:57
What happens if you open a terminal and go to the directory where you downloaded and unpacked the Pale Moon tarball? Can you run Pale Moon from the terminal from that directory?
For me I would run the following two commands:
that is what i was already doing to achieve the error posted before, as the executable doesn't seem to do anything at all. likely due to the same error?
the output of the command ldd ./palemoon is as follows:
Code: Select all
linux-vdso.so.1 (0x00007f9bc221d000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f9bc21ef000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f9bc21ea000)
libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007f9bc1e00000)
libm.so.6 => /lib64/libm.so.6 (0x00007f9bc2106000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f9bc20d8000)
libc.so.6 => /lib64/libc.so.6 (0x00007f9bc1c0f000)
/lib64/ld-linux-x86-64.so.2 (0x00007f9bc221f000)
Re: [Linux] browser not launching, "couldn't load XPCOM"; package issue?
Posted: 2024-10-03, 10:40
by micwoj92
You need to install `dbus-glib` package.
Re: [Linux] browser not launching, "couldn't load XPCOM"; package issue?
Posted: 2024-10-03, 19:54
by shupliance
micwoj92 wrote: ↑2024-10-03, 10:40
You need to install `dbus-glib` package.
i have this package installed. this was the first solution i tried, it does not work for me unfortunately.
Re: [Linux] browser not launching, "couldn't load XPCOM"; package issue?
Posted: 2024-10-03, 20:37
by micwoj92
You either don't or your system is fucked, I just tried this on fresh fedora40 machine:
Code: Select all
user@fedora:~$ tar xf palemoon-33.3.1.linux-x86_64-gtk3.tar.xz
user@fedora:~$ cd palemoon/
user@fedora:~/palemoon$ file /usr/lib64/libdbus-glib-1.so.2
/usr/lib64/libdbus-glib-1.so.2: symbolic link to libdbus-glib-1.so.2.3.5
user@fedora:~/palemoon$ ./palemoon
(pale moon:2859): GLib-CRITICAL **: 23:24:03.457: g_find_program_for_path: assertion 'program != NULL' failed
(pale moon:2859): GLib-CRITICAL **: 23:24:03.458: g_find_program_for_path: assertion 'program != NULL' failed
This runs as expected, when I removed dbus-glib I get the same error you are having:
Code: Select all
user@fedora:~/palemoon$ ./palemoon
XPCOMGlueLoad error for file /home/user/palemoon/libxul.so:
libdbus-glib-1.so.2: cannot open shared object file: No such file or directory
Couldn't load XPCOM.
And finally, if you run
Code: Select all
ldconfig -v 2>/dev/null | grep -v ^$'\t'
You should see /lib and /lib64 directories as output.
EDIT:
You can even run ldd on the file (what I assume andyprough meant), but you need to run it on the right libxul file, top output with installed, bottom with uninstalled.
Code: Select all
ldd ./libxul.so | grep dbus
libdbus-glib-1.so.2 => /lib64/libdbus-glib-1.so.2 (0x00007f0d6e664000)
libdbus-1.so.3 => /lib64/libdbus-1.so.3 (0x00007f0d6e610000)
Code: Select all
ldd ./libxul.so | grep dbus
libdbus-glib-1.so.2 => not found
libdbus-1.so.3 => /lib64/libdbus-1.so.3 (0x00007f5f34c3e000)