You are not logged in.
I just did a -Syu, and therefore am running the latest Kernel, xorg server and KDE. I use nvidia. X loads up, KDE come up, music plays... I push any button on keyboard and *poof*, crash. I cannot get the keyboard or X or a command line back. I either ssh into it and reboot, or hit the hardware reset button.
This is the Xorg.0.log tail end
<snip>
(==) Mouse0: Emulate3Buttons, Emulate3Timeout: 50
(**) Option "ZAxisMapping" "4 5 6 7"
(**) Mouse0: ZAxisMapping: buttons 4, 5, 6 and 7
(**) Mouse0: Buttons: 11
(**) Mouse0: Sensitivity: 1
(**) Option "CoreKeyboard"
(**) Keyboard0: always reports core events
(**) Option "Protocol" "standard"
(**) Keyboard0: Protocol: standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xorg"
(**) Keyboard0: XkbRules: "xorg"
(**) Option "XkbModel" "pc105"
(**) Keyboard0: XkbModel: "pc105"
(**) Option "XkbLayout" "us"
(**) Keyboard0: XkbLayout: "us"
(**) Option "CustomKeycodes" "off"
(**) Keyboard0: CustomKeycodes disabled
(II) evaluating device (Keyboard0)
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(II) evaluating device (Mouse0)
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
(--) Mouse0: PnP-detected protocol: "ExplorerPS/2"
(II) Mouse0: ps2EnableDataReporting: succeededBacktrace:
0: /usr/bin/X(xf86SigHandler+0x6a) [0x49b1da]
1: /lib/libc.so.6 [0x2ad04025d120]
2: /lib/libc.so.6(memcpy+0xd2) [0x2ad0402a3e02]
3: /usr/bin/X(XkbCopyKeymap+0x1712) [0x53cd12]
4: /usr/bin/X(SwitchCoreKeyboard+0x17b) [0x45ce0b]
5: /usr/bin/X(mieqProcessInputEvents+0x16d) [0x4d652d]
6: /usr/bin/X(ProcessInputEvents+0x1c) [0x49b97c]
7: /usr/bin/X(Dispatch+0x7d) [0x44d5ad]
8: /usr/bin/X(main+0x47d) [0x435fed]
9: /lib/libc.so.6(__libc_start_main+0xf4) [0x2ad04024a164]
10: /usr/bin/X(FontFileCompleteXLFD+0x281) [0x435329]Fatal server error:
Caught signal 11. Server aborting
I do not have this problem if I use xfce4. Using the mouse in KDE works fine... until I push a keyboard button.
Thanks for any help and guidance.
Last edited by johnr (2008-03-18 14:30:23)
Offline
In case someone is going to ask:
Kernel 2.6.24.3-3
xorg-server 1.4.0.90-8
nvidia 169.12-1
kde 3.5.9
Offline
Same here,
I'm using kdemod (3.5.9-2), and Ati Rage Mobile M4 with the latest ati driver (6.8.0-2).
The relevant ouptut from startx:
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20
Minor opcode: 0
Resource id: 0x1c0008f
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20
Minor opcode: 0
Resource id: 0x1c0008f
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20
Minor opcode: 0
Resource id: 0x1c0008f
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x7e) [0x80e053e]
1: [0xb7fbb420]
2: /usr/bin/X(SwitchCoreKeyboard+0x17c) [0x809c9cc]
3: /usr/bin/X(mieqProcessInputEvents+0x17c) [0x811bdcc]
4: /usr/bin/X(ProcessInputEvents+0x2c) [0x80e0dbc]
5: /usr/bin/X(Dispatch+0x72) [0x808c6b2]
6: /usr/bin/X(main+0x48b) [0x8073e3b]
7: /lib/libc.so.6(__libc_start_main+0xe6) [0xb7d7d396]
8: /usr/bin/X(FontFileCompleteXLFD+0x205) [0x80731b1]
Fatal server error:
Caught signal 11. Server aborting
kmix: Fatal IO error: client killed
kdeinit: Fatal IO error: client killed
kdeinit: sending SIGHUP to children.
kwin: Fatal IO error: client killed
ksmserver: Fatal IO error: client killed
*** kdesktop got signal 1 (Exiting)
kicker: sighandler called
ICE default IO error handler doing an exit(), pid = 4823, errno = 11
xinit: connection to X server lost.
klauncher: Exiting on signal 1
klauncher: Fatal IO error: client killed
Aufgelegt
GOT SIGHUP
ICE default IO error handler doing an exit(), pid = 4857, errno = 11
kdeinit: sending SIGTERM to children.
kdeinit: Exit.
kded: Fatal IO error: client killed
kicker: sighandler called
DCOPClient::attachInternal. Attach failed Could not open network socket
DCOPClient::attachInternal. Attach failed Could not open network socket
ERROR: Couldn't attach to DCOP server!
startkde: Shutting down...
Warning: connect() failed: : No such file or directory
Error: Can't contact kdeinit!
startkde: Running shutdown scripts...
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 4783 killed;
xprop: unable to open display ':0'
usage: xprop [-options ...] [[format [dformat]] atom] ...
where options include:
-grammar print out full grammar for command line
-display host:dpy the X server to contact
-id id resource id of window to examine
-name name name of window to examine
-font name name of font to examine
-remove propname remove a property
-set propname value set a property to a given value
-root examine the root window
-len n display at most n bytes of any property
-notype do not display the type field
-fs filename where to look for formats for properties
-frame don't ignore window manager frames
-f propname format [dformat] formats to use for property of given name
-spy examine window properties forever
startkde: Done./var/log/messages does only say this
X[4822]: segfault at 6b636f48 eip b7d9eb05 esp bfd6ac00 error 4Greetings Maurice
Offline
You can temparily solve this segfault, if you deactivate keyboardlayouts in kde controlcenter (in regional settings).
Offline
Moe, Thanks for the reply, sounds like you got sorted. I tried that and did not have any success.
EDIT: actually, I think it did, but I had to do a complete reboot (after initial crash) for it to work. seems to have worked thanks for the tip.
Last edited by johnr (2008-03-18 14:29:23)
Offline
I noticed that I had problems with X segfaulting after upgrading to xorg-server 1.4.0.90-8. After completely rebuilding the system I was having the same problem. moe's suggestion worked, however X was still segfaulting. I reverted back to xorg-server 1.4.0.90-6 and things seem to be fine. I'm wondering if there's a problem with the 90-8 build. I don't know if this helps anyone or not, but just thought I would mention it.
Offline