Activity log for bug #1464928

Date Who What changed Old value New value Message
2015-06-13 23:01:30 Karl-Philipp Richter bug added bug
2015-06-13 23:04:07 Karl-Philipp Richter description Specifying a `KernelDriver` containing `_` or `-` in the `nvidia` driver section of `/etc/bumblebee/bumblebee.conf` causes `optirun bash` to fail with [ 533.997079] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) Failed to load module "nvidia352" (module does not exist, 0) [ 533.997196] [ERROR]Aborting because fallback start is disabled. if `nvidia_352` or `nvidia-352` has been specified. Futhermore this is impossible to debug without massive loss of sanity if `optirun` doesn't tell where configuration options have been picked up from if a critical error occured. `grep -r 'nvidia352' /etc/bumblebee/` returns no result. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bumblebee 3.2.1-7 Uname: Linux 4.1.0-040100rc7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 14 00:53:57 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-06-08 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: bumblebee UpgradeStatus: Upgraded to vivid on 2015-06-09 (4 days ago) mtime.conffile..etc.bumblebee.bumblebee.conf: 2015-06-14T00:53:00.911443 mtime.conffile..etc.bumblebee.xorg.conf.nouveau: 2015-06-09T20:38:24.773993 mtime.conffile..etc.bumblebee.xorg.conf.nvidia: 2015-06-14T00:43:34.468919 Specifying a `KernelDriver` containing `_` or `-` in the `nvidia` driver section of `/etc/bumblebee/bumblebee.conf` causes `optirun bash` to fail with     [ 533.997079] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) Failed to load module "nvidia352" (module does not exist, 0)     [ 533.997196] [ERROR]Aborting because fallback start is disabled. if `nvidia_352` or `nvidia-352` has been specified. Futhermore this is impossible to debug without massive loss of sanity if `optirun` doesn't tell where configuration options have been picked up from if a critical error occured. `grep -r 'nvidia352' /etc/bumblebee/` returns no result. The specified module exists as shown by `modinfo`: $ modinfo nvidia_352 filename: /lib/modules/4.1.0-040100rc7-generic/updates/dkms/nvidia_352.ko alias: char-major-195-* version: 352.09 supported: external license: NVIDIA alias: pci:v000010DEd00000E00sv*sd*bc04sc80i00* alias: pci:v000010DEd*sv*sd*bc03sc02i00* alias: pci:v000010DEd*sv*sd*bc03sc00i00* depends: drm vermagic: 4.1.0-040100rc7-generic SMP mod_unload modversions parm: NVreg_Mobile:int parm: NVreg_ResmanDebugLevel:int parm: NVreg_RmLogonRC:int parm: NVreg_ModifyDeviceFiles:int parm: NVreg_DeviceFileUID:int parm: NVreg_DeviceFileGID:int parm: NVreg_DeviceFileMode:int parm: NVreg_UpdateMemoryTypes:int parm: NVreg_InitializeSystemMemoryAllocations:int parm: NVreg_UsePageAttributeTable:int parm: NVreg_MapRegistersEarly:int parm: NVreg_RegisterForACPIEvents:int parm: NVreg_CheckPCIConfigSpace:int parm: NVreg_EnablePCIeGen3:int parm: NVreg_EnableMSI:int parm: NVreg_MemoryPoolSize:int parm: NVreg_RegistryDwords:charp parm: NVreg_RmMsg:charp parm: NVreg_AssignGpus:charp ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bumblebee 3.2.1-7 Uname: Linux 4.1.0-040100rc7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 14 00:53:57 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-06-08 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron:  TERM=xterm  PATH=(custom, no user)  XDG_RUNTIME_DIR=<set>  LANG=de_DE.UTF-8  SHELL=/bin/bash SourcePackage: bumblebee UpgradeStatus: Upgraded to vivid on 2015-06-09 (4 days ago) mtime.conffile..etc.bumblebee.bumblebee.conf: 2015-06-14T00:53:00.911443 mtime.conffile..etc.bumblebee.xorg.conf.nouveau: 2015-06-09T20:38:24.773993 mtime.conffile..etc.bumblebee.xorg.conf.nvidia: 2015-06-14T00:43:34.468919
2015-06-22 15:03:32 Launchpad Janitor bumblebee (Ubuntu): status New Confirmed
2015-06-22 15:13:57 joseangelmadrid bug added subscriber joseangelmadrid
2015-06-25 15:24:05 Alberto Salvia Novella bumblebee (Ubuntu): importance Undecided High
2015-11-28 03:00:37 Karl-Philipp Richter tags amd64 apport-bug vivid amd64 apport-bug apport-collected vivid wily
2015-11-28 03:00:38 Karl-Philipp Richter description Specifying a `KernelDriver` containing `_` or `-` in the `nvidia` driver section of `/etc/bumblebee/bumblebee.conf` causes `optirun bash` to fail with     [ 533.997079] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) Failed to load module "nvidia352" (module does not exist, 0)     [ 533.997196] [ERROR]Aborting because fallback start is disabled. if `nvidia_352` or `nvidia-352` has been specified. Futhermore this is impossible to debug without massive loss of sanity if `optirun` doesn't tell where configuration options have been picked up from if a critical error occured. `grep -r 'nvidia352' /etc/bumblebee/` returns no result. The specified module exists as shown by `modinfo`: $ modinfo nvidia_352 filename: /lib/modules/4.1.0-040100rc7-generic/updates/dkms/nvidia_352.ko alias: char-major-195-* version: 352.09 supported: external license: NVIDIA alias: pci:v000010DEd00000E00sv*sd*bc04sc80i00* alias: pci:v000010DEd*sv*sd*bc03sc02i00* alias: pci:v000010DEd*sv*sd*bc03sc00i00* depends: drm vermagic: 4.1.0-040100rc7-generic SMP mod_unload modversions parm: NVreg_Mobile:int parm: NVreg_ResmanDebugLevel:int parm: NVreg_RmLogonRC:int parm: NVreg_ModifyDeviceFiles:int parm: NVreg_DeviceFileUID:int parm: NVreg_DeviceFileGID:int parm: NVreg_DeviceFileMode:int parm: NVreg_UpdateMemoryTypes:int parm: NVreg_InitializeSystemMemoryAllocations:int parm: NVreg_UsePageAttributeTable:int parm: NVreg_MapRegistersEarly:int parm: NVreg_RegisterForACPIEvents:int parm: NVreg_CheckPCIConfigSpace:int parm: NVreg_EnablePCIeGen3:int parm: NVreg_EnableMSI:int parm: NVreg_MemoryPoolSize:int parm: NVreg_RegistryDwords:charp parm: NVreg_RmMsg:charp parm: NVreg_AssignGpus:charp ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bumblebee 3.2.1-7 Uname: Linux 4.1.0-040100rc7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 14 00:53:57 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-06-08 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron:  TERM=xterm  PATH=(custom, no user)  XDG_RUNTIME_DIR=<set>  LANG=de_DE.UTF-8  SHELL=/bin/bash SourcePackage: bumblebee UpgradeStatus: Upgraded to vivid on 2015-06-09 (4 days ago) mtime.conffile..etc.bumblebee.bumblebee.conf: 2015-06-14T00:53:00.911443 mtime.conffile..etc.bumblebee.xorg.conf.nouveau: 2015-06-09T20:38:24.773993 mtime.conffile..etc.bumblebee.xorg.conf.nvidia: 2015-06-14T00:43:34.468919 Specifying a `KernelDriver` containing `_` or `-` in the `nvidia` driver section of `/etc/bumblebee/bumblebee.conf` causes `optirun bash` to fail with     [ 533.997079] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) Failed to load module "nvidia352" (module does not exist, 0)     [ 533.997196] [ERROR]Aborting because fallback start is disabled. if `nvidia_352` or `nvidia-352` has been specified. Futhermore this is impossible to debug without massive loss of sanity if `optirun` doesn't tell where configuration options have been picked up from if a critical error occured. `grep -r 'nvidia352' /etc/bumblebee/` returns no result. The specified module exists as shown by `modinfo`: $ modinfo nvidia_352 filename: /lib/modules/4.1.0-040100rc7-generic/updates/dkms/nvidia_352.ko alias: char-major-195-* version: 352.09 supported: external license: NVIDIA alias: pci:v000010DEd00000E00sv*sd*bc04sc80i00* alias: pci:v000010DEd*sv*sd*bc03sc02i00* alias: pci:v000010DEd*sv*sd*bc03sc00i00* depends: drm vermagic: 4.1.0-040100rc7-generic SMP mod_unload modversions parm: NVreg_Mobile:int parm: NVreg_ResmanDebugLevel:int parm: NVreg_RmLogonRC:int parm: NVreg_ModifyDeviceFiles:int parm: NVreg_DeviceFileUID:int parm: NVreg_DeviceFileGID:int parm: NVreg_DeviceFileMode:int parm: NVreg_UpdateMemoryTypes:int parm: NVreg_InitializeSystemMemoryAllocations:int parm: NVreg_UsePageAttributeTable:int parm: NVreg_MapRegistersEarly:int parm: NVreg_RegisterForACPIEvents:int parm: NVreg_CheckPCIConfigSpace:int parm: NVreg_EnablePCIeGen3:int parm: NVreg_EnableMSI:int parm: NVreg_MemoryPoolSize:int parm: NVreg_RegistryDwords:charp parm: NVreg_RmMsg:charp parm: NVreg_AssignGpus:charp ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bumblebee 3.2.1-7 Uname: Linux 4.1.0-040100rc7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 14 00:53:57 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-06-08 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron:  TERM=xterm  PATH=(custom, no user)  XDG_RUNTIME_DIR=<set>  LANG=de_DE.UTF-8  SHELL=/bin/bash SourcePackage: bumblebee UpgradeStatus: Upgraded to vivid on 2015-06-09 (4 days ago) mtime.conffile..etc.bumblebee.bumblebee.conf: 2015-06-14T00:53:00.911443 mtime.conffile..etc.bumblebee.xorg.conf.nouveau: 2015-06-09T20:38:24.773993 mtime.conffile..etc.bumblebee.xorg.conf.nvidia: 2015-06-14T00:43:34.468919 --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 InstallationDate: Installed on 2013-10-17 (771 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) NonfreeKernelModules: nvidia Package: bumblebee 3.2.1-9 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=de_DE.UTF-8 SHELL=/bin/bash Tags: wily Uname: Linux 4.3.0-040300-generic x86_64 UpgradeStatus: Upgraded to wily on 2015-11-19 (8 days ago) UserGroups: adm bumblebee cdrom dip lpadmin netdev plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.bumblebee.bumblebee.conf: 2015-11-28T03:22:03.840889 mtime.conffile..etc.bumblebee.xorg.conf.nouveau: 2015-11-19T05:20:30.927814 mtime.conffile..etc.bumblebee.xorg.conf.nvidia: 2015-11-28T03:22:29.796691
2015-11-28 03:00:39 Karl-Philipp Richter attachment added Dependencies.txt https://bugs.launchpad.net/bugs/1464928/+attachment/4526526/+files/Dependencies.txt
2015-11-28 03:00:48 Karl-Philipp Richter attachment added JournalErrors.txt https://bugs.launchpad.net/bugs/1464928/+attachment/4526527/+files/JournalErrors.txt
2015-11-28 03:00:49 Karl-Philipp Richter attachment added modified.conffile..etc.bumblebee.bumblebee.conf.txt https://bugs.launchpad.net/bugs/1464928/+attachment/4526528/+files/modified.conffile..etc.bumblebee.bumblebee.conf.txt
2015-11-28 03:00:50 Karl-Philipp Richter attachment added modified.conffile..etc.bumblebee.xorg.conf.nouveau.txt https://bugs.launchpad.net/bugs/1464928/+attachment/4526529/+files/modified.conffile..etc.bumblebee.xorg.conf.nouveau.txt
2015-11-28 03:00:51 Karl-Philipp Richter attachment added modified.conffile..etc.bumblebee.xorg.conf.nvidia.txt https://bugs.launchpad.net/bugs/1464928/+attachment/4526530/+files/modified.conffile..etc.bumblebee.xorg.conf.nvidia.txt
2016-11-07 02:35:31 Karl-Philipp Richter tags amd64 apport-bug apport-collected vivid wily amd64 apport-bug apport-collected third-party-packages vivid wily yakkety
2016-11-07 02:35:33 Karl-Philipp Richter description Specifying a `KernelDriver` containing `_` or `-` in the `nvidia` driver section of `/etc/bumblebee/bumblebee.conf` causes `optirun bash` to fail with     [ 533.997079] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) Failed to load module "nvidia352" (module does not exist, 0)     [ 533.997196] [ERROR]Aborting because fallback start is disabled. if `nvidia_352` or `nvidia-352` has been specified. Futhermore this is impossible to debug without massive loss of sanity if `optirun` doesn't tell where configuration options have been picked up from if a critical error occured. `grep -r 'nvidia352' /etc/bumblebee/` returns no result. The specified module exists as shown by `modinfo`: $ modinfo nvidia_352 filename: /lib/modules/4.1.0-040100rc7-generic/updates/dkms/nvidia_352.ko alias: char-major-195-* version: 352.09 supported: external license: NVIDIA alias: pci:v000010DEd00000E00sv*sd*bc04sc80i00* alias: pci:v000010DEd*sv*sd*bc03sc02i00* alias: pci:v000010DEd*sv*sd*bc03sc00i00* depends: drm vermagic: 4.1.0-040100rc7-generic SMP mod_unload modversions parm: NVreg_Mobile:int parm: NVreg_ResmanDebugLevel:int parm: NVreg_RmLogonRC:int parm: NVreg_ModifyDeviceFiles:int parm: NVreg_DeviceFileUID:int parm: NVreg_DeviceFileGID:int parm: NVreg_DeviceFileMode:int parm: NVreg_UpdateMemoryTypes:int parm: NVreg_InitializeSystemMemoryAllocations:int parm: NVreg_UsePageAttributeTable:int parm: NVreg_MapRegistersEarly:int parm: NVreg_RegisterForACPIEvents:int parm: NVreg_CheckPCIConfigSpace:int parm: NVreg_EnablePCIeGen3:int parm: NVreg_EnableMSI:int parm: NVreg_MemoryPoolSize:int parm: NVreg_RegistryDwords:charp parm: NVreg_RmMsg:charp parm: NVreg_AssignGpus:charp ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bumblebee 3.2.1-7 Uname: Linux 4.1.0-040100rc7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 14 00:53:57 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-06-08 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron:  TERM=xterm  PATH=(custom, no user)  XDG_RUNTIME_DIR=<set>  LANG=de_DE.UTF-8  SHELL=/bin/bash SourcePackage: bumblebee UpgradeStatus: Upgraded to vivid on 2015-06-09 (4 days ago) mtime.conffile..etc.bumblebee.bumblebee.conf: 2015-06-14T00:53:00.911443 mtime.conffile..etc.bumblebee.xorg.conf.nouveau: 2015-06-09T20:38:24.773993 mtime.conffile..etc.bumblebee.xorg.conf.nvidia: 2015-06-14T00:43:34.468919 --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 InstallationDate: Installed on 2013-10-17 (771 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) NonfreeKernelModules: nvidia Package: bumblebee 3.2.1-9 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=de_DE.UTF-8 SHELL=/bin/bash Tags: wily Uname: Linux 4.3.0-040300-generic x86_64 UpgradeStatus: Upgraded to wily on 2015-11-19 (8 days ago) UserGroups: adm bumblebee cdrom dip lpadmin netdev plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.bumblebee.bumblebee.conf: 2015-11-28T03:22:03.840889 mtime.conffile..etc.bumblebee.xorg.conf.nouveau: 2015-11-19T05:20:30.927814 mtime.conffile..etc.bumblebee.xorg.conf.nvidia: 2015-11-28T03:22:29.796691 Specifying a `KernelDriver` containing `_` or `-` in the `nvidia` driver section of `/etc/bumblebee/bumblebee.conf` causes `optirun bash` to fail with     [ 533.997079] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) Failed to load module "nvidia352" (module does not exist, 0)     [ 533.997196] [ERROR]Aborting because fallback start is disabled. if `nvidia_352` or `nvidia-352` has been specified. Futhermore this is impossible to debug without massive loss of sanity if `optirun` doesn't tell where configuration options have been picked up from if a critical error occured. `grep -r 'nvidia352' /etc/bumblebee/` returns no result. The specified module exists as shown by `modinfo`: $ modinfo nvidia_352 filename: /lib/modules/4.1.0-040100rc7-generic/updates/dkms/nvidia_352.ko alias: char-major-195-* version: 352.09 supported: external license: NVIDIA alias: pci:v000010DEd00000E00sv*sd*bc04sc80i00* alias: pci:v000010DEd*sv*sd*bc03sc02i00* alias: pci:v000010DEd*sv*sd*bc03sc00i00* depends: drm vermagic: 4.1.0-040100rc7-generic SMP mod_unload modversions parm: NVreg_Mobile:int parm: NVreg_ResmanDebugLevel:int parm: NVreg_RmLogonRC:int parm: NVreg_ModifyDeviceFiles:int parm: NVreg_DeviceFileUID:int parm: NVreg_DeviceFileGID:int parm: NVreg_DeviceFileMode:int parm: NVreg_UpdateMemoryTypes:int parm: NVreg_InitializeSystemMemoryAllocations:int parm: NVreg_UsePageAttributeTable:int parm: NVreg_MapRegistersEarly:int parm: NVreg_RegisterForACPIEvents:int parm: NVreg_CheckPCIConfigSpace:int parm: NVreg_EnablePCIeGen3:int parm: NVreg_EnableMSI:int parm: NVreg_MemoryPoolSize:int parm: NVreg_RegistryDwords:charp parm: NVreg_RmMsg:charp parm: NVreg_AssignGpus:charp ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bumblebee 3.2.1-7 Uname: Linux 4.1.0-040100rc7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 14 00:53:57 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-06-08 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron:  TERM=xterm  PATH=(custom, no user)  XDG_RUNTIME_DIR=<set>  LANG=de_DE.UTF-8  SHELL=/bin/bash SourcePackage: bumblebee UpgradeStatus: Upgraded to vivid on 2015-06-09 (4 days ago) mtime.conffile..etc.bumblebee.bumblebee.conf: 2015-06-14T00:53:00.911443 mtime.conffile..etc.bumblebee.xorg.conf.nouveau: 2015-06-09T20:38:24.773993 mtime.conffile..etc.bumblebee.xorg.conf.nvidia: 2015-06-14T00:43:34.468919 --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 InstallationDate: Installed on 2013-10-17 (771 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) NonfreeKernelModules: nvidia Package: bumblebee 3.2.1-9 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=de_DE.UTF-8 SHELL=/bin/bash Tags: wily Uname: Linux 4.3.0-040300-generic x86_64 UpgradeStatus: Upgraded to wily on 2015-11-19 (8 days ago) UserGroups: adm bumblebee cdrom dip lpadmin netdev plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.bumblebee.bumblebee.conf: 2015-11-28T03:22:03.840889 mtime.conffile..etc.bumblebee.xorg.conf.nouveau: 2015-11-19T05:20:30.927814 mtime.conffile..etc.bumblebee.xorg.conf.nvidia: 2015-11-28T03:22:29.796691 --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2015-12-12 (330 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) NonfreeKernelModules: nvidia openafs zfs zunicode zcommon znvpair zavl Package: bumblebee 3.2.1-13 PackageArchitecture: amd64 Tags: third-party-packages yakkety Uname: Linux 4.8.6-040806-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-17 (20 days ago) UserGroups: adm autopilot bumblebee cdrom dip libvirtd lp lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.bumblebee.bumblebee.conf: 2016-11-07T03:22:46.645461 mtime.conffile..etc.bumblebee.xorg.conf.nouveau: 2016-11-07T00:15:19.318563 mtime.conffile..etc.bumblebee.xorg.conf.nvidia: 2016-11-07T03:33:30.953877
2016-11-07 02:35:34 Karl-Philipp Richter attachment added Dependencies.txt https://bugs.launchpad.net/bugs/1464928/+attachment/4773795/+files/Dependencies.txt
2016-11-07 02:35:37 Karl-Philipp Richter attachment added JournalErrors.txt https://bugs.launchpad.net/bugs/1464928/+attachment/4773796/+files/JournalErrors.txt
2016-11-07 02:35:38 Karl-Philipp Richter attachment added ProcEnviron.txt https://bugs.launchpad.net/bugs/1464928/+attachment/4773797/+files/ProcEnviron.txt
2016-11-07 02:35:39 Karl-Philipp Richter attachment added modified.conffile..etc.bumblebee.bumblebee.conf.txt https://bugs.launchpad.net/bugs/1464928/+attachment/4773798/+files/modified.conffile..etc.bumblebee.bumblebee.conf.txt
2016-11-07 02:35:40 Karl-Philipp Richter attachment added modified.conffile..etc.bumblebee.xorg.conf.nouveau.txt https://bugs.launchpad.net/bugs/1464928/+attachment/4773799/+files/modified.conffile..etc.bumblebee.xorg.conf.nouveau.txt
2016-11-07 02:35:41 Karl-Philipp Richter attachment added modified.conffile..etc.bumblebee.xorg.conf.nvidia.txt https://bugs.launchpad.net/bugs/1464928/+attachment/4773800/+files/modified.conffile..etc.bumblebee.xorg.conf.nvidia.txt
2017-05-25 16:13:54 Karl-Philipp Richter bug watch added https://github.com/Bumblebee-Project/Bumblebee/issues/872
2017-05-25 16:13:54 Karl-Philipp Richter bug task added the-bumblebee-project
2017-05-25 16:54:39 Bug Watch Updater the-bumblebee-project: status Unknown New