← Back to team overview

desktop-packages team mailing list archive

[Bug 1236206] Re: [xmir] Xorg crashed with SIGABRT in __GI_raise()


The old Xmir is no longer supported and a new version is being

** Changed in: xorg-server (Ubuntu)
       Status: New => Won't Fix

** Tags added: xmir

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.

  [xmir] Xorg crashed with SIGABRT in __GI_raise()

Status in xorg-server package in Ubuntu:
  Won't Fix

Bug description:
  No idea what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-core 2:1.14.3-3ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Oct  6 20:52:55 2013
  DistUpgraded: 2013-06-07 19:16:22,118 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:21da]
  InstallationDate: Installed on 2011-08-19 (779 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110817)
  MachineType: LENOVO 429149G
  MarkForUpload: True
  ProcCmdline: /usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -mir 0 -mirSocket /tmp/mir_socket -nolisten tcp
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-11-generic root=UUID=51ab960b-a2da-4841-98ce-c017f0582971 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
   #0  0x00007f5d6e121f77 in __GI_raise (sig=6, sig@entry=<Fehler beim Lesen der Variable: Cannot access memory at address 0x7fff2f970b98>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
           resultvar = 0
           pid = 1227
           selftid = 1227
   Cannot access memory at address 0x7fff2f970b98
  StacktraceTop: __GI_raise (sig=6, sig@entry=<Fehler beim Lesen der Variable: Cannot access memory at address 0x7fff2f970b98>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to saucy on 2013-06-07 (121 days ago)
  UserGroups: utah
  dmi.bios.date: 05/18/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET46WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 429149G
  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:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 429149G
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.10+13.10.20131004-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.903-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
  xserver.bootTime: Mon Oct  7 07:56:19 2013
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
   product id                                 728 
   vendor                                     LGD
  xserver.version: 2:1.14.3-3ubuntu1

To manage notifications about this bug go to: