XMir fails to start on intel

Bug #1208715 reported by Robert Ancell
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Fix Released
Critical
Chris Halse Rogers

Bug Description

XMir is not starting using the staging version of Mir (0.0.8+13.10.20130803bzr925saucy0) and the Xorg (1.14.2-0ubuntu8) from main.

To reproduce:

on VT1:
$ sudo mir_demo_server

on VT2:
$ sudo X -retro -mir X :1

Expected result:
Horrible X background shown

Observed result:
Black background. X running at 100% CPU.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: xserver-xorg-xmir 2:1.14.2-0ubuntu8
ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
Uname: Linux 3.10.0-6-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.12-0ubuntu2
Architecture: amd64
CheckboxSubmission: e440e09ef58a53bccc45087674ba6b8e
CheckboxSystem: d00f84de8a555815fa1c4660280da308
CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Aug 6 17:13:51 2013
DistUpgraded: 2011-07-06 09:01:04,742 DEBUG enabling apt cron job
DistroCodename: saucy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:044e]
 NVIDIA Corporation GT218M [GeForce 310M] [10de:0a75] (rev a2) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:044e]
InstallationDate: Installed on 2011-04-01 (858 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
MachineType: Dell Inc. Vostro 3500
MarkForUpload: True
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic root=UUID=6c20ea74-9ae6-400e-b5b2-6f148c4e3209 ro quiet splash vt.handoff=7
SourcePackage: xorg-server
UpgradeStatus: Upgraded to saucy on 2011-07-05 (762 days ago)
dmi.bios.date: 10/25/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 0NVXFV
dmi.board.vendor: Dell Inc.
dmi.board.version: A10
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A10
dmi.modalias: dmi:bvnDellInc.:bvrA10:bd10/25/2010:svnDellInc.:pnVostro3500:pvrA10:rvnDellInc.:rn0NVXFV:rvrA10:cvnDellInc.:ct8:cvrA10:
dmi.product.name: Vostro 3500
dmi.product.version: A10
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.46-1~ppa1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.2~git20130628.g6b676e6-0ubuntu0+mir4-jenkins86saucy0
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.2~git20130628.g6b676e6-0ubuntu0+mir4-jenkins86saucy0
version.xserver-xorg-core: xserver-xorg-core 2:1.14.2-0ubuntu8
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.1.0+xmir2538-0~saucy1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.9+xmir15871-2~saucy1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.8+xmir2340-0~saucy1
xserver.bootTime: Tue Aug 6 12:38:22 2013
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 NOUVEAU(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 9196
 vendor AUO
xserver.version: 2:1.14.2-0ubuntu8

Revision history for this message
Robert Ancell (robert-ancell) wrote :
Revision history for this message
Robert Ancell (robert-ancell) wrote :

Also tried with the staging version of X (1.14.2-0ubuntu8)

Revision history for this message
Robert Ancell (robert-ancell) wrote :

Correction - Also tried with the staging version of X (1.14.2-0ubuntu9)

Revision history for this message
Robert Ancell (robert-ancell) wrote :

Interesting note - when I run X from inside Unity it works. It only fails when running X from a VT.

Changed in xorg-server (Ubuntu):
assignee: nobody → Chris Halse Rogers (raof)
Revision history for this message
Robert Ancell (robert-ancell) wrote :
Revision history for this message
kevin gunn (kgunn72) wrote :

OK, so I purged this morning. unpinned the system-compositor-testing ppa.
then updated/dist-upgraded (which meant i should have mir & xorg-xmir from main)
then i downloaded and installed u-s-c from https://launchpad.net/~ubuntu-unity/+archive/daily-build-next

and it failed (i'm on intel)

the u-s-c log says

"/usr/sbin/unity-system-compositor: Symbol `_ZTVN3mir26DefaultServerConfigurationE' has different size in shared object, consider re-linking
*** Error in `/usr/sbin/unity-system-compositor': malloc(): memory corruption: 0x00000000023fe650 ***"

and it fell back to standalone X (but not the first time)

Revision history for this message
kevin gunn (kgunn72) wrote :

followed Robert's example above to run x on mir_demo_server

I did not get the black screen w/ 100% cpu

however, i did get some debug info in my VT2 after typing $ sudo X -retro -mir X :1

it initialized a bunch of stuff, then tried to load GLX and said driver needs flags 1, then needs flags 0, then needs flags 0...all with "incompatible with nested, deleting"
the last print is ...X symbol lookup error in the intel_drv.so undefined symbol xmir_get_drm_info

Revision history for this message
kevin gunn (kgunn72) wrote :

note, my config is mir + xorg from main

Revision history for this message
kevin gunn (kgunn72) wrote :

OK - slight alteration to my setup.
using daily-build ppa instead of daily-build-next ppa.....daily-build is correct one (as daily-build-next contains older stuff)

so now for both xmir boot & the VT mir server demo above....i'm segfaulting in X the same way

"[ 2155.837] (II) No input driver specified, ignoring this device.
[ 2155.837] (II) This device may have been added with another device file.
[ 2155.840] (EE)
[ 2155.840] (EE) Backtrace:
[ 2155.858] (EE) 0: X (xorg_backtrace+0x3d) [0x7f3642203a7d]
[ 2155.858] (EE) 1: X (0x7f3642062000+0x1a57e9) [0x7f36422077e9]
[ 2155.858] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f3641162000+0xfbb0) [0x7f3641171bb0]
[ 2155.859] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f363cdab000+0xdcc22) [0x7f363ce87c22]
[ 2155.859] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f363cdab000+0xa1a1d) [0x7f363ce4ca1d]
[ 2155.859] (EE) 5: /usr/lib/xorg/modules/extensions/libxmir.so (xmir_screen_for_each_damaged_window+0x3c) [0x7f363e7ebe9c]
[ 2155.859] (EE) 6: X (BlockHandler+0x44) [0x7f36420bae74]
[ 2155.859] (EE) 7: X (WaitForSomething+0x124) [0x7f3642200fc4]
[ 2155.859] (EE) 8: X (0x7f3642062000+0x54b81) [0x7f36420b6b81]
[ 2155.859] (EE) 9: X (0x7f3642062000+0x4442a) [0x7f36420a642a]
[ 2155.859] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7f363fdb0de5]
[ 2155.859] (EE) 11: X (0x7f3642062000+0x4476f) [0x7f36420a676f]
[ 2155.859] (EE)
[ 2155.859] (EE) Segmentation fault at address 0x7f36424a0004
[ 2155.859] (EE)
Fatal server error:
[ 2155.859] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 2155.859] (EE)
[ 2155.859] (EE) "

Revision history for this message
Robert Ancell (robert-ancell) wrote :

Confirmed fixed in 1.14.2-0ubuntu9

Changed in xorg-server (Ubuntu):
importance: Undecided → Critical
status: New → Fix Released
Revision history for this message
rikolk@upcmail.nl (kolkvdr) wrote :

should this problem be fixed in 1.14.2-0ubuntu9?
because i still have the following error:

/usr/sbin/unity-system-compositor: Symbol `_ZTVN3mir26DefaultServerConfigurationE' has different size in shared object, cons
ider re-linking
*** Error in `/usr/sbin/unity-system-compositor': malloc(): memory corruption: 0x0000000000e17680 ***

dpkg result:
xserver-xorg-xmir 2:1.14.2-0ubuntu9 amd64 Xorg - the X.Org X server (module for running nested in Mir)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.