Hi. I use Mozilla 1.7.6 under SuSE 9.2. I have severe problems very often when I want it started up. I can see the Mozilla icon is dancing, but after a short it dies. Where does Mozilla log its activities ? Erik Jakobsen
Erik, On Sunday 17 April 2005 07:35, Erik Jakobsen wrote:
Hi.
I use Mozilla 1.7.6 under SuSE 9.2.
1.7.7 is out, including a contributed gtk2+xfs build.
I have severe problems very often when I want it started up. I can see the Mozilla icon is dancing, but after a short it dies.
Where does Mozilla log its activities ?
I'd look in "~/.xsession-errors" for diagnostics related to start-up problems. I don't think Mozilla produces a separate log, but I'm not really sure about that. If it does not, then everything will be in the aforementioned file. If it does, you might be able to use this command to find it immediately following the occurrence of the symptom: find ~/.mozilla -mmin -1 This command will show the names of every file and directory in your .mozilla directory hierarchy that was modified within the preceding minute.
Erik Jakobsen
Randall Schulz
Randall R Schulz wrote:
Erik,
On Sunday 17 April 2005 07:35, Erik Jakobsen wrote:
Hi.
I use Mozilla 1.7.6 under SuSE 9.2.
1.7.7 is out, including a contributed gtk2+xfs build.
Hi Randall and thanks for your reply. I just upgraded to 1.7.7 with RedCarpet after I sent this query :-) Its working now, but dont know its stability, but time will show it.
I have severe problems very often when I want it started up. I can see the Mozilla icon is dancing, but after a short it dies.
Where does Mozilla log its activities ?
I'd look in "~/.xsession-errors" for diagnostics related to start-up problems. I don't think Mozilla produces a separate log, but I'm not really sure about that. If it does not, then everything will be in the aforementioned file. If it does, you might be able to use this command to find it immediately following the occurrence of the symptom:
find ~/.mozilla -mmin -1
This command will show the names of every file and directory in your .mozilla directory hierarchy that was modified within the preceding minute.
Thank you so much, I'm very glad for this advices and tips, that I will try if the problem persists.
Erik Jakobsen
Randall R Schulz wrote:
Where does Mozilla log its activities ?
I'd look in "~/.xsession-errors" for diagnostics related to start-up problems. I don't think Mozilla produces a separate log, but I'm not really sure about that. If it does not, then everything will be in the aforementioned file. If it does, you might be able to use this command to find it immediately following the occurrence of the symptom:
find ~/.mozilla -mmin -1
This command will show the names of every file and directory in your .mozilla directory hierarchy that was modified within the preceding minute.
Unfortunatley the problem persists. Here's the output of ~/.xsession-errors: xset: bad font path element (#64), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax xset: bad font path element (#64), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax startkde: Starting up... kbuildsycoca running... kdecore (KLibLoader): WARNING: KLibrary: /opt/kde3/lib/kde3/kcm_kdnssd.so: undefined symbol: init_kdnssd No composite extension frmshowmessages::updateFileList sending IMStart with 0 chars to 0x8236f98 sending IMEnd with 1 chars to 0x8236f98, text=í sending IMStart with 0 chars to 0x822ad18 sending IMEnd with 1 chars to 0x822ad18, text=~ /opt/mozilla/bin/mozilla.sh: line 254: 6891 Segmentation fault $MOZ_PROGRAM $MOZ_LANG And here: # find .mozilla -mmin -1 .mozilla/default/27qj5jgk.slt .mozilla/pluginreg.dat .mozilla/appreg I also have a lock file in the maildirectory 27qj5jgk.slt. Erik Jakobsen
Erik Jakobsen wrote:
Hi.
I use Mozilla 1.7.6 under SuSE 9.2.
I have severe problems very often when I want it started up. I can see the Mozilla icon is dancing, but after a short it dies.
Where does Mozilla log its activities ?
Erik Jakobsen
There is no Mozilla log that I am aware of. The segmentation fault you mentioned in a later message seems to be have been around for a long time; it happens here quite often in SuSE 9.0/Mozilla 1.4.1. Sometimes Mozilla just locks up and has to be KILLed The only way I know of to help get rid of the bug causing this is to enable Talkback in Mozilla, which you can only do at compile time. You can recompile the SuSE source rpm (after modifying the .spec file so that Talkback is enabled) or you can install a binary from the Mozilla website that already has it enabled. AFAIK SuSE compiles Mozilla with Talkback disabled, possibly because they have made some changes to the source specific to SuSE distributions. Usually in this case, one should report the bug to the guys who made the changes rather than the original authors. There is no way that I know to report this problem to SuSE in a meaningful way: all we know is Mozilla crashes, sometimes with a segfault. That isn't very helpful information. If Mozilla will not start, possibly you still have a lock file in your user profile directory. Just delete it and start Mozilla again. Usually, though, the presence of a lockfile should result in the profile selection window popping up. Another reason why Mozilla will not start is because another instance is already running. Sometimes a crash or lockup (in Mozilla) can leave Mozilla running without a visible browser window. Open a console and run: 'ps x |grep mozilla' If it is still running you will see one or more instances of /opt/mozilla/mozilla-bin which have to be KILLed. Run: 'killall -KILL mozilla-bin' I prefer to give them a "hangup" signal first, 'killall -HUP mozilla-bin' but there is usually at least one instance left behind so a KILL is needed anyway.
Darryl Gregorash wrote:
Erik Jakobsen wrote:
Hi.
I use Mozilla 1.7.6 under SuSE 9.2.
I have severe problems very often when I want it started up. I can see the Mozilla icon is dancing, but after a short it dies.
Where does Mozilla log its activities ?
Erik Jakobsen
There is no Mozilla log that I am aware of. The segmentation fault you mentioned in a later message seems to be have been around for a long time; it happens here quite often in SuSE 9.0/Mozilla 1.4.1. Sometimes Mozilla just locks up and has to be KILLed The only way I know of to help get rid of the bug causing this is to enable Talkback in Mozilla, which you can only do at compile time. You can recompile the SuSE source rpm (after modifying the .spec file so that Talkback is enabled) or you can install a binary from the Mozilla website that already has it enabled.
Ok. Thank you for the information on Talckback. How is the SuSE source recompiled, and how to modify the .spec filter. Where are the .spec filter to be found ?.
AFAIK SuSE compiles Mozilla with Talkback disabled, possibly because they have made some changes to the source specific to SuSE distributions. Usually in this case, one should report the bug to the guys who made the changes rather than the original authors. There is no way that I know to report this problem to SuSE in a meaningful way: all we know is Mozilla crashes, sometimes with a segfault. That isn't very helpful information.
You are right, but neither do I know to whom the report should be addresed to.
If Mozilla will not start, possibly you still have a lock file in your user profile directory. Just delete it and start Mozilla again. Usually, though, the presence of a lockfile should result in the profile selection window popping up.
Do you mean the .profile file in ~/.HOME ?. I encounter a lockfile in ~/.Home/.mozilla's maildirectory. Is it this one You mean ?.
Another reason why Mozilla will not start is because another instance is already running. Sometimes a crash or lockup (in Mozilla) can leave Mozilla running without a visible browser window. Open a console and run: 'ps x |grep mozilla' If it is still running you will see one or more instances of /opt/mozilla/mozilla-bin which have to be KILLed. Run: 'killall -KILL mozilla-bin' I prefer to give them a "hangup" signal first, 'killall -HUP mozilla-bin' but there is usually at least one instance left behind so a KILL is needed anyway.
Again I thank you for your advices, and I'' try to use them. Erik
participants (3)
-
Darryl Gregorash
-
Erik Jakobsen
-
Randall R Schulz