Closed Bug 13544 Opened 25 years ago Closed 25 years ago

[PP]complete crash of Linux 6.0 while running Milestone 9

Categories

(Core :: Networking, defect, P3)

x86
Linux
defect

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: robhb, Assigned: gagan)

Details

Downloaded binary of M9, ran successfully. Then, as root, ran mozilla-apprunner in KDE without having a ppp connection first. Browser was created, terminal reflected error loading URL (since I had no ppp connection at the time). Tried to view menus on menu bar, they were extremely slow to respond and would show multiple menus simultaneously. Then I noticed that I could not do anything on the computer. Mouse pointer moves with mouse movement, but no other input has any effect. Cannot change focus of windows. Cannot get KDE menus. Cannot ctrl-alt-backspace to restart X server. Cannot switch to a virtual terminal to kill the process. Cannot get a new xterm or alt-f2 to get KDE CLI to kill process. Looks like reboot time.
Assignee: don → gagan
Component: Browser-General → Networking-Core
QA Contact: leger → tever
Summary: complete crash of Linux 6.0 while running Milestone 9 → [PP]complete crash of Linux 6.0 while running Milestone 9
tever, I think this is a known bug. Can you find dup?
I have seen this too once or twice before with SUSE 6.0. But I don't thimk it's related to apprunner. I think it's an KDE problem. The menu-problems are just the usual sluggish XP-Menu stuff. I'm working most of the time without ppp connection, so I think this is also not related. I can't test any further, because I switched to SUSE 6.2 and a newer KDE. Never happend again, but I probably should not say that ...
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
robhb@dclink.com: Pls. open again if you are continuing to see this. Also let us know of the make/version of Linux you are using. I am going to close this for now.
Bulk move of all Networking-Core (to be deleted component) bugs to new Networking component.
Status: RESOLVED → VERIFIED
marking Verified.
You need to log in before you can comment on or make changes to this bug.