Bug 27620

Summary: Xorg crashes after pressing Enter key
Product: xorg Reporter: wike <wike.svk>
Component: Server/GeneralAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED NOTOURBUG QA Contact: Xorg Project Team <xorg-team>
Severity: critical    
Priority: medium    
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
kdm.log and xorg.conf
none
kdm.log
none
xorg.conf
none
kdm.log
none
xorg.conf none

Description wike 2010-04-13 10:38:48 UTC
Created attachment 34969 [details]
kdm.log and xorg.conf

I'm running
Arch Linux with 2.6.33-ARCH kernel
xorg-server 1.7.6-3
Nvidia driver 195.36.15-2

After logging into KDE/Xfce4/Gnome session and typing some text, after pressing [Enter] key Xorg crashes.
I have found out the way how to reproduce this bug:
Start any program and type "(" character, press Enter.

/var/log/kdm.log:
Backtrace:
0: /usr/bin/X (xorg_backtrace+0x3b) [0x809f81b]
1: /usr/bin/X (0x8048000+0x54745) [0x809c745]
2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb76f740c]
3: /usr/bin/X (0x8048000+0x40170) [0x8088170]
4: /usr/bin/X (0x8048000+0x1a705) [0x8062705]
5: /lib/libc.so.6 (__libc_start_main+0xe6) [0xb72e6b86]
6: /usr/bin/X (0x8048000+0x1a2f1) [0x80622f1]

Fatal server error:
Caught signal 3 (Quit). Server aborting

This bug is reported on various places for at least Ubuntu, Debian and Arch distributions:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/526352
http://bugs.archlinux.org/task/17472
Comment 1 Julien Cristau 2010-04-13 10:53:46 UTC
please attach files as plain text.
Comment 2 wike 2010-04-13 10:59:04 UTC
Created attachment 34970 [details]
kdm.log
Comment 3 wike 2010-04-13 10:59:22 UTC
Created attachment 34971 [details]
xorg.conf
Comment 4 wike 2010-04-13 11:00:27 UTC
Created attachment 34972 [details]
kdm.log
Comment 5 wike 2010-04-13 11:01:10 UTC
Created attachment 34973 [details]
xorg.conf
Comment 6 wike 2010-04-13 11:53:39 UTC
I had found out that my problem was caused by update of VirtualBox I did today. When the VB startup script is being run on system startup the bug starts to have an effect. Without it, everything works just fine.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.