Date: Tue, 15 Jun 1999 22:37:10 -0700 (PDT) From: dmmiller@cvzoom.net To: freebsd-gnats-submit@freebsd.org Subject: kern/12233: Fvwm2 causes FreeBSD-current to hang or reboot Message-ID: <19990616053710.B2AE714D4D@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 12233 >Category: kern >Synopsis: Fvwm2 causes FreeBSD-current to hang or reboot >Confidential: no >Severity: critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jun 15 22:40:01 PDT 1999 >Closed-Date: >Last-Modified: >Originator: Donn Miller >Release: -current >Organization: >Environment: FreeBSD lca66.cvzoom.net 4.0-CURRENT FreeBSD 4.0-CURRENT #1: Tue Jun 15 04:35:43 EDT 1999 root@lca66.cvzoom.net:/usr/src/sys/compile/CUSTOM i386 >Description: Fvwm2 (the latest version, which is 2.2.2), is causing weird problems with -current. Sometimes, if I do certain actions in fvwm2, such as selecting a menu button with the middle or right buttons, FreeBSD either locks or reboots without warning. A specific example: I was typing something in an xterm, which was hidden by another xterm. I had fvwm2 configured to have the focus follow mouse like twm. When I pressed "enter" in the xterm, which was obscured by another xterm, my machine locked solid. I tried pressing ctrl+alt+f* to get back to a VC, but I was locked out. Then, when I did cntrl+alt+backspace to kill the xserver, my machine rebooted immediately. On my computer, this will happen every once in a while while doing some routine activities in fvwm2.* By the way, I had my kernel compiled with "-mpentium -O3", and used the same flags to "make world". I also built fvwm2 and XFree86 3.3.3.1 with these flags. It may be this very reason that FreeBSD is behaving like this, the fact that egcs may cause some unstable code as compared to the old gcc-2.7*. Again, it doesn't happen very often, about once every two weeks. >How-To-Repeat: CVsup the latest -current, and run the latest version of fvwm2. It doesn't happend very often, but doing certain activities in fvwm2 may cause FreeBSD to do a sudden reboot. >Fix: Stop using fvwm2. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990616053710.B2AE714D4D>