#644636 xorg: xserver randomly crashes without any clear indication

Package:
xorg
Source:
xorg
Description:
X.Org X Window System
Submitter:
Florian Boelstler
Date:
2019-12-12 21:57:03 UTC
Severity:
important
#644636#5
Date:
2011-10-07 16:57:13 UTC
From:
To:
#644636#10
Date:
2011-10-07 17:39:24 UTC
From:
To:
On Fri, Oct  7, 2011 at 18:57:13 +0200, Florian Boelstler wrote:

There seems to be 0 content in your mail other than the logs added by
reportbug.  You'll have to do better.

Cheers,
Julien
#644636#15
Date:
2011-10-07 17:58:04 UTC
From:
To:
Am 07.10.2011 19:39, schrieb Julien Cristau:
I did enter some information on the first "screen" presented by
reportbug. Unfortunately it got lost for a reason I don't know.

Anyway there is not much to report from my side besides the information
given in subject line and the backtrace I _manually_added_ using
reportbug. Obviously that part is not sufficient.

My environment:
wdm 1.28-3
wmii 3.6+debian-8

Crash occurs once a week while I use this system for about 3 hours a day.
#644636#20
Date:
2011-10-07 18:43:26 UTC
From:
To:
OK, I missed this one the first time.  I don't think that's a bug in X,
something on your system is sending us SIGQUIT when they shouldn't.

Cheers,
Julien
#644636#25
Date:
2011-10-21 21:43:47 UTC
From:
To:
Am 07.10.2011 20:43, schrieb Julien Cristau:

Is there anything I can do to trap that obscure piece of software
sending SIGQUIT?
#644636#30
Date:
2011-10-26 21:47:25 UTC
From:
To:
IIRC the times I've seen this it was plymouth or something stealing the
console out from under X.  Maybe check for things opening
/dev/tty[0-9]*.

Cheers,
Julien
#644636#37
Date:
2011-11-22 21:23:41 UTC
From:
To:
Am 26.10.2011 23:47, schrieb Julien Cristau:

I don't have plymouth installed.

In the meanwhile I'm pretty sure it's caused by icedove. It happens
mostly while entering a password for some mail account.

Are there any known issues for wdm / wmii and X?

Thanks for any idea.

Cheers,

  Florian
#644636#42
Date:
2011-12-24 12:37:54 UTC
From:
To:
Just coincidentally stumbled over .xsession-errors.
Shortly after the session start at 12:55 the xserver was restarted.

Is this output below of any help? Or just a consequence?

Thanks.


Xsession: X session started for flo at Sat Dec 24 12:55:57 CET 2011

XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server
":0.0" after 2064 requests (2064 known processed) with 0 events remaining.
wmiir: fatal: cannot read file/directory '/event': broken pipe: Broken pipe

XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server
":0.0" after 9 requests (6 known processed) with 0 events remaining.
wmiir: fatal: can't mount: Connection refused



Xsession: X session started for flo at Sat Dec 24 12:57:27 CET 2011

Has notifications support True
Loading...
Connecting to daemon...
Connected.
refreshing...
#644636#47
Date:
2012-10-03 15:20:29 UTC
From:
To:
The issue still occurs.
Maybe this piece of kernel log is pointing to something more useful:
plugin-containe[3683]: segfault at b2d025e4 ip b664a4e6 sp b2389034
error 6 in libpthread-2.11.3.so[b6640000+15000]

It's always printed if the problem occurs.

Cheers

  Florian
#644636#52
Date:
2012-11-22 22:23:42 UTC
From:
To:
I recently switched from wmii to i3 for managing my windows.
This didn't cure the problem.

Switching from wdm to xdm seems to resolve the problem.
It's just a day of testing so far, though looks pretty promising.

I'll report back in a few days...

Cheers,

  Florian
#644636#57
Date:
2012-11-29 21:06:26 UTC
From:
To:
It seems like my bug is related. At least, it is just as random as that
of the original poster.

Stdout messages when launched from startx
-------------------------------
X.Org X Server 1.12.4
Release Date: 2012-08-27
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.32-5-686-bigmem i686 Debian
Current Operating System: Linux lowry-nb 3.2.0-4-686-pae #1 SMP Debian 3.2.32-1 i686
Kernel command line: BOOT_IMAGE=/vmlinuz-3.2.0-4-686-pae root=/dev/mapper/lowry--nb-root ro quiet pcie_aspm=force
Build Date: 05 November 2012  10:28:15AM
xorg-server 2:1.12.4-3 (Julien Cristau <jcristau@debian.org>)
Current version of pixman: 0.26.0
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Nov 29 20:06:05 2012
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(II) [KMS] Kernel modesetting enabled.

Backtrace:
0: /usr/bin/X (xorg_backtrace+0x49) [0xb776c6d9]
1: /usr/bin/X (0xb75ef000+0x1810f6) [0xb77700f6]
2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb75d040c]
3: /usr/bin/X (AttendClient+0x1c) [0xb776e40c]
4: /usr/lib/xorg/modules/extensions/libdri2.so (DRI2SwapComplete+0x1e2) [0xb710e632]
5: /usr/lib/xorg/modules/drivers/radeon_drv.so (0xb6f65000+0xcaf9c) [0xb702ff9c]
6: /usr/lib/xorg/modules/extensions/libdri2.so (DRI2SwapBuffers+0x19c) [0xb710e8cc]
7: /usr/lib/xorg/modules/extensions/libdri2.so (0xb710c000+0x3f2c) [0xb710ff2c]
8: /usr/bin/X (0xb75ef000+0x3c375) [0xb762b375]
9: /usr/bin/X (0xb75ef000+0x29e95) [0xb7618e95]
10: /lib/i386-linux-gnu/i686/cmov/libc.so.6 (__libc_start_main+0xe6) [0xb727de46]
11: /usr/bin/X (0xb75ef000+0x2a1e9) [0xb76191e9]

Segmentation fault at address (nil)

Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting


Please consult the The X.Org Foundation support
	 at http://wiki.x.org
 for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.

Server terminated with error (1). Closing log file.
xinit: connection to X server lost

waiting for X server to shut down
------------------------
#644636#62
Date:
2014-01-21 22:56:44 UTC
From:
To:
Hi!
Do you still encounter this bug with latest versions? If yes, please
provide up-to-date data, and if not, this bug report might be closed, so
let us know :)
Cheers,

 Solveig
#644636#65
Date:
2014-01-21 22:56:44 UTC
From:
To:
Hi!
Do you still encounter this bug with latest versions? If yes, please
provide up-to-date data, and if not, this bug report might be closed, so
let us know :)
Cheers,

 Solveig
#644636#70
Date:
2014-01-31 21:25:08 UTC
From:
To:
Hi,

I can't speak for the issue raised by Alexander.
Though the original issue I've reported is gone after having moved away
from wdm. Still happily using xdm :)

Cheers

  Florian
#644636#75
Date:
2019-12-12 21:03:53 UTC
From:
To:
#644636#80
Date:
2019-12-12 21:23:47 UTC
From:
To:
i forgot to write:

when i woke up laptop, entered password, {i do not remember, whether i
entered login (username) that time}, and i had come into new desktop
session, instead of saved (suspended) session.

then many these messages were appearing in syslog:

Dec 12 20:51:57 localhost at-spi2-registr[16774]: Could not open X display
Dec 12 20:51:57 localhost at-spi-bus-launcher[1051]:
dbus-daemon[1062]: Successfully activated service
'org.a11y.atspi.Registry'
Dec 12 20:51:57 localhost at-spi-bus-launcher[1051]: SpiRegistry
daemon is running with well-known name - org.a11y.atspi.Registry
Dec 12 20:51:57 localhost at-spi2-registr[16774]: AT-SPI: Cannot open
default display
Dec 12 20:51:57 localhost at-spi-bus-launcher[1051]:
dbus-daemon[1062]: Activating service name='org.a11y.atspi.Registry'
requested by ':1.39' (uid=1000 pid=16772 comm="xfce4-session ")

then i restarted machine, to stop them...
#644636#85
Date:
2019-12-12 21:54:27 UTC
From:
To:
as/like said in the stackeoverflow link, there is no "core dump" log
in syslog, though i had systemd-coredump installed.