Activity log for bug #270790

Date Who What changed Old value New value Message
2008-09-16 07:28:46 DannyKing bug added bug
2008-09-30 06:11:13 lukyluke bug added attachment 'Xorg.log.txt.gz' (Xorg.log.txt.gz)
2008-10-01 15:13:25 Brian Murray None: bugtargetdisplayname Ubuntu xorg (Ubuntu)
2008-10-01 15:13:25 Brian Murray None: bugtargetname ubuntu xorg (Ubuntu)
2008-10-01 15:13:25 Brian Murray None: statusexplanation
2008-10-01 15:13:25 Brian Murray None: title Bug #270790 in Ubuntu: "System bell (I think) crashes X" Bug #270790 in xorg (Ubuntu): "System bell (I think) crashes X"
2008-12-05 21:48:57 Bryce Harrington description All of a sudden, after working fine all day (and in fact, all month) my install of Hardy has an odd bug concerning what I think must be the system bell: Whenever I press tab in a terminal (I have tried in gnome-terminal and xterm) my X server restarts! It also restarts if I press delete and there is no text left to delete in the terminal. The only thing that happens in both those situations is the beep, so I disabled the bell in /etc/inputrc and that has stopped the crashing. I don't know what suddenly caused this issue, but it was working perfectly and then suddenly started to have this problem. A bug fix would be great because this is pretty serious but if someone could offer a short term fix I would appreciate it too. Thanks All of a sudden, after working fine all day (and in fact, all month) my install of Hardy has an odd bug concerning what I think must be the system bell: Whenever I press tab in a terminal (I have tried in gnome-terminal and xterm) my X server restarts! It also restarts if I press delete and there is no text left to delete in the terminal. The only thing that happens in both those situations is the beep, so I disabled the bell in /etc/inputrc and that has stopped the crashing. I don't know what suddenly caused this issue, but it was working perfectly and then suddenly started to have this problem. A bug fix would be great because this is pretty serious but if someone could offer a short term fix I would appreciate it too. Thanks Backtrace: 0: /usr/bin/X(xf86SigHandler+0x7e) [0x80c780e] 1: [0xb7fb2420] 2: /usr/bin/X(ProcBell+0x13c) [0x808386c] 3: /usr/bin/X [0x815076e] 4: /usr/bin/X(Dispatch+0x2cf) [0x808d8df] 5: /usr/bin/X(main+0x48b) [0x807471b] 6: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7d3f450] 7: /usr/bin/X(FontFileCompleteXLFD+0x201) [0x8073a91] Fatal server error: Caught signal 11. Server aborting
2008-12-05 21:48:57 Bryce Harrington title System bell (I think) crashes X System bell crashes X in ProcBell
2008-12-05 22:04:09 Bryce Harrington xorg: status New Incomplete
2008-12-05 22:04:09 Bryce Harrington xorg: bugtargetdisplayname xorg (Ubuntu) xorg-server (Ubuntu)
2008-12-05 22:04:09 Bryce Harrington xorg: bugtargetname xorg (Ubuntu) xorg-server (Ubuntu)
2008-12-05 22:04:09 Bryce Harrington xorg: statusexplanation Please collect a full backtrace on this crash. See http://wiki.ubuntu.com/X/Backtracing for directions.
2008-12-05 22:04:09 Bryce Harrington xorg: title Bug #270790 in xorg (Ubuntu): "System bell crashes X in ProcBell" Bug #270790 in xorg-server (Ubuntu): "System bell crashes X in ProcBell"
2009-01-09 06:00:32 Bryce Harrington xorg-server: status Incomplete Invalid
2009-02-15 08:43:16 Salvatore Iovene xorg-server: status Invalid New
2009-02-15 08:43:16 Salvatore Iovene xorg-server: statusexplanation Please collect a full backtrace on this crash. See http://wiki.ubuntu.com/X/Backtracing for directions. I have to reopen this bug, because I can reproduce it. Ubuntu Intrepid, xserver-xorg 1:7.4~5ubuntu3, xserver-xorg-input-wacom 1:0.8.1.6-1ubuntu2. The backtrace is the same. xset -b doesn't help.
2009-02-21 10:26:11 Bryce Harrington xorg-server: status New Invalid
2009-02-21 10:26:11 Bryce Harrington xorg-server: statusexplanation I have to reopen this bug, because I can reproduce it. Ubuntu Intrepid, xserver-xorg 1:7.4~5ubuntu3, xserver-xorg-input-wacom 1:0.8.1.6-1ubuntu2. The backtrace is the same. xset -b doesn't help. If you want to reopen it, we still must have a backtrace. See http://wiki.ubuntu.com/X/Backtracing for directions.