Caught signal 11 (Segmentation fault). Server aborting

[nierce]

Binary package hint: xorg

It randomly happens in gnome ubuntu maverick, suddenly I am logged out and login screen (gdm) appears. I am pretty sure each time it happens I just press Enter or some combinations with it.

These should be the bad point:
Xorg.0.log:

Backtrace:
[ 12371.402] 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80ef31b]
[ 12371.402] 1: /usr/bin/X (0x8048000+0x5d00d) [0x80a500d]
[ 12371.402] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0x50740c]
[ 12371.402] 3: /usr/bin/X (FreeClientResources+0xed) [0x80655ad]
[ 12371.402] 4: /usr/bin/X (FreeAllResources+0x60) [0x8065680]
[ 12371.402] 5: /usr/bin/X (0x8048000+0x1a606) [0x8062606]
[ 12371.402] 6: /lib/libc.so.6 (__libc_start_main+0xe7) [0x126ce7]
[ 12371.402] 7: /usr/bin/X (0x8048000+0x1a1b1) [0x80621b1]
[ 12371.402] Segmentation fault at address (nil)
[ 12371.402]
Caught signal 11 (Segmentation fault). Server aborting

This is big annoying bug

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xorg 1:7.5+6ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-28.49-generic 2.6.35.11
Uname: Linux 2.6.35-28-generic i686
Architecture: i386
DRM.card0.LVDS.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1024x768
 edid-base64: AP///////wAwrkBAAAAAAAAPAQOAHhd46nSwlldUiyglUFQhCAABAQEBAQEBAQEBAQEBAQEBZBkAQEEAJjAYiDYAMOQQAAAYKBUAQEEAJjAYiDYAMOQQAAAYAAAADwBhQzJhQygPAQAyDFETAAAA/gBMUDE1MFgwOC1UTEE4AD8=
DRM.card0.VGA.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1280x1024 1280x1024 1280x960 1280x800 1280x800 1152x864 1152x864 1152x720 1024x768 1024x768 832x624 800x600 800x600 640x480 640x480 720x400
 edid-base64: AP///////wAJ0QF6RVQAAAcSAQMOJh54LswVpVdJmyUSUFSla4BxAHFAgUCBgIEAgQ8BAQEBMCoAmFEAKkAwcBMAeC0RAAAeAAAA/wBUMjgxMTYwOFNMMEwwAAAA/QA3TB9TDgAKICAgICAgAAAA/ABCZW5RIFg5MDAKCgoKAD0=
Date: Wed Mar 23 09:07:15 2011
GdmLog: X: /tmp/.X11-unix has suspicious mode (not 1777) or is not a directory, aborting.
GdmLog1: X: /tmp/.X11-unix has suspicious mode (not 1777) or is not a directory, aborting.
MachineType: LENOVO 9455W42
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-28-generic root=UUID=6981baab-6717-4b2d-9b46-88474fd88a03 ro
ProcEnviron:
 LANGUAGE=cs_CZ:cs:en_GB:en
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
dmi.bios.date: 01/09/2007
dmi.bios.vendor: LENOVO
dmi.bios.version: 7CETC1WW (2.11 )
dmi.board.name: 9455W42
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr7CETC1WW(2.11):bd01/09/2007:svnLENOVO:pn9455W42:pvrThinkPadR60:rvnLENOVO:rn9455W42:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 9455W42
dmi.product.version: ThinkPad R60
dmi.sys.vendor: LENOVO
system:
 distro: Ubuntu
 codename: maverick
 architecture: i686
 kernel: 2.6.35-28-generic
xkbcomp:
 Error: command ['xkbcomp', ':0', '-w0', '-'] failed with exit code 1: Error: Cannot open display ":0"
                   Exiting

[Ian (gibbathehutt)]

This seems to be happening to me of late. Symptoms as previous poster. Get a seg fault in /var/log/Xorg.0.log.old

Backtrace:
[ 7808.923] 0: /usr/bin/X (xorg_backtrace+0x28) [0x45c5a8]
[ 7808.924] 1: /usr/bin/X (0x400000+0x5a87d) [0x45a87d]
[ 7808.924] 2: /lib/libpthread.so.0 (0x7f9f6a38a000+0xfb40) [0x7f9f6a399b40]
[ 7808.924] 3: /usr/lib/xorg/extra-modules/nvidia_drv.so (0x7f9f64d02000+0x3a3a7c) [0x7f9f650a5a7c]
[ 7808.924] 4: /usr/bin/X (FreeClientResources+0xef) [0x44adef]
[ 7808.924] 5: /usr/bin/X (CloseDownClient+0x5c) [0x43b2ac]
[ 7808.924] 6: /usr/bin/X (0x400000+0x3fa46) [0x43fa46]
[ 7808.924] 7: /usr/bin/X (0x400000+0x2187b) [0x42187b]
[ 7808.924] 8: /lib/libc.so.6 (__libc_start_main+0xfe) [0x7f9f692f5d8e]
[ 7808.924] 9: /usr/bin/X (0x400000+0x21409) [0x421409]
[ 7808.924] Segmentation fault at address (nil)
[ 7808.924]
Caught signal 11 (Segmentation fault). Server aborting
[ 7808.933]
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
[ 7808.933] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 7808.933]
[ 7809.000] (II) Power Button: Close
[ 7809.000] (II) UnloadModule: "evdev"
[ 7809.080] (II) Power Button: Close
[ 7809.080] (II) UnloadModule: "evdev"
[ 7809.151] (II) Logitech USB Laser Mouse: Close
[ 7809.151] (II) UnloadModule: "evdev"
[ 7809.200] (II) Apple, Inc Apple Keyboard: Close
[ 7809.200] (II) UnloadModule: "evdev"
[ 7809.260] (II) Apple, Inc Apple Keyboard: Close
[ 7809.260] (II) UnloadModule: "evdev"
[ 7809.340] (II) zc3xx: Close
[ 7809.340] (II) UnloadModule: "evdev"
[ 7809.723] ddxSigGiveUp: Closing log

[Ian (gibbathehutt)]

If you need any files, let me know and I'll do a dump and attach them.

[dazza5000 (darran-kelinske)]

getting this too - will add additional files

[ 36.899] 9: /usr/bin/X (mieqProcessInputEvents+0x199) [0x459c39]
[ 36.899] 10: /usr/bin/X (ProcessInputEvents+0x9) [0x46d9e9]
[ 36.899] 11: /usr/bin/X (0x400000+0x40f23) [0x440f23]
[ 36.899] 12: /usr/bin/X (0x400000+0x21a7e) [0x421a7e]
[ 36.899] 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xff) [0x7fae4ec29eff]
[ 36.899] 14: /usr/bin/X (0x400000+0x21629) [0x421629]
[ 36.899] Segmentation fault at address (nil)
[ 36.899]
Caught signal 11 (Segmentation fault). Server aborting
[ 36.899]
Please consult the The X.Org Foundation support
  at http://wiki.x.org
 for help.
[ 36.899] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 36.899]
[ 36.910] (II) Power Button: Close
[ 36.910] (II) UnloadModule: "evdev"
[ 36.910] (II) Unloading evdev
[ 36.910] (II) Power Button: Close
[ 36.910] (II) UnloadModule: "evdev"
[ 36.910] (II) Unloading evdev

[dazza5000 (darran-kelinske)]

I'm getting this on 11.04

[bugbot (bugbot)]

Hey nierce,

Hi, have you had a chance to test if this bug is still present in natty?

If it does (and if you're the original reporter), please boot into natty
and run the command:

  apport-collect <bug-number>

which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run this right after reproducing the problem.)

[nierce (mbrunat)]

I don't have natty yet. Perhaps in this week.
This bug hasn't appear for longer time but this makes it even subtle.
I will update this bug if it will continue in natty.
Thanks for info

On 28.4.2011 06:17, bugbot wrote:
> Hey nierce,
>
>
> Hi, have you had a chance to test if this bug is still present in natty?
>
> If it does (and if you're the original reporter), please boot into natty
> and run the command:
>
> apport-collect<bug-number>
>
> which will update the bug with fresh logs and tag the bug as affecting
> natty. (It is best to run this right after reproducing the problem.)
>
>
> ** Changed in: xorg-server (Ubuntu)
> Status: New => Incomplete
>

[Victor Gonçalves (hotcyv)]

Architecture: i386
DistroCodename: natty
DistroRelease: Ubuntu 11.04
DistroVariant: ubuntu
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
Package: xorg-server (not installed)
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Tags: natty unity-2d ubuntu
Uname: Linux 2.6.38-8-generic i686
UnreportableReason: Please work this issue through technical support channels first.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[nagy.pite (nagy.pite)]

Backtrace:
[ 29851.244] 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80eab1b]
[ 29851.244] 1: /usr/bin/X (0x8048000+0x5fac8) [0x80a7ac8]
[ 29851.244] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0x69340c]
[ 29851.245] 3: /usr/bin/X (_CallCallbacks+0x3e) [0x8074e1e]
[ 29851.245] 4: /usr/bin/X (WriteToClient+0x267) [0x80a7607]
[ 29851.245] 5: /usr/lib/xorg/modules/extensions/libdri2.so (ProcDRI2WaitMSCReply+0x62) [0x135bf2]
[ 29851.245] 6: /usr/lib/xorg/modules/extensions/libdri2.so (DRI2WaitMSCComplete+0x75) [0x133fc5]
[ 29851.245] 7: /usr/lib/xorg/modules/drivers/intel_drv.so (0x50b000+0x226bc) [0x52d6bc]
[ 29851.245] 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0x50b000+0x87d2) [0x5137d2]
[ 29851.245] 9: /lib/i386-linux-gnu/libdrm.so.2 (drmHandleEvent+0xf5) [0x5d6665]
[ 29851.245] 10: /usr/lib/xorg/modules/drivers/intel_drv.so (0x50b000+0x7937) [0x512937]
[ 29851.245] 11: /usr/bin/X (WakeupHandler+0x52) [0x8074602]
[ 29851.245] 12: /usr/bin/X (WaitForSomething+0x1ba) [0x80a1f3a]
[ 29851.245] 13: /usr/bin/X (0x8048000+0x27f1e) [0x806ff1e]
[ 29851.245] 14: /usr/bin/X (0x8048000+0x1a81c) [0x806281c]
[ 29851.245] 15: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xe7) [0xd39e37]
[ 29851.245] 16: /usr/bin/X (0x8048000+0x1a411) [0x8062411]
[ 29851.245] Segmentation fault at address 0xb4e5f008
[ 29851.245]
Caught signal 11 (Segmentation fault). Server aborting

[nierce (mbrunat)]

It happens to me again today. Still on maverick. I found out that probably it happens only if acceleration (compiz) is on.
Attaching ubuntu-bug xorg

[Alex Lewis (alexlewis-deactivatedaccount)]

I've seen the exact same stack trace as the first comment in this bug report.

Dell Latitude D630.
Ubuntu 11.04
Classic Desktop (with effects)

I've attached the Xorg log file containing the error. Is there anything else you would like me to do?

I *think* the crash happens when Chrome is loading/refreshing Google Mail (specifically Google Apps Mail). This may just be a coincidence and only happens now and again.

[qwazi (chris-mckitterick)]

Same dealy here on Maverick 64-bit running with Compiz:

[ 50342.253] (II) XKB: reuse xkmfile /var/lib/xkb/server-81EC4871279DB1D73113D19E789F270C19322F52.xkm
[ 85236.715] (II) XKB: reuse xkmfile /var/lib/xkb/server-81EC4871279DB1D73113D19E789F270C19322F52.xkm
[102302.968]
Backtrace:
[102303.066] 0: /usr/bin/X (xorg_backtrace+0x28) [0x45c5a8]
[102303.066] 1: /usr/bin/X (0x400000+0x5a87d) [0x45a87d]
[102303.066] 2: /lib/libpthread.so.0 (0x7ff66114c000+0xfb40) [0x7ff66115bb40]
[102303.074] 3: /usr/lib/xorg/extra-modules/nvidia_drv.so (0x7ff65bac4000+0x3a3a7c) [0x7ff65be67a7c]
[102303.074] 4: /usr/bin/X (FreeClientResources+0xef) [0x44adef]
[102303.074] 5: /usr/bin/X (CloseDownClient+0x5c) [0x43b2ac]
[102303.074] 6: /usr/bin/X (0x400000+0x3fa46) [0x43fa46]
[102303.074] 7: /usr/bin/X (0x400000+0x2187b) [0x42187b]
[102303.074] 8: /lib/libc.so.6 (__libc_start_main+0xfe) [0x7ff6600b7d8e]
[102303.074] 9: /usr/bin/X (0x400000+0x21409) [0x421409]
[102303.075] Segmentation fault at address (nil)
[102303.075]
Caught signal 11 (Segmentation fault). Server aborting

[Michał Wróbel (maw)]

I was getting the same error as Ian, JPM ( #775705) and qwazi on my 64-bit Maverick with nVidia binary drivers (260.19.06). No compiz here, but extensively using VMware Player with 3D acceleration.

According to a hint by Paul de Vries (http://vimeo.com/groups/cinelerra/forumthread:236340), I have updated the nVidia drivers. I took 270.41.06 from ppa:ubuntu-x-swat/x-updates. I will report whether it stopped crashing.

[Michał Wróbel (maw)]

Unfortunately, my Xorg on the new nVidia drivers crashed, but this time on another account with compiz enabled and during non-3D work (just a terminal and a browser, no VMware). The backtrace was this time quite different.

[Michał Wróbel (maw)]

Please ignore my comment #14 for now, as this seems to be a completely different bug.

[William Haines (william-haines1)]

I don't believe this was fixed in natty. If anything, it is more widespread now. https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/778490.

[Michał Wróbel (maw)]

My 64-bit Maverick runs without a crash for 9 days now on 270.41.06 nVidia binary drivers.

[nierce (mbrunat)]

Today again. This time without compiz and two monitors.
Pidgin, Thunderbird, Chromium only was opened and again logout happened just after hit Enter in pidgin sending icq message.

Why is this bug still Incomplete? What else to attach?

I have tried this https://wiki.ubuntu.com/X/Backtracing but as I entered 'attach ###' in gdb ubuntu froze

Attaching results from ubuntu-bug xorg

[Bryce Harrington (bryce)]

It's incomplete because we still need someone to collect a full backtrace on this crash - see http://wiki.ubuntu.com/X/Backtracing for guidance.

Alternately, if you can specify steps to reproduce the crash I can try on my end (I haven't seen any crashes like this, and I hit Enter many times during the day). "Randomly" doesn't give much to go on.

[Spiderone (koliba23)]

I'm using xine-ui to connect to vdr(mpeg2,x264 videos) .This logout happens once from 5-10 times when closing xine fullscreen by remote control or keyboard. After logging in compiz is using 100% cpu.

GT9600 Driver Version: 270.41.19 on natty x64 . This also happened with older drivers I think.

Hope that helps.

[Launchpad Janitor (janitor)]

[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]

[Haneef Mubarak (haneefmubarak)]

Can confirm that the bug still exists. This is a problem for xorg in general, and therefore raises issues with both lightdm and unity. It may also affect gdm and kdm.

[Haneef Mubarak (haneefmubarak)]

If the bug still exists in oneiric and it is not fixed, realize that the bug will become more prevalent in precise since 12.04 will be a LTS release and many users will be upgrading.

[Ram Kanteti (yoramsk)]

sorry, i don't use ubuntu anymore
On Apr 22, 2012 5:38 PM, Haneef Mubarak <email address hidden> wrote:

> If the bug still exists in oneiric and it is not fixed, realize that the
> bug will become more prevalent in precise since 12.04 will be a LTS
> release and many users will be upgrading.

[Sebastien Bacher (seb128)]

Closing the lightdm, unity, etc component the issue affect those but it's not in their code. The bug seems to mix several issues, could you get a stacktrace and an Xorg.0.log from a config having the issue, on precise would be better. It might be best to open a new bug report that to keep a confusing one mixing issues from different users accross configs and releases though

[Haneef Mubarak (haneefmubarak)]

Gotcha. Will do. After doing that, should I mark this bug as a duplicate?

[Menno van Alz (menno-van-alz)]

I think I got some similar bug on Kubuntu 12.04.
It happens randomly.

I found this in /var/kdm.log

Backtrace:
0: /usr/bin/X (xorg_backtrace+0x37) [0xb7749627]
1: /usr/bin/X (0xb75c1000+0x18c3aa) [0xb774d3aa]
2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb759e40c]
3: /usr/lib/dri/fglrx_dri.so (0xb19e0000+0xae36c5) [0xb24c36c5]
Segmentation fault at address (nil)

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.

 ddxSigGiveUp: Closing log
Server terminated with error (1). Closing log file.

X.Org X Server 1.11.3
Release Date: 2011-12-16
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.42-26-generic i686 Ubuntu

There's also an entry in /var/syslog:
Aug 22 17:42:07 x86 kdm[1153]: X server for display :0 terminated unexpectedly

[Menno van Alz (menno-van-alz)]

I use Kubuntu 12.04 with fglrx driver.

[akaroot (mykolaakaroot)]

Its happens randomly with me too on 32bit Ubuntu 12.04 ThinkPad R500 with Intel 4500MHD video card

Xorg.0.log:
Backtrace:
0: /usr/bin/X (xorg_backtrace+0x37) [0xb76b8647]
1: /usr/bin/X (0xb7530000+0x18c3ca) [0xb76bc3ca]
2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb750d40c]
3: /usr/lib/i386-linux-gnu/libpciaccess.so.0 (pci_device_next+0x100) [0xb7453170]
4: /usr/lib/i386-linux-gnu/libpciaccess.so.0 (pci_device_find_by_slot+0x4b) [0xb745322b]
5: /usr/lib/i386-linux-gnu/libpciaccess.so.0 (pci_device_vgaarb_init+0xf0) [0xb7455780]
6: /usr/bin/X (0xb7530000+0x81474) [0xb75b1474]
7: /usr/bin/X (xf86BusConfig+0xc1) [0xb759fbf1]
8: /usr/bin/X (InitOutput+0x7ca) [0xb75acc2a]
9: /usr/bin/X (0xb7530000+0x251a0) [0xb75551a0]
10: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb71904d3]
11: /usr/bin/X (0xb7530000+0x25699) [0xb7555699]
 Segmentation fault at address (nil)
Caught signal 11 (Segmentation fault). Server aborting

[akaroot (mykolaakaroot)]

In my case this problem randomly appears on boot before greetings screen and i receive message "The system is running in low-graphics mode"

[itsjustarumour (itsjustarumour-gmail-deactivatedaccount-deactivatedaccount)]

Seeing the same thing on a fresh install of 12.10 (64-bit) with NVidia driver, GT240 graphics card.

From Xorg.0.log:

[ 9613.796] (EE) Backtrace:
[ 9613.796] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7f4138301b76]
[ 9613.796] (EE) 1: /usr/bin/X (0x7f4138159000+0x1ac9a9) [0x7f41383059a9]
[ 9613.796] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f413747f000+0xfcb0) [0x7f413748ecb0]
[ 9613.796] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (0x7f41360e3000+0x1454d0) [0x7f41362284d0]
[ 9613.796] (EE) 4: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f41319ac000+0xf3e40) [0x7f4131a9fe40]
[ 9613.796] (EE) 5: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f41319ac000+0x53ed22) [0x7f4131eead22]
[ 9613.796] (EE) 6: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f41319ac000+0x53ef9b) [0x7f4131eeaf9b]
[ 9613.796] (EE) 7: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f41319ac000+0x53b40a) [0x7f4131ee740a]
[ 9613.796] (EE) 8: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f41319ac000+0x5084a6) [0x7f4131eb44a6]
[ 9613.797] (EE) 9: /usr/bin/X (0x7f4138159000+0xad108) [0x7f4138206108]
[ 9613.797] (EE) 10: /usr/bin/X (AbortDDX+0x85) [0x7f41381eee65]
[ 9613.797] (EE) 11: /usr/bin/X (0x7f4138159000+0x1b3c02) [0x7f413830cc02]
[ 9613.797] (EE) 12: /usr/bin/X (0x7f4138159000+0x1b449d) [0x7f413830d49d]
[ 9613.797] (EE) 13: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f41319ac000+0xc98ae) [0x7f4131a758ae]
[ 9613.797] (EE) 14: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f41319ac000+0x7c2bb) [0x7f4131a282bb]
[ 9613.797] (EE) 15: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f41319ac000+0xf117b) [0x7f4131a9d17b]
[ 9613.797] (EE) 16: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f41319ac000+0xb5db2) [0x7f4131a61db2]
[ 9613.797] (EE) 17: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f41319ac000+0x53fe3c) [0x7f4131eebe3c]
[ 9613.797] (EE) 18: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f41319ac000+0x513c79) [0x7f4131ebfc79]
[ 9613.797] (EE) 19: /usr/bin/X (BlockHandler+0x44) [0x7f41381b2c34]
[ 9613.797] (EE) 20: /usr/bin/X (WaitForSomething+0x114) [0x7f41382fef24]
[ 9613.797] (EE) 21: /usr/bin/X (0x7f4138159000+0x557e1) [0x7f41381ae7e1]
[ 9613.797] (EE) 22: /usr/bin/X (0x7f4138159000+0x4456a) [0x7f413819d56a]
[ 9613.797] (EE) 23: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xed) [0x7f413610476d]
[ 9613.797] (EE) 24: /usr/bin/X (0x7f4138159000+0x448ad) [0x7f413819d8ad]
[ 9613.797] (EE)
[ 9613.797] (EE) Segmentation fault at address 0x7f413805edf8
[ 9613.797]
FatalError re-entered, aborting
[ 9613.797] Caught signal 11 (Segmentation fault). Server aborting
[ 9613.797]

[Marcos Vives Del Sol (socram8888)]

[ 51.033] (EE)
[ 51.034] (EE) Backtrace:
[ 51.035] (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0xb772bc79]
[ 51.035] (EE) 1: /usr/bin/X (0xb7584000+0x1abb66) [0xb772fb66]
[ 51.035] (EE) 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb756140c]
[ 51.035] (EE) 3: /usr/lib/xorg/modules/drivers/sis_drv.so (0xb6f9e000+0x4ed83) [0xb6fecd83]
[ 51.035] (EE) 4: /usr/lib/xorg/modules/drivers/sis_drv.so (0xb6f9e000+0x3a629) [0xb6fd8629]
[ 51.035] (EE) 5: /usr/lib/xorg/modules/drivers/sis_drv.so (0xb6f9e000+0x28aeb) [0xb6fc6aeb]
[ 51.035] (EE) 6: /usr/lib/xorg/modules/libexa.so (0xb6dbb000+0x5278) [0xb6dc0278]
[ 51.035] (EE) 7: /usr/lib/xorg/modules/libexa.so (0xb6dbb000+0x578f) [0xb6dc078f]
[ 51.035] (EE) 8: /usr/lib/xorg/modules/libexa.so (0xb6dbb000+0x5967) [0xb6dc0967]
[ 51.036] (EE) 9: /usr/lib/xorg/modules/libexa.so (0xb6dbb000+0x618a) [0xb6dc118a]
[ 51.036] (EE) 10: /usr/lib/xorg/modules/libexa.so (0xb6dbb000+0x3e9f) [0xb6dbee9f]
[ 51.036] (EE) 11: /usr/lib/xorg/modules/libexa.so (0xb6dbb000+0xa1b2) [0xb6dc51b2]
[ 51.036] (EE) 12: /usr/lib/xorg/modules/libexa.so (0xb6dbb000+0xacc3) [0xb6dc5cc3]
[ 51.036] (EE) 13: /usr/bin/X (0xb7584000+0x12958b) [0xb76ad58b]
[ 51.036] (EE) 14: /usr/bin/X (miPaintWindow+0x266) [0xb770b366]
[ 51.037] (EE) 15: /usr/bin/X (miClearToBackground+0x11c) [0xb772351c]
[ 51.037] (EE) 16: /usr/bin/X (0xb7584000+0x38311) [0xb75bc311]
[ 51.037] (EE) 17: /usr/bin/X (0xb7584000+0x3cba5) [0xb75c0ba5]
[ 51.037] (EE) 18: /usr/bin/X (0xb7584000+0x2a10a) [0xb75ae10a]
[ 51.038] (EE) 19: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb71e04d3]
[ 51.038] (EE) 20: /usr/bin/X (0xb7584000+0x2a4e9) [0xb75ae4e9]
[ 51.038] (EE)
[ 51.039] (EE) Segmentation fault at address 0x0
[ 51.039]
Fatal server error:
[ 51.039] Caught signal 11 (Segmentation fault). Server aborting
[ 51.039]
[ 51.039] (EE)
Please consult the The X.Org Foundation support
  at http://wiki.x.org
 for help.
[ 51.039] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 51.039] (EE)

Lubuntu didn't even boot, crashed before displaying the user login screen.

[Juan Ignacio Rodríguez (nachorodriguez)]

Trying to run sugar-emulator or xephyr :100
ignacio@ignacio:/usr/bin$ Xephyr :100
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension SECURITY
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension SELinux
Initializing built-in extension GLX
(EE)
(EE) Backtrace:
(EE) 0: Xephyr (xorg_backtrace+0x49) [0xb776d369]
(EE) 1: Xephyr (0xb75db000+0x1960d4) [0xb77710d4]
(EE) 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb75b840c]
(EE) 3: Xephyr (0xb75db000+0x2980d) [0xb760480d]
(EE) 4: Xephyr (0xb75db000+0x28918) [0xb7603918]
(EE) 5: Xephyr (0xb75db000+0x23938) [0xb75fe938]
(EE) 6: Xephyr (0xb75db000+0x84a15) [0xb765fa15]
(EE) 7: Xephyr (AddScreen+0x73) [0xb7626fd3]
(EE) 8: Xephyr (0xb75db000+0x84ed5) [0xb765fed5]
(EE) 9: Xephyr (InitOutput+0x4c) [0xb75fcf8c]
(EE) 10: Xephyr (0xb75db000+0x2171b) [0xb75fc71b]
(EE) 11: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0xb704f935]
(EE) 12: Xephyr (0xb75db000+0x21d19) [0xb75fcd19]
(EE)
(EE) Segmentation fault at address 0x10

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

[Alan (alanjas)]

With the latest packages on Saucy (13.10) my problem with Xephyr disappear!
Now, works fine: Xephyr :100

[Esteban (dugueperoux-esteban)]

Updating from 13.04 to 13.10 I get a segfault when executing Xephyr as following :

Xephyr :3 -screen 1440x900x16 &
DISPLAY=:3 metacity

The segfault message :

(EE)
(EE) Backtrace:
Avertissement du gestionnaire de fenêtres : Erreur fatale d'E/S 11 (Ressource temporairement non disponible) sur le visuel « :3 ».
[1]+ Erreur de segmentation (core dumped) Xephyr :3 -screen 1440x900x16

The cause seems comes from the 16 color parameter but if I set 24 instead of 16 it works fine.

[penalvch (penalvch)]

nierce, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p xorg-server REPLACE-WITH-BUG-NUMBER

Please note, given you already have done this in a prior release, performing this on a release prior to Trusty would not be helpful.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Launchpad Janitor (janitor)]

[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]