desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #94939
[Bug 1376966] Re: gpu-manager treats all files in /etc/modprobe.d as config files
Looking at the description:
After some debugging I fond that this was done by gpu-manager, because
it incorrectly believes that my nvidia module is blacklisted. gpu-
manager.log contained "Is nvidia blacklisted? yes".
More debugging determined that this was happening because I have a several years old file named:
/etc/modprobe.d/blacklist.dpkg-old
which among other things contain the line "blacklist nvidia".
It looks to me like the test case would involve creating a file name
blacklist.dpkg-old in /etc/modprobe.d and installing the buggy version
of ubuntu-drivers-common and reviewing gpu-manager.log file for "Is
nvidida blacklisted? yes". With the version of the package from
-proposed you should not see that line in the gpu-manager.log file.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1376966
Title:
gpu-manager treats all files in /etc/modprobe.d as config files
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common source package in Trusty:
Fix Committed
Bug description:
My media center computer have a single nvidia GPU connected to a TV,
and have for many years been happily using the nvidia driver.
Unfortunately the recent upgrade to version 1:0.2.91.7 broke X.
Starting lightdm would fail, delete my xorg.conf and redirect libgl
symlinks to mesa.
After some debugging I fond that this was done by gpu-manager, because
it incorrectly believes that my nvidia module is blacklisted. gpu-
manager.log contained "Is nvidia blacklisted? yes".
More debugging determined that this was happening because I have a several years old file named:
/etc/modprobe.d/blacklist.dpkg-old
which among other things contain the line "blacklist nvidia".
However that is _not_ a modprobe config file. modprobe only uses files
with a .conf extension. (See the man page modprobe.d(5)).
Unfortunately gpu-manager does not have this restriction and looks in
all files in /etc/modprobe.d by running:
grep -G "blacklist.*nvidia[[:space:]]*$" /etc/modprobe.d/*
I could work-around the bug by removing the .dpkg-old file. However this will likely break other machines as well. I found two bugs 1373968 and 1374871 about X not working after installing the latest update. However they does not contain enough information to determine if they are duplicates of this bug or not.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1376966/+subscriptions
References