Bumblbeed cannot launch X server due to SUID X wrapper

Bug #1691331 reported by Andrei Borzenkov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bumblebee (Ubuntu)
New
Undecided
Unassigned

Bug Description

The same problem as reported upstream in https://github.com/Bumblebee-Project/Bumblebee/issues/704 - secondary Xorg fails to start because it is being executed SUID by Xorg.wrap. Disabling executable bits on /usr/lib/xorg/Xorg.wrap makes it work.

Patch in https://github.com/Bumblebee-Project/Bumblebee/pull/743 allows setting Xorg binary path in bumblebee.conf working around this issue.

As a side note - as shipped bumblebee contains references to nvidia-current, but it appears at least some of nvidia packages do not set this alias. I suppose when I started with Ubuntu using 14.04, nvidia-340 was current; I never changed this version since then. Now it is no more current so I had to edit bumblebee.conf to explicitly point to nvidia-340.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: bumblebee 3.2.1-10
ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-51-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Wed May 17 07:17:34 2017
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-20140620-0
InstallationDate: Installed on 2015-07-02 (684 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25
SourcePackage: bumblebee
UpgradeStatus: Upgraded to xenial on 2016-10-29 (199 days ago)
mtime.conffile..etc.bumblebee.bumblebee.conf: 2017-05-17T07:06:00.523418
mtime.conffile..etc.bumblebee.xorg.conf.nouveau: 2016-10-29T14:38:07.748432
mtime.conffile..etc.bumblebee.xorg.conf.nvidia: 2016-10-29T14:41:41.888434

Revision history for this message
Andrei Borzenkov (arvidjaar-s) wrote :
Revision history for this message
Luca Boccassi (bluca) wrote :

This was fixed in 3.2.1-11

Revision history for this message
Andrei Borzenkov (arvidjaar-s) wrote :

Any chance it cam be released for 16.04 via updates?

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.