Hi Urs, Troy, On Sat, 16 Sep 2006, Urs Beyerle wrote: > Hi Troy, > > I have just checked thunderbird-1.5.0.7, firefox-1.5.0.7 and > seamonkey-1.0.5. > The init.d scripts still does not work with seamonkey, but works with > thunderbird and firefox. > > In case of firefox: /usr/bin/firefox starts > /usr/lib/firefox-1.5.0.7/firefox, which runs > /usr/lib/firefox-1.5.0.7/firefox-bin. The "init.d" part is in > /usr/lib/firefox-1.5.0.7/firefox. > > Whereas /usr/bin/mozilla starts directly > usr/lib/mozilla-seamonkey-1.0.5/mozilla-bin. > The "init.d" is still part of the mozilla/seamonkey source code > (mozilla/xpfe/bootstrap/mozilla.in), but never gets to the RPM. The > "buggy" /usr/bin/mozilla is provided by TUV (Source1: mozilla.sh.in). > > How should we fix the parentlock problem for seamonkey, if we can not > rely on its init.d feature? Maybe by adding this to the seamonkey trigger? (beware of linebreaks) sed -i 's@^[[:space:]]*exec \$MOZ_PROGRAM@[ -x $MOZ_DIST_BIN/init.d/S01parentlock ] \&\& $MOZ_DIST_BIN/init.d/S01parentlock\n&@' /usr/bin/mozilla || : If init.d comes back, we remove that line from the trigger (or not, who cares). Cheers, Stephan -- Stephan Wiesand DESY - DV - Phone: +49 33762 7 7370 Platanenallee 6 Fax: +49 33762 7 7216 15738 Zeuthen, Germany