When I start mozilla, it creates several threads but doesn't show any
window (nor galeon show anything).
When I tried same version (0.7-4) from RH rawhide, it works well (even with
(Pentium 150, S3Virge/GX2 - XF3.3.6-SVGA, 800x600, Window Maker).
Do you have the flash plugin installed?
No, I have not installed any additional plugins (nor macromedia flash) and I
Are you trying to run galeon and mozilla at the same time? What happens if you
make sure that all processes are dead ( galeon and mozilla ) and try starting
I'm not running two different browsers at the same time nor two different
versions of mozilla at the same time (I know how it handles this ...).
Between all of my tests I terminated/killed all of running threads/processes of
mozilla and I have also tried to restart X for sure ...
Mozilla 0.7-4 from Rawhide works.
(Mozilla 0.7-3 from Rawhide last week also worked).
Mozilla 0.7-4 from fisher doesn't. (I have upgraded to fisher today).
Then I downgraded Mozilla from fisher to Mozilla 0.7-4 from Rawhide => it works!.
(I have repeated downgrade/upgrade fisher's/rawhide 0.7-4 twice with same results).
When I tried todays tar.gz snapshot from official mozilla's FTP, it behaves the
same as "fisher's" Mozilla-0.7-4 (start threads with almost no CPU usage and no
... and mozilla I downloaded today from official mozilla ftp works OK.
(2001-02-01 22:28 mozilla-i686-pc-linux-gnu.tar.gz)
Can you try the 0.7-10 from rawhide? It's up there now.
Yes, I have tried 0.7-10 from rawhide and it does not work (doesn't show any
window, doesn't eat a CPU, and I made sure all processes/threads/browsers were
not running before ...). Am I the only one who reports this? If anybody wants
more information about my hardware/software/configuration ... I'm here to serve ...
Well, there must be something else involved, because when I downloaded 0.7-10
from blizzard's homepage at people.redhat- it works! But md5sums show that they
are same ... I don't understand that ...
I have never seen similar problems ... sorry for making false alarm, the problem
is probably somewhere else. (I think it's time to change STATUS of this "bug")
Strange. Maybe you had something left behind on the filesystem or something.