Hi!
On a completely updated Leap 15.5 with KDE I get:
~> /home/user/palemoon/palemoon
(pale moon:8009): Gtk-WARNING **: 16:12:52.396: Theme parsing error: gtk.css:1552:16: '-gtk-icon-size' is not a valid property name
(pale moon:8009): Gtk-WARNING **: 16:12:52.396: Theme parsing error: gtk.css:1555:16: '-gtk-icon-size' is not a valid property name
Segmentation fault (core dumped)
when accessing or later when loging in to some local (router) homepages.
I can’t find anything related in dmesg or journalctl.
Palemoon ist not installed, it simply runs from its directory (travel “install” so to say). It’s fully updated, most time it even segfaults when trying to update.
With the same versions of Palemoon on TW there is no problem at all…
Any idea how to debug that?
DrKonqi should have popped up with a stack trace …
- When not, “coredumpctl dump” to retrieve the core dump and, “cordumpctl debug” to retrieve a stack trace.
Raise a Pale Moon Forum entry with your stack trace: <https://forum.palemoon.org/viewforum.php?f=24>.
- Don’t bother with a KDE Bug Report …
…I copied over the profile folder from a working “install” of palemoon, problem gone. No idea why…
Didn’t change the config for some weeks and it worked some days earlier. Meanwhile I found a totally unrelated TW install that crashed, too, whe nstarting palemoon. Really, really strange. But that’S the machine with the icon-puzzeling Desktop every now and then. The install is from December on a fresh SSD with EXT4 for / and /home.
Meanwhile I’m somewhat concerned about the stability of TW (and Leap?), as this are 3 installs with strange behaviour in the last few months on (relatively) fresh SSDs. No idea what’s going on here…
@suse_rasputin:
Then, you’ll have to rename the “not working” configuration files to something which includes the date created and, compare those configurations to a working configuration file → “diff” …