Seamonkey Segmentation fault. Profile unrelated.

English Applications
1

Hello!
I have a mysterious problem with seamonkey which segfaults under first user account, while working under second. First thing I’ve tried is launching ‘seamonkey --ProfileManager’ and creating new profile. Unfortunately it doesn’t help. While I can run it without any problem under account user2, when I run it under account user1 I get

/usr/bin/seamonkey: line 140:  1737 Segmentation fault      $MOZ_PROGRAM "$@"

While investigating the problem I’ve found that I can run seamonkey under user1, but only in some very special ways:

su - user1 -c seamonkey

sudo -u user1 sm.sh

sm.sh:

#!/bin/bash
DISPLAY=:0
export DISPLAY
seamonkey

Interestingly enough running

su user1 -c seamonkey

(not a login shell) Also breaks with SEGFAULT.

i686 GNU/Linux
openSUSE 13.1
seamonkey 2.40-65.2 i586 openSUSE-13.1-Update

Any ideas are welcome.

2

More info.
It only happens to Seamonkey among GUI programs. Others like Firefox, Thunderbird, Chromium and Konqueror run just fine. With cli programs something very similar happens only to wget:

user1@localhost:~>wget http://www.google.com/
Segmentation fault
user1@localhost:~>

user1@localhost:~>sudo -u user1 wget http://www.google.com/
--2016-03-15 13:59:08--  http://www.google.com/
Resolving www.google.com (www.google.com)... 173.194.112.81, 173.194.112.84, 173.194.112.80, ...
Connecting to www.google.com (www.google.com)|173.194.112.81|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://www.google.de/?gfe_rd=cr&ei=GgfoVt6OL-yG8Qe_wYTABg [following]
--2016-03-15 13:59:08--  http://www.google.de/?gfe_rd=cr&ei=GgfoVt6OL-yG8Qe_wYTABg
Resolving www.google.de (www.google.de)... 216.58.208.35
Connecting to www.google.de (www.google.de)|216.58.208.35|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘index.html’

index.html                           <=>                                                     ] 154,23K  --.-KB/s   in 0,04s   

2016-03-15 13:59:09 (3,42 MB/s) - ‘index.html’ saved [157933]
user1@localhost:~>

Again, curl and others run just fine.

Any ideas are welcome.