Under GNOME 1.0 on RH5.2 (all updates applied), Netscape Communicator 4.6 will occasionally cause the entire system to lock up completely. X no longer responds (ctrl-backspace doesn't work nor does atl-Fn) to keyboard or mouse. The machine no longer responds to ping (or ARP). Network interface is Intel EtherExpress Pro 10/100 using driver v1.08 of 5/3/99. Configured to force 10Mbit. This could be a GNOME bug, I've had the system die similarly from GNOME but can't quite characterize what I was doing. In Netscape, I was on an ftp site with a long listing of files and mousing madly on the scroll bar . Then everything froze. The ftp site was rufus.w3.org and I was in RPMs for the letter 'P' I believe. The x11 log shows "Gdk-Message: Got event for unknown window: 0" . Alas, these messages don't have a timestamp on them. I think in future I shall pipe them to logger so they are timestamped, rather than just redirect to file. I perused /var/log/messages, didn't see anything recent that applied although hours ago was a message from the Ethernet card that the transmitter timed out and it restarted. As there were IP-related (ident) messages seconds later, presumably the restart was successful.
*** Bug 4180 has been marked as a duplicate of this bug. *** Under GNOME 1.0 on RH5.2 (all updates applied), Netscape Communicator 4.6 will occasionally cause the entire system to lock up completely. X no longer responds (ctrl-backspace doesn't work nor does atl-Fn) to keyboard or mouse. The machine no longer responds to ping (or ARP). Network interface is Intel EtherExpress Pro 10/100 using driver v1.08 of 5/3/99. Configured to force 10Mbit. This could be a GNOME bug, I've had the system die similarly from GNOME but can't quite characterize what I was doing. In Netscape, I was on an ftp site with a long listing of files and mousing madly on the scroll bar . Then everything froze. The ftp site was rufus.w3.org and I was in RPMs for the letter 'P' I believe. The x11 log shows "Gdk-Message: Got event for unknown window: 0" . Alas, these messages don't have a timestamp on them. I think in future I shall pipe them to logger so they are timestamped, rather than just redirect to file. I perused /var/log/messages, didn't see anything recent that applied although hours ago was a message from the Ethernet card that the transmitter timed out and it restarted. As there were IP-related (ident) messages seconds later, presumably the restart was successful.
*** This bug has been marked as a duplicate of 3505 ***