[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/740785/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
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 ** No longer affects: xorg (Ubuntu) ** Attachment removed: Log containing backtrace https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/740785/+attachment/2113963/+files/Xorg.1.log ** Attachment removed: Xorg.crash.log https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/740785/+attachment/2124313/+files/Xorg.crash.log ** Attachment removed: Xorg.0.log.old.txt https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/740785/+attachment/3508200/+files/Xorg.0.log.old.txt ** Changed in: xorg-server (Ubuntu) Importance: High = Low ** Changed in: xorg-server (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/740785/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
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. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/740785/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
With the latest packages on Saucy (13.10) my problem with Xephyr disappear! Now, works fine: Xephyr :100 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/740785/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
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 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/740785/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
[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. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/740785/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
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] ** Attachment added: Xorg.0.log.old.txt https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/740785/+attachment/3508200/+files/Xorg.0.log.old.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/740785/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
** No longer affects: unity (Ubuntu) ** No longer affects: lightdm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/740785/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
In my case this problem randomly appears on boot before greetings screen and i receive message The system is running in low-graphics mode -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/740785/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
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 (0xb753+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 (0xb753+0x81474) [0xb75b1474] 7: /usr/bin/X (xf86BusConfig+0xc1) [0xb759fbf1] 8: /usr/bin/X (InitOutput+0x7ca) [0xb75acc2a] 9: /usr/bin/X (0xb753+0x251a0) [0xb75551a0] 10: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb71904d3] 11: /usr/bin/X (0xb753+0x25699) [0xb7555699] Segmentation fault at address (nil) Caught signal 11 (Segmentation fault). Server aborting -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/740785/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
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 (0xb19e+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 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/740785/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
I use Kubuntu 12.04 with fglrx driver. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/740785/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
** Changed in: lightdm (Ubuntu) Status: New = Invalid ** Changed in: unity (Ubuntu) Status: New = Invalid ** Changed in: xorg (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/740785/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
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 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/740785/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
Gotcha. Will do. After doing that, should I mark this bug as a duplicate? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/740785/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
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. ** Changed in: xorg-server (Ubuntu) Status: Expired = Confirmed ** Also affects: xorg (Ubuntu) Importance: Undecided Status: New ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Also affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/740785/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
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. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/740785/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/740785/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
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. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
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. ** Changed in: xorg-server (Ubuntu) Importance: Undecided = High ** Changed in: xorg-server (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
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 ** Attachment added: ubuntu-bug xorg https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/740785/+attachment/2143335/+files/xorg.crash ** Changed in: xorg-server (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
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. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
My 64-bit Maverick runs without a crash for 9 days now on 270.41.06 nVidia binary drivers. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
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. ** Attachment added: Xorg.crash.log https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/740785/+attachment/2124313/+files/Xorg.crash.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
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. ** Attachment added: Xorg.crash3.log https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/740785/+attachment/2124357/+files/Xorg.crash3.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
** Attachment removed: Xorg.crash3.log https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/740785/+attachment/2124357/+files/Xorg.crash3.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
Please ignore my comment #14 for now, as this seems to be a completely different bug. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
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 (0x40+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 (0x40+0x3fa46) [0x43fa46] [102303.074] 7: /usr/bin/X (0x40+0x2187b) [0x42187b] [102303.074] 8: /lib/libc.so.6 (__libc_start_main+0xfe) [0x7ff6600b7d8e] [102303.074] 9: /usr/bin/X (0x40+0x21409) [0x421409] [102303.075] Segmentation fault at address (nil) [102303.075] Caught signal 11 (Segmentation fault). Server aborting -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
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. ** Attachment added: Log containing backtrace https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/740785/+attachment/2113963/+files/Xorg.1.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
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 ** Attachment added: result file from ubuntu-bug xorg https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/740785/+attachment/2108392/+files/ubuntu-bug-xorg -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
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 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
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 ** Tags added: apport-collected natty ubuntu unity-2d -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
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 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
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-collectbug-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 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
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 (0x40+0x40f23) [0x440f23] [36.899] 12: /usr/bin/X (0x40+0x21a7e) [0x421a7e] [36.899] 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xff) [0x7fae4ec29eff] [36.899] 14: /usr/bin/X (0x40+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 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
I'm getting this on 11.04 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
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 (0x40+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 (0x40+0x3fa46) [0x43fa46] [ 7808.924] 7: /usr/bin/X (0x40+0x2187b) [0x42187b] [ 7808.924] 8: /lib/libc.so.6 (__libc_start_main+0xfe) [0x7f9f692f5d8e] [ 7808.924] 9: /usr/bin/X (0x40+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 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
If you need any files, let me know and I'll do a dump and attach them. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
** Package changed: xorg (Ubuntu) = xorg-server (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
