The first line (“Glib-CRITICAL”) is not a problem as far as I know.
So I did:
cd .mozilla
mv seamonkey seamonkey.old
and then seamonkey started without a problem. So there’s an issue in my profile that I will need to investigate. I don’t normally use seamonkey, so not an urgent problem here.
On the other hand, firefox is working here without any problems.
I realise that /usr/bin/seamonkey is a scriot that ultimately calls /usr/lib64/seamonkey/seamonkey-bin
but not sure how to find what is crashing
…Just called under gdb – not much help
(gdb) run
Starting program: /usr/lib64/seamonkey/seamonkey-bin
Got object file from memory but can’t read symbols: File truncated.
[Thread debugging using libthread_db enabled]
Using host libthread_db library “/lib64/libthread_db.so.1”.
(process:17518): GLib-CRITICAL **: g_slice_set_config: assertion ‘sys_page_size == 0’ failed
Detaching after fork from child process 17527.
[New Thread 0x7fffe54f0700 (LWP 17528)]
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7df024e in _dl_runtime_resolve () from /lib64/ld-linux-x86-64.so.2
(gdb) where #0 0x00007ffff7df024e in _dl_runtime_resolve () at /lib64/ld-linux-x86-64.so.2 #1 0x00007ffff1ad6ac8 in () at /usr/lib64/seamonkey/libxul.so
…
Quite. That was not my worry but included for accuracy.
My complaint was tat seamonkey segv’ed. I have “fixed” this by deleting te .mozila/seamonkey file, but I have no idea why tis happened, which gives a freeling of insecurity. and loss of bookmarks and passwiords