I added a symlink from /usr/local/bin to the entry point of seamonkey, to be able to start seamonkey using the path. This works - I can type seamonkey from a terminal window, and it starts (and shows). I then added seamonkey to the xfce menu, and, clicking nothing visible happens. Checking processes, seamonkey-bin _did_ start up though! But no window opened. This problem appears with 4.4.0 (which I had installed previously) and now with 4.4.2. I use the exact same procudure with firefox, and have no problem there. To make things more strange: if I kill the desktop, and restart it, the problem is solved (then I can start seamonkey from the menu!), but next startup, the same problem appears again. Help! John Note: I first installed seamonkey from the tar.gz, but when that didn't work, I reinstalled from the installer, just to be sure everything was ok.
Some more information. I though that it might be useful to define the startup of seamonkey in the menu as 'start in terminal', in the hope some message would appear. I get: *** glibc detected *** free(): invalid pointer: 0x08289a48 *** as only message in that window. Some googling found a suggestion to add "export MALLOC_CHECK_=0" to /etc/profile. No explanation as to what it does, and I didn't want to do that on a global level, so I tried to add it at the beginning of the seamonky startup script. It did remove the glibc error, but I get 100% CPU occupation, and still no browser.
'man malloc' will tell you what that does. MALLOC_CHECK_=0 will never actually fix anything; in your case it appears to have simply just hidden one problem and caused another.
Yes, I thought the malloc thing was a stopgap solution (thanks for explaining). I tried to compare the startup scripts for seamonkey and firefox, and was hopeful when they were similar at the start. But about a page into the scripts, there were too many differences for me to understand... I do have the impression SeaMonkey is much more dependent on command line parameters. I wonder if xfcemenu adds any when starting the program. I'll try to find that code if I have some time later. John
Nope, it'll never add params unless they're specified in the app's .desktop file.
Who is responsible for the creation of the .desktop file? I cannot find any for seamonkey, but it exists for firefox and other apps. I tried with to create one: [Desktop Entry] Name=SeaMonkey Comment=Web Browser Exec=seamonkey Icon= Terminal=0 Type=Application Categories=Application;Network; No difference at all. I noticed that the .desktop for firefox is in fact xfce4 helpers - not a laucher for the actual app. Somewhat shooting in the dark, I tried several command line options to seamonkey (adding them into the menu each time): -ProfileManager Now seamonkey doesn't even start (or aborts) -P Same -splash The Splash screen appears! But not the rest, In fact, the splash screen remains visible, it doesn't disappear as it should. Another test: I did an 'ldd' on the seamonkey-bin executable and found quite a few libraries that use library in the gnome-dirs instead of the ones in the seamonkey package. But I checked and firefox does the same, so I suspect that's ok. I give up for now - have to get some (more) work done. John
Does not look like a bug in exo, please reopen if proven otherwise.