Your message dated Tue, 17 May 2016 23:49:20 +0000
with message-id <[email protected]>
and subject line Bug#822665: fixed in bumblebee 3.2.1-12
has caused the Debian Bug report #822665,
regarding bumblebee: reports wrong error message from Xorg log
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
822665: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822665
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bumblebee
Version: 3.2.1-10

When trying to use bumblebee those days, the reported failure is:

$ optirun xterm
[42519.843834] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) 
/dev/dri/card0: failed to set DRM interface version 1.4: Permission denied

[42519.843864] [ERROR]Aborting because fallback start is disabled.
$ 

Looking in Xorg.8.log, we can see:

[ 42519.553] (II) xfree86: Adding drm device (/dev/dri/card1)
[ 42519.840] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 42519.840] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: 
Permission denied
[ 42519.841] (--) PCI:*(0:1:0:0) 10de:139b:1462:1139 rev 162, Mem @ 
0xa2000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 
0x00004000/128, BIOS @ 0x????????/524288
...
[ 42519.843] (II) [drm] nouveau interface version: 1.3.1
[ 42519.843] (EE) Unknown chipset: NV117
[ 42519.843] (EE) No devices detected.
[ 42519.843] (EE) 
Fatal server error:
[ 42519.843] (EE) no screens found(EE) 

The "permission denied" is quite strange, as the device does have the ACL 
allowing RW for the current user.
But anyway that card is already used by :0, could it be that the error code 
returned by the DRI device is
just wrong (EPERM instead of EBUSY) ?

Anyway, that error does not appear to be fatal to Xorg, which does list the 
second one as fatal,
and incidentally that error message looks like a much more understandable reason

--- End Message ---
--- Begin Message ---
Source: bumblebee
Source-Version: 3.2.1-12

We believe that the bug you reported is fixed in the latest version of
bumblebee, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Luca Boccassi <[email protected]> (supplier of updated bumblebee package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Wed, 18 May 2016 00:17:59 +0100
Source: bumblebee
Binary: bumblebee bumblebee-nvidia
Architecture: source
Version: 3.2.1-12
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers <[email protected]>
Changed-By: Luca Boccassi <[email protected]>
Description:
 bumblebee  - NVIDIA Optimus support for Linux
 bumblebee-nvidia - NVIDIA Optimus support using the proprietary NVIDIA driver
Closes: 822665
Changes:
 bumblebee (3.2.1-12) unstable; urgency=medium
 .
   [ Luca Boccassi ]
   * Set nvidia lib directory to /usr/lib/nvidia/nvidia to solve
     incompatibility between Bumblebee and concurrent installations of
     current plus legacyYYYxx Nvidia driver series on the same system.
   * Add ignore-systemd-logind-noise.patch and
     ignore-failure-to-set-DRM-interface.patch to ignore red herrings.
     (Closes: #822665)
   * Set Ubuntu default kernel driver to nvidia, which is provided as a
     modprobe alias by the nvidia-XYZ packages.
 .
   [ Vincent Cheng ]
   * Use dh_strip --dbgsym-migration to cleanly migrate from old-style dbg
     packages to autogenerated dbgsym packages.
Checksums-Sha1:
 b6e79dc3956d28251797eaa76330dfb6d0ea04e5 2217 bumblebee_3.2.1-12.dsc
 cb585b19c3c3473f7c39940dd128a037bccc869c 13876 bumblebee_3.2.1-12.debian.tar.xz
Checksums-Sha256:
 3d7c14596210604bb0c0537ebf03f32952c44b920ec246507ed0a0e5c60e5a7e 2217 
bumblebee_3.2.1-12.dsc
 3cc991ee500aecdf6e486d748ac57c90aedf88c21d8d0b2858302916aeed1655 13876 
bumblebee_3.2.1-12.debian.tar.xz
Files:
 aba68998f70fc207a9829f3cdf9f8369 2217 utils extra bumblebee_3.2.1-12.dsc
 eeec2001427db1281f469440be200e1b 13876 utils extra 
bumblebee_3.2.1-12.debian.tar.xz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJXO6f3AAoJEChr9+/NdyQeOsoP/0nXJcECekHVYsqnijZylU4S
3YoRC4M20C2fPSLfc1XTH26gzgs9F0XvMwoMMWkGMD/So7NpvtWEcgERWa+pC8at
sRV/dH+qJ2v1kr52VeKJ/i9LibUaCBFJkBDvy2Q2gm3qIP/bPFah/NxQMsDy2aua
FVtUTfdALiPtmEBMkTnbUlkHQYuq10naxoqsBsTxJtG7GoykROP27IlIPR+JEIwH
dpm7rUbvu3osIOjQ0HXxnvWDGlNGa7j2Yy0AzC18RRYZU7d0l0zCGGLn3G0O2w7q
unHO7QlfXtrADFid6/30i9WW+A2akR1NVOxypT2QryPMQscQyT90Ed1P6aYCeJUx
D/hrtMiukEamNWEvH7Sp5Bqrc7rdHSveKno9azxCSWSAPlhjutAWKcKHtTcSfOom
9U0H7lmX0B1bqPNFOEhzAuuwUfV8Z9sMw5VSKLb26HuPBr82NQAQGNIP/H8h0tna
Awi8OxMqs1Lk9aGw+p5P6T5VC342tjapbCPVpmp2vluxDu7rBTeGxjmwWKgXtbso
/EwGgYLmOBwXFdtGDZPgDwXADyRacrQ/xfe/QzyqofYAiLLq6qO2GuycR8DdwajE
3PdSJrnfKZLJ1IhaxUwSEn7uhg6T6G4wP4JQ+yYLvJeNKisjH+m7NuzjcMMewPBO
n9AIZkq+5IAwD8bY+5dO
=dBy9
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to