Re: issues with X not loading
Yes, please see /usr/ports/UPDATING, Xorg was updated. OK, I went through and ran # portupgrade -rf libxcb which took a while to update everything, but did so without any errors (or at least without any that I caught). However, now when I startx, X loads, but I have no mouse in X. (The mouse works fine when X isn't running.) These errors are present when I switch terminals and return to the terminal X was running on: ** (xfce-mcs-manager:4299): CRITICAL **: find_master: assertion `mixer_handle != -1' failed (xfce-mcs-manager:4299): xfce-mcs-manager-WARNING **: Module /usr/local/lib/xfce4/mcs-plugins/xfce4-iconbox_settings.so cannot be opened (GModule (/usr/local/lib/xfce4/mcs-plugins/xfce4-iconbox_settings.so) initialization check failed: Incorrect module version) (Thunar:4302): thunar-vfs-WARNING **: Failed to connect to the HAL daemon: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory I have tried uninstalling (using pkg_delete) and reinstalling (using portinstall) hal, but still get this problem. I also tried adding AllowEmptyInput off in xorg.conf, but that gives an error when starting X that AllowEmptyInput is not valid. I also added the path to hald (/usr/local/sbin) to the path in /etc/rc, but still get the same error. I'm not seeing anything obvious in the /var/log/Xorg.0.log, though I do see where it sees AllowEmptyInput as on... If it makes a difference, it's a PS/2 mouse and keyboard (I'm not sure if X is receiving keyboard input, but I'm not sure how to test that without being able to click something to open some kind of window...) Thanks for any further tips. Keith ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: issues with X not loading
On Sat, 31 Jan 2009, Keith Seyffarth wrote: I also tried adding AllowEmptyInput off in xorg.conf, but that gives an error when starting X that AllowEmptyInput is not valid. In section ServerLayout, add Option AllowEmptyInput Off An alternative is to leave your hal/moused/xorg.conf alone and add Option AutoAddDevices Off to ServerLayout. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: issues with X not loading
I also tried adding AllowEmptyInput off in xorg.conf, but that gives an error when starting X that AllowEmptyInput is not valid. In section ServerLayout, add Option AllowEmptyInput Off Thakns. This worked. I had the syntax incorrect. however, I thought this wasn't supposed to be necessar after the updates to hal on the 27th? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
xorg input ignored until mouse is moved (was Re: issues with X not loading)
On Sat, 31 Jan 2009, Keith Seyffarth wrote: I also tried adding AllowEmptyInput off in xorg.conf, but that gives an error when starting X that AllowEmptyInput is not valid. In section ServerLayout, add Option AllowEmptyInput Off Thakns. This worked. I had the syntax incorrect. however, I thought this wasn't supposed to be necessar after the updates to hal on the 27th? I hadn't tested it since then, but did just now. Removing keyboard and mouse entries and AllowEmptyInput and AutoAddDevices entries in ServerLayout did work... for a few seconds. Then it went back to keyboard input or mouse clicks ignored until the mouse is moved. That includes ctrl-alt-backspace. This is with hal-0.5.11_14 and moused enabled, tested on two different systems. Both have a USB and PS/2 mouse. So I'm sticking with explicitly declaring keyboard and mouse and AutoAddDevices Off for now. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: xorg input ignored until mouse is moved (was Re: issues with X not loading)
On Sat, 31 Jan 2009, Warren Block wrote: So I'm sticking with explicitly declaring keyboard and mouse and AutoAddDevices Off for now. Interestingly, the InputDevice mouse and keyboard entries and the corresponding entries in ServerLayout are unnecessary. Just Options AutoAddDevices Off in ServerLayout. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
issues with X not loading
On freebsd 6.0, I started having issues with X on Friday, and by Sunday, clicking buttons on the XFCE toolbar or choosing menu items from the XFCE menu weren't working. Subsequent to this, X would just hang when I run startx. I think what may have started this was trying to portupgrade gnucash, because it looks like some port items that were dependencies for other things (xorg-protos, for example) have been removed from the ports system. so, I tried portupgrade for xfce4, which tells me everything is current. Then I tried portupgrade xorg, which did upgrade a lot of things. This got me to a point where I can run startx, and rather than hanging, it, um, crashes gracefully. I receive this error: (==) Using config file: /etc/X11/xorg.conf Parse error on line 75 of section Files in file /etc/X11/xorg.conf RgbPath is not a valid keyword in this section. (EE) Problem parsing the config file (EE) Error parsing the config file Fatal server error: no screens found giving up. I can comment out line 75 referred to above, but that seems to put me back to where I was before trying to upgrade: startx hangs the computer... Does anyone have any suggestions? Thanks, Keith S. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: issues with X not loading
Le Wed, 28 Jan 2009 14:29:06 -0700 (MST), Keith Seyffarth w...@weif.net a écrit : (==) Using config file: /etc/X11/xorg.conf Parse error on line 75 of section Files in file /etc/X11/xorg.conf RgbPath is not a valid keyword in this section. (EE) Problem parsing the config file (EE) Error parsing the config file Does anyone have any suggestions? Yes, please see /usr/ports/UPDATING, Xorg was updated. Regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: issues with X not loading
On Wed, 2009-01-28 at 14:29 -0700, Keith Seyffarth wrote: On freebsd 6.0, I started having issues with X on Friday, and by Sunday, clicking buttons on the XFCE toolbar or choosing menu items from the XFCE menu weren't working. Subsequent to this, X would just hang when I run startx. I think what may have started this was trying to portupgrade gnucash, because it looks like some port items that were dependencies for other things (xorg-protos, for example) have been removed from the ports system. so, I tried portupgrade for xfce4, which tells me everything is current. Then I tried portupgrade xorg, which did upgrade a lot of things. This got me to a point where I can run startx, and rather than hanging, it, um, crashes gracefully. I receive this error: (==) Using config file: /etc/X11/xorg.conf Parse error on line 75 of section Files in file /etc/X11/xorg.conf RgbPath is not a valid keyword in this section. (EE) Problem parsing the config file (EE) Error parsing the config file Fatal server error: no screens found giving up. I can comment out line 75 referred to above, but that seems to put me back to where I was before trying to upgrade: startx hangs the computer... Does anyone have any suggestions? Check the libxcb thread on this list. Try running portupgrade -a -rf libxcb and wait patiently- it worked for me. Meanwhile, leave rgbpath uncommented if you have X ttys enabled or it'll annoy the shit out of you- comment it out as soon as portupgrade finishes and you'll have beloved X back :) If mouse doesn't work at this point you'll have to make sure dbus and hald are enabled under rc.conf and reboot. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
