xerver-xorg-core 2:1.13.3-0ubuntu3 breaks bumblebee

Bug #1163404 reported by Bruno Pagani
404
This bug affects 91 people
Affects Status Importance Assigned to Milestone
X.Org X server
Confirmed
Undecided
Unassigned

Bug Description

Since this version, Bumblebee fails to start a secondary xserver on the NVIDIA card, with either nouveau or any flavors of the nvidia graphics driver.

Is this an issue on the Bumblebee side, and then how to fix it, or is this changes made by Ubuntu that causes this problem (indeed they do, but the question is about who has to fix this)?

Maarten Lankhorst answered this when contacted by email:
If you want to load the nvidia module you need to specify it explicitly in your configuration. Intel failed
to be detected before because of a bug. You were probably already running a xserver with intel.
Before it would just fail entirely because the intel card was already in use, now it still detects the
intel card through udev.

As a workaround I suppose you could append something like -seat bla, in which case the intel
device will not be found through udev, unless you had the ID_SEAT property for that device set to bla too.

However, I haven't been able to make the seat option to work either since in fact this is equivalent to what we do with loading X using custom conf files.

I'm providing logs for the non-working case, and will ask someone to add those for the working one (can't revert to 2b1 at the moment).

Revision history for this message
Bruno Pagani (b-pagani) wrote :
Revision history for this message
Bruno Pagani (b-pagani) wrote :
Revision history for this message
CirclingTheSun (circlingthesun) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xorg-server (Ubuntu):
status: New → Confirmed
Revision history for this message
David Knoll (davidknoll) wrote :

Me too, here's my Xorg.8.log. Maybe now I know what the bug is I can try the 310 drivers again.

Revision history for this message
3vi1 (launchpad-net-eternaldusk) wrote :

I tested with the nvidia-313-updates package on my new P150EM and got the same results. Backleveling xserver -xorg-core works around the problem.

Revision history for this message
Bruno Pagani (b-pagani) wrote :

Setting BusID in nouveau and nvidia xorg.conf file solves this. However, this is not normal, since isolateDevice should have the same effect.

Revision history for this message
Bruno Pagani (b-pagani) wrote :

So some detailed informations: we use -isolateDevice on the nvidia card, and set AutoAddGPU to false. This is working everywhere else, and has been working on Ubuntu up to 1.13.3-0ubuntu3.

Adding BusID is making things work, but normally, our setup is doing already more than that, and BusID shouldn't be needed when isolateDevice and AutoAddGPUs are set...

Revision history for this message
peterrus (petorrus) wrote :
Revision history for this message
Bruno Pagani (b-pagani) wrote :

Seems to be a bug in upstream X.org, that Ubuntu patches uncovered: https://bugs.freedesktop.org/show_bug.cgi?id=63576

Revision history for this message
3vi1 (launchpad-net-eternaldusk) wrote :

This appears to have been fixed at some point. Testing with current packages is not showing the problem.

Revision history for this message
Bruno Pagani (b-pagani) wrote :

Yes, because we changed the config files of Bumblebee to cover this case, but the upstream bug in X.org still exists.

affects: xorg-server (Ubuntu) → xorg-server
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

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