After a few recent system updates, and trying out Wings Lite theme from the KDE store, when I try launching Pale Moon browser (installed from their repo and integrated with desktop shortcuts etc), the cursor shows the bouncing effect as usual then stops, i.e. the browser doesn’t load. If I launch it from the commandline, it immediately loads and works normally.
I reverted to the default Breeze theme and rebooted but the app still doesn’t load. I’m not sure if it has seg-faulted and would appreciate instructions on capturing the crash dump if any.
I edited the shortcut with the full path to the executable and the working directory (/usr/bin/palemoon & /usr/lib/palemoon/, respectively) but it didn’t make a difference. Since it’s in /usr/bin/ it can be invoked by just typing palemoon in Konsole.
When run from the terminal, all I see is the usual web console javascript errors and other messages replicated there - there was nothing else notable.
I thought you were able to launch it from a terminal.
Anyhow, 1) you should put the palemoon directory in /opt
2) make a link in /usr/bin to /opt/palemoon/palemoon
3) make a desktop application with exec /opt/palemoon/
That way you can launch it from a menu/desktop/panel and terminal.
i am able to launch it from a terminal, just not from the shortcut. The repo always installs it to /usr/lib and it has always run from there without problems.
If it’s crashing then shouldn’t it be possible to generate a dump file for analysis? The browser devs asked to do that to eliminate any problems on their end.
Dunno what OS you’re on, but an app from the repos will install to /usr/bin and some stuff to lib. I ditched the tar file and the previous stuff for palemoon and installed from repos. You’ll find it in /usr/bin and some in /usr/ lib.
If you want the desktop app, you just need palemoon ( /usr/bin) as executive.
I’m using KDE Neon.
The point is it was working fine before and then stopped - I need help troubleshooting what changed to make it stop. All repo installed applications here go into /usr/lib/ and their launch binaries to /usr/bin/.
You might at least get some more information out of the system by checking your system’s journals (logs) - after you try opening the program from the shortcut, hopefully there’ll be something helpful from either one of these:
sudo journalctl --since=-2m --identifier=palemoon
(Look for entries to the journal from the past 2 minutes that reference palemoon as the source)
sudo journalctl --since=-2m --grep=palemoon
(Look for entries to the journal from the past 2 minutes that have palemoon in the content of the log message)
Process 5374 (palemoon) of user 1000 dumped core.
Found module /usr/lib/palemoon/palemoon with build-id: 0b68ab2e764933b0b8a89c32403996f25ea4c498
Found module /usr/lib/x86_64-linux-gnu/libx265.so.199 with build-id: 724cf0e53c8c791c6baa015a6a8f8e83b1be6e5b
Found module /usr/lib/x86_64-linux-gnu/libx264.so.163 with build-id: b2e7160a74448d05d96f3305d73fc2316edbedaf
Found module /usr/lib/x86_64-linux-gnu/libshine.so.3.0.1 with build-id: 123d958ed2a8bf8f5ae564812db6e5266775dd28
Found module /usr/lib/x86_64-linux-gnu/libcodec2.so.1.0 with build-id: 24a8b8e35453fd42cd69d5f33561aad86e662d8e
Found module /usr/lib/x86_64-linux-gnu/libavcodec.so.58.134.100 with build-id: 275d20beefaac834b14cd4f8c8754d59beec5c48
Found module /usr/lib/x86_64-linux-gnu/libaom.so.3.3.0 with build-id: 74062a113075a6b5584e51899a5cc46bbcddffe1
Found module /usr/lib/x86_64-linux-gnu/libvpx.so.7.0.0 with build-id: 3a6da91a1b01a608e8387f09e05fa2603f9348c9
Found module /home/username/.moonchild productions/pale moon/PMProfile/extensions/moonlight@novell.com/plugins/moonlight/libmoonpluginxpi.so with build-id: be97631e00b6d313161c5f1>
Found module /usr/lib/x86_64-linux-gnu/libavutil.so.56.70.100 with build-id: abc6b699a880017e212d717fb86a1c6ea0e022e8
Found module /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0.2400.33 with build-id: 13bc23baa0b8effd8c76619ce73161e5c45ee756
Found module /home/username/.moonchild productions/pale moon/PMProfile/extensions/moonlight@novell.com/plugins/libmoonloaderxpi.so with build-id: 3543c7f7b89f31cb1399c95899bf9537a>
Found module /usr/lib/palemoon/libmozavcodec.so with build-id: 2626004f2937e5450baedf9fdbcca5b2fa222cdf
Found module /usr/lib/x86_64-linux-gnu/libxvidcore.so.4.3 with build-id: 4d1d30a6dfd58fdcadc9fbf028c73ad5797a747d
Found module /usr/lib/x86_64-linux-gnu/libdav1d.so.5.1.1 with build-id: 1333de73ba77bb82bfaf121682f00d5a9619237b
Stack trace of thread 5374:
#0 0x0000709f0ba969fc n/a (n/a + 0x0)
Sep 21 14:28:01 Bismarck drkonqi-coredump-processor[59547]: "/usr/lib/palemoon/palemoon" 5374 "/var/lib/systemd/coredump/core.palemoon.1000.482a59b9800e4e44bcd2bb5301976259.5374.1726892870000000.zst"
Sep 21 14:28:01 Bismarck drkonqi-coredump-launcher[59578]: Unable to find file for pid 5374 expected at "kcrash-metadata/palemoon.482a59b9800e4e44bcd2bb5301976259.5374.ini"
Got a reply from the repo maintainer - he had changed the desktop file to have StartupNotify=true. Reverting it fixed the issue. Thanks for trying to troubleshoot
