[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Problems after xorg patch to 5.0_STABLE
On Oct 1, 2009, at 5:28 AM, Geert Hendrickx wrote:
On Mon, Sep 21, 2009 at 06:08:43PM -0400, Steven Bellovin wrote:
On Sep 21, 2009, at 5:50 PM, Jukka Salmi wrote:
Rafal Boni --> port-i386 (2009-09-21 17:22:13 -0400):
On Mon, Sep 21, 2009 at 12:44:35PM -0700, Soren Jacobsen wrote:
On Sep 21, 2009, at 12:14 PM, Jukka Salmi wrote:
However, I removed the directory in question and extracted the
again, but the screen still goes black as soon as Xorg is
Sadly, this is expected. See PR xsrc/41870. I am very tempted to
change our X server back to the old behavior of installing a
cursor immediately and painting the background to that horrible
horrible eye-killing pattern. Much as I hate that default
black with no cursor is all kinds of wrong.
Yeah, too many people's reaction to the black screeen w/no cursor
been "OMG, it's fuxored" (including mine, even now
should go back to the damn grey stipled screen; it's not like it
be changed by whatever eye-candy is running on top of X as soon
I don't think that was the problem I was seeing. Unless a side
is that you're not able to shut down the X server anymore... ;-)
With the 1.6.3 server, Ctrl+Alt+Backspace did not work, only
SIGKILL to the server (by a user logged in over the network)
left the screen garbled until the system was restarted. And blindly
typing `shutdown -r now' or pressing the power button to trigger a
shutdown by powerd(8) did not work as well.
In the meantime I've extracted the old sets to make Xorg (server
is usable again...
There's a problem I'm having with -current; I wonder if it's related
to the "can't exit" part of this.
For some reason, when I fire up recent versions of X, it doesn't
seem to know the names of any keys. This means that assorted
keyboard accelerators in my window manager (pkgsrc/wm/fvwm) don't
work. xmodmap seems to fail to destroy any concept of the caps lock
key's existence, I believe because I can't name it. If, though, I
run xmodmap manually and do an fvwm Restart, all is happy at that
No, I don't know why. I'm getting ready to send-pr on this and a
few other issues...
does the problem go away for you if you:
ln -s /usr/X11R7/lib/X11/xkb /var/db/xkb
I'll give that a try, though it may not happen for a day or two -- due
to other stability issues, I'm not carrying my NetBSD laptop these days.
This is apparantly the default path for xkbcomp in the newer xorg-
I think we should explicitly set XKM_OUTPUT_DIR to the old path
Geert Hendrickx -=- ghen%telenet.be@localhost -=- PGP: 0xC4BB9E9F
This e-mail was composed using 100% recycled spam messages!
--Steve Bellovin, http://www.cs.columbia.edu/~smb
Main Index |
Thread Index |