xorg crush on keyboard event

Bug #397461 reported by Oleksij Rempel
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
X.Org X server
Fix Released
Medium
xorg-server (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: xserver-xorg-core

Xorg crush on keyboard event. Mos of the time it is easy to reproduce:
1. boot ubuntu karmic and login
2. open some think. for example gedit and tipe some thing random ( it think it's depends some how on key "enter")
3. x crashes

Seems like Bug #327197 describe same issue on dual screen... i have this issue on different configurations: laptop (karmic 32bit) with attached second screen and on PC (karmic 64bit) with one screen.

lsb_release -rd
Description: Ubuntu karmic (development branch)
Release: 9.10

=======on PC==========
apt-cache policy xserver-xorg-core
xserver-xorg-core:
  Installiert: 2:1.6.2~git20090708+server-1.6-branch.6f1aff5a-0ubuntu0sarvatt
  Kandidat: 2:1.6.2~git20090708+server-1.6-branch.6f1aff5a-0ubuntu0sarvatt
  Versions-Tabelle:
 *** 2:1.6.2~git20090708+server-1.6-branch.6f1aff5a-0ubuntu0sarvatt 0
        500 http://ppa.launchpad.net karmic/main Packages
        100 /var/lib/dpkg/status
     2:1.6.1.901-2ubuntu2 0
        500 http://de.archive.ubuntu.com karmic/main Packages
========================

======on Laptop=============
apt-cache policy xserver-xorg-core
xserver-xorg-core:
  Installiert: 2:1.6.1.901-2ubuntu2
  Kandidat: 2:1.6.1.901-2ubuntu2
  Versions-Tabelle:
 *** 2:1.6.1.901-2ubuntu2 0
        500 http://de.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status
===============================

==========bucktrace=====================
gdb backtrace full
#0 0x00007f75a52848e3 in __select_nocancel () from /lib/libc.so.6
No symbol table info available.
#1 0x00000000004ed94a in WaitForSomething (
    pClientsReady=<value optimized out>) at ../../os/WaitFor.c:228
        i = <value optimized out>
        waittime = {tv_sec = 0, tv_usec = 292082}
        wt = 0x7fffea308f10
        timeout = <value optimized out>
        clientsReadable = {fds_bits = {0 <repeats 16 times>}}
        clientsWritable = {fds_bits = {61872864, 5623539, 140737122438968, 1,
            61515552, 20973628, 0, 32, 61895968, 32, 81087824, 5202188, 48,
            5184701, 32, 0}}
        curclient = <value optimized out>
        selecterr = 4
        nready = <value optimized out>
        devicesReadable = {fds_bits = {0, 61201552, 1, 29, 5, 61418512,
            61209168, 5656299, 0, 61872864, 59828176, 61418512, 61404240, 29,
            0, 61201552}}
        now = <value optimized out>
        someReady = 0
#2 0x000000000044dab2 in Dispatch () at ../../dix/dispatch.c:367
        result = <value optimized out>
        client = 0x3aaa720
        nready = <value optimized out>
        start_tick = 860
#3 0x0000000000433f05 in main (argc=<value optimized out>,
    argv=0x7fffea309148, envp=<value optimized out>) at ../../dix/main.c:397
        i = 1
        alwaysCheckForInput = {0, 1}
(gdb) q
The program is running. Quit anyway (and detach it)? (y or n) LND: Sending signal 3 to Thread 0x7f75a731f6f0 (LWP 3403)
Detaching from program: /usr/bin/Xorg, process 3403
=================================================

Revision history for this message
In , Oleksij Rempel (olerem) wrote :

Created an attachment (id=27527)
Xorg.0.log

Revision history for this message
In , Oleksij Rempel (olerem) wrote :
Revision history for this message
In , Oleksij Rempel (olerem) wrote :

I use config less xorg so there is no xorg.conf to provide.

Revision history for this message
Oleksij Rempel (olerem) wrote :

Binary package hint: xserver-xorg-core

Xorg crush on keyboard event. Mos of the time it is easy to reproduce:
1. boot ubuntu karmic and login
2. open some think. for example gedit and tipe some thing random ( it think it's depends some how on key "enter")
3. x crashes

Seems like Bug #327197 describe same issue on dual screen... i have this issue on different configurations: laptop (karmic 32bit) with attached second screen and on PC (karmic 64bit) with one screen.

lsb_release -rd
Description: Ubuntu karmic (development branch)
Release: 9.10

=======on PC==========
apt-cache policy xserver-xorg-core
xserver-xorg-core:
  Installiert: 2:1.6.2~git20090708+server-1.6-branch.6f1aff5a-0ubuntu0sarvatt
  Kandidat: 2:1.6.2~git20090708+server-1.6-branch.6f1aff5a-0ubuntu0sarvatt
  Versions-Tabelle:
 *** 2:1.6.2~git20090708+server-1.6-branch.6f1aff5a-0ubuntu0sarvatt 0
        500 http://ppa.launchpad.net karmic/main Packages
        100 /var/lib/dpkg/status
     2:1.6.1.901-2ubuntu2 0
        500 http://de.archive.ubuntu.com karmic/main Packages
========================

======on Laptop=============
apt-cache policy xserver-xorg-core
xserver-xorg-core:
  Installiert: 2:1.6.1.901-2ubuntu2
  Kandidat: 2:1.6.1.901-2ubuntu2
  Versions-Tabelle:
 *** 2:1.6.1.901-2ubuntu2 0
        500 http://de.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status
===============================

==========bucktrace=====================
gdb backtrace full
#0 0x00007f75a52848e3 in __select_nocancel () from /lib/libc.so.6
No symbol table info available.
#1 0x00000000004ed94a in WaitForSomething (
    pClientsReady=<value optimized out>) at ../../os/WaitFor.c:228
        i = <value optimized out>
        waittime = {tv_sec = 0, tv_usec = 292082}
        wt = 0x7fffea308f10
        timeout = <value optimized out>
        clientsReadable = {fds_bits = {0 <repeats 16 times>}}
        clientsWritable = {fds_bits = {61872864, 5623539, 140737122438968, 1,
            61515552, 20973628, 0, 32, 61895968, 32, 81087824, 5202188, 48,
            5184701, 32, 0}}
        curclient = <value optimized out>
        selecterr = 4
        nready = <value optimized out>
        devicesReadable = {fds_bits = {0, 61201552, 1, 29, 5, 61418512,
            61209168, 5656299, 0, 61872864, 59828176, 61418512, 61404240, 29,
            0, 61201552}}
        now = <value optimized out>
        someReady = 0
#2 0x000000000044dab2 in Dispatch () at ../../dix/dispatch.c:367
        result = <value optimized out>
        client = 0x3aaa720
        nready = <value optimized out>
        start_tick = 860
#3 0x0000000000433f05 in main (argc=<value optimized out>,
    argv=0x7fffea309148, envp=<value optimized out>) at ../../dix/main.c:397
        i = 1
        alwaysCheckForInput = {0, 1}
(gdb) q
The program is running. Quit anyway (and detach it)? (y or n) LND: Sending signal 3 to Thread 0x7f75a731f6f0 (LWP 3403)
Detaching from program: /usr/bin/Xorg, process 3403
=================================================

Revision history for this message
Oleksij Rempel (olerem) wrote :
Revision history for this message
Oleksij Rempel (olerem) wrote :
Revision history for this message
Oleksij Rempel (olerem) wrote :

I use config less xorg so there is no xorg.conf to provide.

Changed in xorg-server:
status: Unknown → Confirmed
Revision history for this message
In , Peter Hutterer (peter-hutterer) wrote :

Please provide a log with the backtrace from a crash included. If your server restarts after the crash, this log is usually /var/log/Xorg.0.log.old (note the .old ending)

Revision history for this message
Tobias Wolf (towolf) wrote :

I also have this issue. I got Xorg and my drivers from Xorg edgers PPA. Do you also use this unstable source? I don't use dual screen, only a simple Thinkpad with Intel graphics. At first I thought it would only trigger on special characters like apostrophe and pressing Enter later. It's really funny. And annoying. Trying to not press Enter all the time ... O_ô

Revision history for this message
In , Oleksij Rempel (olerem) wrote :

Xorg.log was applied at first time... but there is no crash trace at all.
Probably you can close it.. wit latest karmic update i can't reproduce this issue.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

upstream asked for your input, please follow up there.

Changed in xorg-server (Ubuntu):
status: New → Incomplete
Oleksij Rempel (olerem)
Changed in xorg-server (Ubuntu):
status: Incomplete → Fix Released
Changed in xorg-server:
status: Confirmed → Fix Released
Changed in xorg-server:
importance: Unknown → Medium
Changed in xorg-server:
importance: Medium → Unknown
Changed in xorg-server:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.