Wierd Xorg and Fluxbox menu behavior!
jmarquez at telenetwork.com
Mon Oct 4 10:22:55 PDT 2004
I'm having a wierd issue with my current setup. I've just recently
updated my source and have done build world and all that jazz. I may
have done something wrong during mergemaster because now I'm unable to
run Xorg properly. I've pin pointed the problem to the fluxbox menu.
This is all under the user enviorment, I can right click on my mouse to
pull up the fluxbox menu and I can scroll down with my mouse and select
any of the first three options(eterm, firefox, run). As soon as my mouse
goes over one of the listed directories, say for example "Terminals ->"
, X crashes! The wierd thing about this situation is when I use my
keyboard arrors instead of my mouse to scroll down the fluxbox menu, I'm
able to go over the directories and navigate just fine! Log files don't
say much about it either.......
"kernel: pid 11967 (fluxbox), uid 1001: exited on signal 10 (core dumped)"
-----/var/log/Xorg.0.log---- last few lines
(**) Option "CorePointer"
(**) Mouse0: Core Pointer
(**) Option "Device" "/dev/sysmouse"
(**) Option "Buttons" "6"
(**) Mouse0: Emulate3Buttons, Emulate3Timeout: 50
(**) Option "ZAxisMapping" "4 5"
(**) Mouse0: ZAxisMapping: buttons 4 and 5
(**) Mouse0: Buttons: 6
(II) Keyboard "Keyboard0" handled by legacy driver
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
(II) Mouse0: SetupAuto: hw.iftype is 4, hw.model is 0
(II) Mouse0: SetupAuto: protocol is SysMouse
(II) RADEON(0): [drm] removed 1 reserved context for kernel
(II) RADEON(0): [drm] unmapping 8192 bytes of SAREA 0xc2514000 at 0x282f9000
(==) RADEON(0): Write-combining range (0xa0000,0x10000) was already clear
Log File: log
Fluxbox version: 0.9.10
Compiled: Oct 2 2004 13:13:07
Compiler version: 3.4.2 [FreeBSD] 20040728
Compiled options (- => disabled):
Error: Can not connect to X server.
Make sure you started X before you start Fluxbox.
I've allready tried reinstalling Xorg, fluxbox, running a portupgrade -arR.....doh! My config files seem okay, any idea guys?
over and out
More information about the freebsd-current