[Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
The Optimus issue most definitely must be filed as a separate bug (and comments on it go there). In order for a bug tracking system like this to work well, the technical scope of a bug must be narrowly defined; that's software development good practice 101. If the scope of a bug is vague or allowed to creep, no developer will touch the assign to me button with a 10-foot pole. In fact, this is exactly the reason why lp:1268257 has been sitting there for 18 months without any progress; the error description consisted of a *symptom* that could have a very large number of causes, so nobody was willing to go look into all of them. It was only after it was realized that lp:1431753 was the cause in the vast majority of cases that things started moving. In this context, kudos go to teo1978 for forcing the breakthrough by finding and applying a workaround for lp:1450251 . You guys have to forgive him for being a bit testy. Even the most patient person would throw a fit after waiting 18 moths for a trivial-looking fix to a bug that made thousands of users lose their GUI every few weeks, and then getting another show-stopping problem when applying that fix! Anyhow, the scope of *this* bug is the DKMS violation, which is fully fixed. From a *technical* perspective, the Optimus issue is an entirely unrelated bug. The fact that it's triggered by the present fix does not matter a this stage. slightly offtopicJust to set the record straight (you might want to use part of this in the description of the new bug): there are (at least) 2 separate ways to get Optimus support working in Ubuntu: (1) nvidia-prime : allows you to switch between running the whole desktop on Intel or Nvidia. The choice is made in the nvidia control panel and takes effect when logging out and back in. It's far from a perfect solution but at least it's easy to use. (2) bumblebee : allows you to specify on which card to run a given program at the command-line (or by editing the application launcher). I personally prefer this route because it gives me more granular control and doesn't force you to log out, but novice users may find it cumbersome. It appears that the configuration files of the packages that are involved in both (1) and (2) did not anticipate drivers newer than 331 to be used with 14.04, resulting in a blank screen upon login. The fix for (1) is in Anna's link: http://vxlabs.com/2015/02/05/solving-the-ubuntu-14-04-nvidia-346-nvidia-prime-black-screen-issue/ . As for (2), see my post: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340-updates/+bug/1431753/comments/62 . Now, if canonical was really serious about LTS, they would have a sufficiently large and professional team working on this. The person responsible for the nvidia driver would have remembered to contacted the people responsible for the gpu-manager and bumblebee packages, or at the very least have been reminded of it by my post, which I made when the fix was still in the proposed stage. The actual release of the fix would have been delayed while those other developers would be updating the configuration files of their respective packages (that's, like, less than an hour of work), and the updates would need another round of testing. After 18 months, nobody would have cared about those few days, and it would have prevented the present outpouring of disappointment./slightly offtopic very much offtopic rantAnd yes, there is a lesson to be learned here. It is becoming increasingly clear that Ubuntu Mobile, much like Windows Mobile, will never compete with the 800-pound gorillas Android and iOS on the mobile platform, and all efforts in that direction are an utter waste. Also, thinking that the desktop will go away is naive; desktops will continue being the platform of choice in the workplace (as well as the enthusiast's basement) for the foreseeable future. Therefore, Canonical should go back to doing what it did best: pushing Linux into the desktop market. And since IT managers generally don't want to upgrade all systems every 6 months. LTS support deserves far more love than it's currently getting. Windows 10's retreat to the desktop metaphor was largely driven by the realization that the desktop market is firmly shifting into the domain of professionals (and enthusiasts), who are not well-served with bells and whistles, frequent breakage and a dumbed-down interface. How long will it take until Shuttleworth gets the memo?/very much offtopic rant -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in
[Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Sezer, you're not going to believe this, but the issue you're having with steam has nothing to to with the nvidia driver, but is caused by a completely unrelated kernel bug that just happened to occur at the same time people started testing the fix for the nvidia driver; see lp:1479093 . The fix for the kernel bug is already released, so just upgrade your kernel yet again, and your steam problem will go away. I have to add that I also got confused by wine not working anymore after applying the nvidia patch (and upgrading the kernel for the first time in many months in order to test it), and it took me almost 2 hours to figure out the problem was unrelated. This whole affair is turning into one of the most frustrating experiences I've ever had with Ubuntu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-340-updates source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-346 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-346-updates source package in Trusty: Fix Committed Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Mat, I am happy you got past your blank-screen problem, even though the things mentioned in my previous post may or may not have played a role in solving it. To be perfectly clear toward other people who come across this discussion, the points (1)-(4) in my previous post DO NOT represent a step-by-step solution for getting a graphical desktop back after running a routine kernel upgrade. They are a few things *I* tried for the specific case of APPLYING THE DRIVERS FROM TRUSTY-PROPOSED TO AN EXISTING BUMBLEBEE SETUP. And it's quite likely some of them are not useful or even harmful. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-340-updates source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-346 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-346-updates source package in Trusty: Fix Committed Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file
For anyone who didn't get the message, fixed versions of the the 440 driver (with legacy GPU support) and the 446 driver (which only supports relatively recent GPUs) are now available in the official trusty- proposed repository. A few people (including me) have reported trying them with the 3.13 kernel and getting encouraging results. So, for those of you who cannot wait to have a fix up and running, try trusty-proposed ; for the rest, it looks like the long wait for a fix in the default distribution is almost over. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file Status in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-331-updates package in Ubuntu: In Progress Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Bug description: 2015-06-16 TJ: I've published a possibly fixed package for Trusty to my PPA at: https://launchpad.net/~tj/+archive/ubuntu/nvidia Please test and report back if that fixes the issue. If it does I can attach the fixed branch to bug #1431753 where the other release fixes are being tracked. --- original bug report follows **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for LUG in your area). Link back to this bug for clarity. --- This seems to fix it (at least for one version upgrade) for many people $ sudo dpkg-reconfigure nvidia-331 after that... $ sudo dpkg-reconfigure nvidia-331-uvm (some users may be on the versions of these packages suffixed with -updates ) Update 2015-05-23: As of the recent kernel update (3.13.0-53), the above two commands followed by a reboot may not fix it. Instead: $ sudo apt-get install --reinstall nvidia-331 nvidia-331-uvm followed by a reboot. --- **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is solved - see https://askubuntu.com/questions/576523 for details. **If you want to comment:** Please consider if you have something meaningful to contribute to the 2500+ people who will get an email. **If you are an Ubuntu developer:** thanks for looking into this! :D Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.13.0-2-generic Date: Sun Jan 12 01:28:35 2014 InstallationDate: Installed on 2013-11-03 (69 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageVersion: 331.20-0ubuntu9 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1268257/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Fix confirmed on 2 very different machines both running Ubuntu 14.04 Trusty with the 3.13 kernel. Detailed notes: AMD workstation with only a discrete nvidia GPU (nothing else) Synaptic complained about conflicts when selecting updated driver from trusty-proposed (something involving nvidia-libopencl1-* vs nvidia-opencl-icd-* IIRC). Installing through aptitude worked better. No further issues when rebooting, updating the kernel and rebooting again. Intel laptop running bumblebee == Blank screen after updating. Solutions tried: (1) starting the kernel with nogpumanager and removing /etc/X11/xorg.conf generated by gpu-manager (2) removing the newly created file /etc/prime-discrete (3) sudo sed -i 's/-current/-346-updates/g' /etc/bumblebee/bumblebee.conf (4) adding lines for 340 and 346 to /etc/modprobe.d/bumblebee.conf Applying all of the above fixed the problem, and (1)-(3) without (4) didn't, so it's very likely that (4) is necessary. What I cannot tell is which of (1)-(3) are also necessary and which are optional.(*) Bottom line is that special precautions should be taken to prevent bumblebee from breaking when rolling this out. (*) I could of course figure that out by reverting the changes one-by- one, but this bug already robbed me of an outrageous amount of my time and all of my goodwill, so you're on your own. Thanks a lot for finally fixing it, though. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-340-updates source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-346 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-346-updates source package in Trusty: Fix Committed Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file
No, this is *not* fixed for 331 and 331-updates; in fact, nothing has changed. The fix released status presumably was set by yet another inattentive user who landed onto this Launchpad page after getting a whoopsie error. Unfortunately, the status cannot easily be reverted to triaged because of what I feel is a shortcoming in Launchpad. There is some good news, though: Alberto Milone over at lp:1431753 (which describes the actual *source* of the problem) hinted at intending to provide a fix for 14.04. Unfortunately, he hasn't provided any updates, details or time frame in the last 3 weeks. So, those of you who have not become completely embittered by Canonical's unforgivable lack of attention to this atrocious bug in their Less Than Stellar (LTS) line, PLEASE head over to lp:1431753 and politely draw their attention to the fact that a massive number of users are very badly affected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file Status in NVIDIA Drivers Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Bug description: **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for LUG in your area). Link back to this bug for clarity. --- This seems to fix it (at least for one version upgrade) for many people $ sudo dpkg-reconfigure nvidia-331 after that... $ sudo dpkg-reconfigure nvidia-331-uvm (some users may be on the versions of these packages suffixed with -updates ) Update 2015-05-23: As of the recent kernel update (3.13.0-53), the above two commands followed by a reboot may not fix it. Instead: $ sudo apt-get install --reinstall nvidia-331 nvidia-331-uvm followed by a reboot. --- **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is solved - see https://askubuntu.com/questions/576523 for details. **If you want to comment:** Please consider if you have something meaningful to contribute to the 2500+ people who will get an email. **If you are an Ubuntu developer:** thanks for looking into this! :D Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.13.0-2-generic Date: Sun Jan 12 01:28:35 2014 InstallationDate: Installed on 2013-11-03 (69 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageVersion: 331.20-0ubuntu9 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
*bump* -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-340-updates source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346-updates source package in Trusty: Confirmed Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Nice! Will this work with the 3.13 kernel in 14.04 ? Also, do you have any idea when it will be available to end-users? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-340-updates source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346-updates source package in Trusty: Confirmed Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Alberto, thank you sooo much, that is great news. Especially since there seems to be another wave of bitter comments and confusion on lp:1268257 . Two questions: - Am I understanding correctly that you'll fix the problem for the 331 driver AND that we'll have the option of using the 340 or 346 driver with the 3.13 kernel in 14.04 ? (For me personally, _either_ solution would work. Having newer drivers is always nice, but there might hypothetically be people with really old hardware who require the old driver.) - Do you have any idea when either solution will be available to end-users? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-340-updates source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346-updates source package in Trusty: Confirmed Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file
@Adam Koczur (sbv): nice, that is a step in the right direction! However, I have to point out that pretty much everyone who is affected by this bug is running the 3.13 kernel that comes with Trusty; those who are running newer (non-LTS) kernels all have newer nvidia drivers (except the ones with legacy graphic cards, but that's a minority; nvidia's legacy support goes quite a way back...) So, do you think it would be safe to test your ppa with the 3.13 kernel, or is that not expected to work? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file Status in NVIDIA Drivers Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Triaged Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Bug description: **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for LUG in your area). Link back to this bug for clarity. --- This seems to fix it (at least for one version upgrade) for many people $ sudo dpkg-reconfigure nvidia-331 after that... $ sudo dpkg-reconfigure nvidia-331-uvm (some users may be on the versions of these packages suffixed with -updates ) --- **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is solved - see https://askubuntu.com/questions/576523 for details. **If you want to comment:** Please consider if you have something meaningful to contribute to the 2500+ people who will get an email. **If you are an Ubuntu developer:** thanks for looking into this! :D Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.13.0-2-generic Date: Sun Jan 12 01:28:35 2014 InstallationDate: Installed on 2013-11-03 (69 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageVersion: 331.20-0ubuntu9 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file
@Adam Koczur (sbv): you do indeed appear to have the wrong bug report; the bug we're (effectively) talking about *here* is also triggered by 331.113-0ubuntu0.0.4 from nvidia-331-updates (it's what I'm running) and is described more accurately at lp:1431753 . In case you wonder why the heck this is not a duplicate, see lp:1450251 . I don't know whether I have to laugh or cry. @Robert Dinse (nanook): you probably should take the 3.19 discussion to the relevant LP bug report - @Adam Koczur (sbv), can you please povide an lp: link? There is far too much offtopic talk on this one as it is already. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file Status in NVIDIA Drivers Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Triaged Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Bug description: **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for LUG in your area). Link back to this bug for clarity. --- This seems to fix it (at least for one version upgrade) for many people $ sudo dpkg-reconfigure nvidia-331 after that... $ sudo dpkg-reconfigure nvidia-331-uvm (some users may be on the versions of these packages suffixed with -updates ) --- **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is solved - see https://askubuntu.com/questions/576523 for details. **If you want to comment:** Please consider if you have something meaningful to contribute to the 2500+ people who will get an email. **If you are an Ubuntu developer:** thanks for looking into this! :D Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.13.0-2-generic Date: Sun Jan 12 01:28:35 2014 InstallationDate: Installed on 2013-11-03 (69 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageVersion: 331.20-0ubuntu9 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Dear Alberto and others, Could you please please backport this fix to the 331 driver, which is the most recent one available for 14.04 LTS (Trusty)? Or at the very least explain why this might not be as trivial as it sounds? This bug impacts a massive amount of Trusty users, and failing to get a graphical interface every time the kernel is upgraded is quite high-profile; a lot of people are abandoning Ubuntu altogether for it. Our whole workplace may do so soon because one of the programs we use professionally requires the proprietary Nvidia driver and our support people cannot afford the time commitment to have everyone use the non-LTS branches. I also feel I need to point out that the users affected and bug heat of this report ( lp:1431753 ) are misleadingly low. Most of the users who trigger this bug land at lp:1268257 . If you look at the stats of *that* bug and all the recent comments, the whole affair starts to look like a trainwreck. We tried to make lp:1268257 a duplicate of this bug ( lp:1431753 ), which would presumably bump the latter to the top of the priority list, but were prevented from doing so by a bug in Launchpad itself ( lp:1450251 ). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-340-updates source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346-updates source package in Trusty: Confirmed Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file
@Bill Turner, wb4alm (wb4alm): FYI, Triaged means that a bug supervisor has determined that the bug report contains all necessary information to start working on it. This is in my opinion the (only) correct status for nvidia-graphics-drivers-331 and nvidia-graphics- drivers-331-updates (note that some of the necessary information is in lp:1431753 ). See also https://help.launchpad.net/Bugs/Statuses . @Daniel van Vugt (vanvugt): thank you, thank you so much!!! You might have saved my sanity there (depending on whether the issue will actually get fixed in a reasonable time span). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file Status in NVIDIA Drivers Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Triaged Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Bug description: **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for LUG in your area). Link back to this bug for clarity. --- This seems to fix it (at least for one version upgrade) for many people $ sudo dpkg-reconfigure nvidia-331 after that... $ sudo dpkg-reconfigure nvidia-331-uvm (some users may be on the versions of these packages suffixed with -updates ) --- **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is solved - see https://askubuntu.com/questions/576523 for details. **If you want to comment:** Please consider if you have something meaningful to contribute to the 2500+ people who will get an email. **If you are an Ubuntu developer:** thanks for looking into this! :D Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.13.0-2-generic Date: Sun Jan 12 01:28:35 2014 InstallationDate: Installed on 2013-11-03 (69 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageVersion: 331.20-0ubuntu9 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file
@ Sébastien BOUISSET (sbouisset): your're using the non-LTS branch of Ubuntu. I've been repeating ad nauseam during the last few weeks that the issue is NOT FIXED in the LTS branch, which uses the 331 driver, and is popular with professional users. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file Status in NVIDIA Drivers Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Bug description: **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for LUG in your area). Link back to this bug for clarity. --- This seems to fix it (at least for one version upgrade) for many people $ sudo dpkg-reconfigure nvidia-331 after that... $ sudo dpkg-reconfigure nvidia-331-uvm (some users may be on the versions of these packages suffixed with -updates ) --- **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is solved - see https://askubuntu.com/questions/576523 for details. **If you want to comment:** Please consider if you have something meaningful to contribute to the 2500+ people who will get an email. **If you are an Ubuntu developer:** thanks for looking into this! :D Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.13.0-2-generic Date: Sun Jan 12 01:28:35 2014 InstallationDate: Installed on 2013-11-03 (69 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageVersion: 331.20-0ubuntu9 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file
This is my current Hanlon-compliant(*) theory as to why the fix is not backported: - Anyone looking up this bug will land at the top of the page, where the status is displayed. A small percentage will make random changes to the status by lack of attention or understanding. - This bug report is visited by huge numbers of people, so even though the percentage of inattentives is small, we're seeing lots of random status changes in its activity log. - The problem is that some status changes are irrevocable. Specifically, shortly after the fix was released for the 340 and 346 drivers, people mistakenly changed the status for the 331 drivers and the bug as a whole to fix released. This made it fall off the devs' radar, and there doesn't seem to be a way to roll back the status. In my opinion, this is stupid and should be filed as a bug against Launchpad itself. My current plan to work around this problem is to mark this bug ( lp:1268257 ) a duplicate of lp:1431753 , which - has the status set correctly, including a target for Trusty, - has a more knowledgeable description of the root cause of the problem and how to fix it, - is frequented by people who can actually fix it, - suffers from a low bug heat, which will change dramatically if my plan succeeds, - does not suffer from random status changes. However, a new problem surfaced: trying to set the dupe in Launchpad invariably gives a timeout error (Error ID: OOPS-f524378385a3a281890972cc17c96962 OOPS-bb927226a672db21659a9f400adc4757 etc...) I speculate this is due to the huge size of this bug in terms of followers, duplicates, people affected and comments. Whatever be the cause, it's yet another bug to be filed against Launchpad itself. Needless to say, I'm getting deeply disillusioned with Ubuntu, Canonical and its bug fixing process... (*) My alternative theories that are not compliant with Hanlon's razor are probably not appropriate for this venue. :-P -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file Status in NVIDIA Drivers Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Bug description: **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for LUG in your area). Link back to this bug for clarity. --- This seems to fix it (at least for one version upgrade) for many people $ sudo dpkg-reconfigure nvidia-331 after that... $ sudo dpkg-reconfigure nvidia-331-uvm (some users may be on the versions of these packages suffixed with -updates ) --- **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is solved - see https://askubuntu.com/questions/576523 for details. **If you want to comment:** Please consider if you have something meaningful to contribute to the 2500+ people who will get an email. **If you are an Ubuntu developer:** thanks for looking into this! :D Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.13.0-2-generic Date: Sun Jan 12 01:28:35 2014 InstallationDate: Installed on 2013-11-03 (69 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageVersion: 331.20-0ubuntu9 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file
Oh come on, this is completely wrong! This bug is *NOT * fixed for the 331 driver (and also not for NVIDIA Drivers Ubuntu because 331 is the most recent driver available in 14.04 LTS (Trusty)). Why doesn't launchpad allow to correct this mistake by setting it back the Confirmed??? If the devs are under the mistaken impression it is fixed, it will never get their attention. What does it take to rectify this? Opening yet another new bug and marking this one as a duplicate? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file Status in NVIDIA Drivers Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Bug description: **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for LUG in your area). Link back to this bug for clarity. --- This seems to fix it (at least for one version upgrade) for many people $ sudo dpkg-reconfigure nvidia-331 after that... $ sudo dpkg-reconfigure nvidia-331-uvm (some users may be on the versions of these packages suffixed with -updates ) --- **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is solved - see https://askubuntu.com/questions/576523 for details. **If you want to comment:** Please consider if you have something meaningful to contribute to the 2500+ people who will get an email. **If you are an Ubuntu developer:** thanks for looking into this! :D Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.13.0-2-generic Date: Sun Jan 12 01:28:35 2014 InstallationDate: Installed on 2013-11-03 (69 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageVersion: 331.20-0ubuntu9 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file
The fact that there are so many accidental edits to the status of this bug seems to indicate it's getting large numbers of views. Canonical, your LTS user base is bleeding. For pity's sake, make it stop. Talking about accidental edits, can someone please, please set the status for NVIDIA Drivers Ubuntu back to Confirmed? See my message #259 ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file Status in NVIDIA Drivers Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Bug description: **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for LUG in your area). Link back to this bug for clarity. --- This seems to fix it (at least for one version upgrade) for many people $ sudo dpkg-reconfigure nvidia-331 after that... $ sudo dpkg-reconfigure nvidia-331-uvm (some users may be on the versions of these packages suffixed with -updates ) --- **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is solved - see https://askubuntu.com/questions/576523 for details. **If you want to comment:** Please consider if you have something meaningful to contribute to the 2500+ people who will get an email. **If you are an Ubuntu developer:** thanks for looking into this! :D Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.13.0-2-generic Date: Sun Jan 12 01:28:35 2014 InstallationDate: Installed on 2013-11-03 (69 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageVersion: 331.20-0ubuntu9 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file
** Changed in: nvidia-drivers-ubuntu Assignee: done (mnmarkonissinen) = (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file Status in NVIDIA Drivers Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Bug description: **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for LUG in your area). Link back to this bug for clarity. --- This seems to fix it (at least for one version upgrade) for many people $ sudo dpkg-reconfigure nvidia-331 after that... $ sudo dpkg-reconfigure nvidia-331-uvm (some users may be on the versions of these packages suffixed with -updates ) --- **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is solved - see https://askubuntu.com/questions/576523 for details. **If you want to comment:** Please consider if you have something meaningful to contribute to the 2500+ people who will get an email. **If you are an Ubuntu developer:** thanks for looking into this! :D Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.13.0-2-generic Date: Sun Jan 12 01:28:35 2014 InstallationDate: Installed on 2013-11-03 (69 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageVersion: 331.20-0ubuntu9 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file
@stephen (stephen-puttick) : I don't think that's needed; it is my understanding from lp:1431753 that this bug is already fully characterized, and fixed for the 340 and 346 drivers in Utopic and Vivid. Furthermore, the fact that the fix appears to be performed at the level of the metadata strongly suggests that it would be absolutely trivial to apply the same fix to the 331 drivers in (un)Trust(worth)y. Canonical might have their reasons for not backporting the fix to their LTS release, but as long as the only noise we get from them is crickets chirping, it is hardly surprising that the community is starting to ask questions about their motives and/or professionalism... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file Status in NVIDIA Drivers Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Bug description: **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for LUG in your area). Link back to this bug for clarity. --- This seems to fix it (at least for one version upgrade) for many people $ sudo dpkg-reconfigure nvidia-331 after that... $ sudo dpkg-reconfigure nvidia-331-uvm (some users may be on the versions of these packages suffixed with -updates ) --- **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is solved - see https://askubuntu.com/questions/576523 for details. **If you want to comment:** Please consider if you have something meaningful to contribute to the 2500+ people who will get an email. **If you are an Ubuntu developer:** thanks for looking into this! :D Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.13.0-2-generic Date: Sun Jan 12 01:28:35 2014 InstallationDate: Installed on 2013-11-03 (69 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageVersion: 331.20-0ubuntu9 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file
You might have meant to say 14.04. Which is still supported till March 1019. That's a very long time for Canonical to claim to be supporting something that's so broken... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file Status in NVIDIA Drivers Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Bug description: **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for LUG in your area). Link back to this bug for clarity. --- This seems to fix it (at least for one version upgrade) for many people $ sudo dpkg-reconfigure nvidia-331 after that... $ sudo dpkg-reconfigure nvidia-331-uvm (some users may be on the versions of these packages suffixed with -updates ) --- **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is solved - see https://askubuntu.com/questions/576523 for details. **If you want to comment:** Please consider if you have something meaningful to contribute to the 2500+ people who will get an email. **If you are an Ubuntu developer:** thanks for looking into this! :D Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.13.0-2-generic Date: Sun Jan 12 01:28:35 2014 InstallationDate: Installed on 2013-11-03 (69 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageVersion: 331.20-0ubuntu9 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file
@ awol (awol99) : I'll do you one better. At my workplace, we just started the process of gradually upgrading all our machines from 12.04 Precise to 14.04 Trusty. After starting with a few, we've hit this bug. Yesterday, I had a discussion about it with the person responsible for software maintenance, and it looks like we'll be upgrading the whole shop to Debian instead. It's not just the direct annoyance caused by this bug (though it is rather serious given that one of the programs we use professionally requires the proprietary Nvidia driver), but more importantly what Canonical's response (or rater lack thereof) implies for our future level of support. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file Status in NVIDIA Drivers Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Bug description: **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for LUG in your area). Link back to this bug for clarity. --- This seems to fix it (at least for one version upgrade) for many people $ sudo dpkg-reconfigure nvidia-331 after that... $ sudo dpkg-reconfigure nvidia-331-uvm (some users may be on the versions of these packages suffixed with -updates ) --- **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is solved - see https://askubuntu.com/questions/576523 for details. **If you want to comment:** Please consider if you have something meaningful to contribute to the 2500+ people who will get an email. **If you are an Ubuntu developer:** thanks for looking into this! :D Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.13.0-2-generic Date: Sun Jan 12 01:28:35 2014 InstallationDate: Installed on 2013-11-03 (69 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageVersion: 331.20-0ubuntu9 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file
As long as the current LTS (i.e. 331) drivers are not fixed, I think it is wrong to set the status for nvidia-drivers-ubuntu to Fix Released. Can someone with the necessary permissions please undo the status change by royalsabz (mehrshad-5843) ? And set the importance to High, while you're at it? This is a really important high-impact bug that should be as high as possible on the agenda until it's completely fixed for all currently supported releases. In this light, the apparent casual lack of attention from Canonical's side is beyond my comprehension. I can only speculate they're too busy making Vivid attractive enough to lure in new users, and are forgetting about keeping long-time users. To the people who think that's the right thing to do: please try to weigh the potential harm caused by delaying Vivid a day or so against the actual harm of having thousands of long-time users' desktops breaking en masse because of running seemingly-innocuous kernel updates... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file Status in NVIDIA Drivers Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Bug description: **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for LUG in your area). Link back to this bug for clarity. --- This seems to fix it (at least for one version upgrade) for many people $ sudo dpkg-reconfigure nvidia-331 after that... $ sudo dpkg-reconfigure nvidia-331-uvm (some users may be on the versions of these packages suffixed with -updates ) --- **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is solved - see https://askubuntu.com/questions/576523 for details. **If you want to comment:** Please consider if you have something meaningful to contribute to the 2500+ people who will get an email. **If you are an Ubuntu developer:** thanks for looking into this! :D Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.13.0-2-generic Date: Sun Jan 12 01:28:35 2014 InstallationDate: Installed on 2013-11-03 (69 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageVersion: 331.20-0ubuntu9 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file
Can someone please, please apply the fix that worked for 346 and 340 to 331 also? Or at the very least explain why this might not be as trivial as it sounds? As I pointed out in lp:1431753, 331 is still the most recent driver supported by the current LTS release. This is a bug that affects thousands of users, not all of whom will be willing/skilled to upgrade their kernels (and then upgrade them again and again every time short-term support runs out). This bug has impacted us badly, and I'm on the verge of stopping to recommend people to use Ubuntu LTS in professional settings, as I feel Canonical is betraying its LTS users big time here. And I'm not the only one losing my patience; see for instance comment #249... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file Status in NVIDIA Drivers Ubuntu: Confirmed Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Bug description: **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for LUG in your area). Link back to this bug for clarity. --- This seems to fix it (at least for one version upgrade) for many people $ sudo dpkg-reconfigure nvidia-331 after that... $ sudo dpkg-reconfigure nvidia-331-uvm (some users may be on the versions of these packages suffixed with -updates ) --- **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is solved - see https://askubuntu.com/questions/576523 for details. **If you want to comment:** Please consider if you have something meaningful to contribute to the 2500+ people who will get an email. **If you are an Ubuntu developer:** thanks for looking into this! :D Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.13.0-2-generic Date: Sun Jan 12 01:28:35 2014 InstallationDate: Installed on 2013-11-03 (69 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageVersion: 331.20-0ubuntu9 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Sorry, but 331 is still the most recent driver supported by the LTS release. While LTS doesn't seem to mean much to Canonical anymore, at least try to keep up the appearance. Especially for a bug that affects thousands of users, not all of whom will be willing/skilled to upgrade their kernels (and then upgrade them again and again every time short- term support runs out). ** Changed in: nvidia-graphics-drivers-331 (Ubuntu) Status: Invalid = Confirmed ** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu) Status: Invalid = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-340-updates source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346-updates source package in Trusty: Confirmed Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file
** Also affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file Status in NVIDIA Drivers Ubuntu: Confirmed Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Bug description: **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for LUG in your area). Link back to this bug for clarity. --- This seems to fix it (at least for one version upgrade) for many people $ sudo dpkg-reconfigure nvidia-331 after that... $ sudo dpkg-reconfigure nvidia-331-uvm (some users may be on the versions of these packages suffixed with -updates ) --- **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is solved - see https://askubuntu.com/questions/576523 for details. **If you want to comment:** Please consider if you have something meaningful to contribute to the 2500+ people who will get an email. **If you are an Ubuntu developer:** thanks for looking into this! :D Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.13.0-2-generic Date: Sun Jan 12 01:28:35 2014 InstallationDate: Installed on 2013-11-03 (69 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageVersion: 331.20-0ubuntu9 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file
The workaround in post #100 works at the level of the individual user, but it's a bit flawed in the sense that it will be undone every time the driver (not the kernel) is updated. In addition, if I understand the legal aspects correctly (IANAL), it does not qualify as a fix because Canonical cannot _distribute_ it without committing a license violation. And requiring the user to reinstall the driver after every kernel upgrade (post #101) *definitely* doesn't qualify as a fix. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file Status in NVIDIA Drivers Ubuntu: Confirmed Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Bug description: **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for LUG in your area). Link back to this bug for clarity. --- This seems to fix it (at least for one version upgrade) for many people $ sudo dpkg-reconfigure nvidia-331 after that... $ sudo dpkg-reconfigure nvidia-331-uvm (some users may be on the versions of these packages suffixed with -updates ) --- **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is solved - see https://askubuntu.com/questions/576523 for details. **If you want to comment:** Please consider if you have something meaningful to contribute to the 2500+ people who will get an email. **If you are an Ubuntu developer:** thanks for looking into this! :D Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.13.0-2-generic Date: Sun Jan 12 01:28:35 2014 InstallationDate: Installed on 2013-11-03 (69 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageVersion: 331.20-0ubuntu9 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1026356] Re: Bad validation on Scales box on Axis (chart properties)
** Bug watch added: freedesktop.org Bugzilla #49987 https://bugs.freedesktop.org/show_bug.cgi?id=49987 ** Also affects: df-libreoffice via https://bugs.freedesktop.org/show_bug.cgi?id=49987 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1026356 Title: Bad validation on Scales box on Axis (chart properties) Status in LibreOffice Productivity Suite: Unknown Status in “libreoffice” package in Ubuntu: Triaged Bug description: 1) lsb_release -rd Description: Ubuntu quantal (development branch) Release: 12.10 2) apt-cache policy libreoffice-calc libreoffice-calc: Installed: 1:3.6.1~rc2-1ubuntu5 Candidate: 1:3.6.1~rc2-1ubuntu5 Version table: *** 1:3.6.1~rc2-1ubuntu5 0 500 http://archive.ubuntu.com/ubuntu/ quantal/main i386 Packages 100 /var/lib/dpkg/status 3) What is expected to happen in a terminal: cd ~/Desktop wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1026356/+attachment/3227705/+files/GraphExample.ods localc --nologo GraphExample.ods 1. Double click on the graph 2. Right click on the y-axis Format Axis 3. Select the Scale tab 4. Uncheck Automatic for any of the values and try enter a number (You must change the value). 5. Click OK and it works. 4) What happens instead is you will see an error message stating that numbers are required. These are the steps I used to create the sample spreadsheet: 1. Create new spreadsheet 2. In column A write the numbers 1 to 5 on rows 1 to 5. 3. In column B write the numbers 1 to 5 on rows 1 to 5. 4. Select all the numbers Format Cells. 5. In the Numbers tab select Text under the list of Categories. 6. Click OK. 7. Click the chart button (with the numbers still selected) 8. Select an XY scatter graph (I've tested with points-only and points with lines) 9. Click Finish. You now have a graph that gives the error message when trying to change the scale. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libreoffice-calc 1:3.5.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Thu Jul 19 00:15:50 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1026356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 577658] Re: Bad validation on Scales box on Axis (chart properties)
*** This bug is a duplicate of bug 1026356 *** https://bugs.launchpad.net/bugs/1026356 ** This bug has been marked a duplicate of bug 1026356 Bad validation on Scales box on Axis (chart properties) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to openoffice.org in Ubuntu. https://bugs.launchpad.net/bugs/577658 Title: Bad validation on Scales box on Axis (chart properties) Status in “openoffice.org” package in Ubuntu: Won't Fix Bug description: Binary package hint: openoffice.org When already created a chart. Then double clic over an axis (for eg. Y axis) Y Axis box Scale tab Uncheck Automatic. THen if for example the automatic value was 12, you write AGAIN 12 (or any other number!) and always will say when clicing to OK: Numbers are required. Check your input. For better understanding, please see screenshot. ProblemType: Bug Architecture: i386 Date: Sat May 8 23:14:06 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) NonfreeKernelModules: nvidia Package: openoffice.org-core 1:3.1.1-5ubuntu1.1 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-20.58-generic SourcePackage: openoffice.org Uname: Linux 2.6.31-20-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/577658/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1026356] Re: Bad validation on Scales box on Axis (chart properties)
I linked this to upstream bug #49987 , but on second thought, upstream bug #57697 contains more recent and relevant info (they ought to mark one a duplicate of the other). https://www.libreoffice.org/bugzilla/show_bug.cgi?id=57697 Between the 2 upstream reports, it appears the bug occurs in 3.5.x and 3.6.x, but is fixed from 3.7 onwards. The upstream info also led me to find a workaround (for my specific instance, anyway): in the Format Axis dialog, one can click on the Numbers tab, uncheck source format (if it's checked), then choose Category: Number and Format: General. Then click OK and open the Format Axis dialog _again_, and then everything should work as expected. This workaround has been a life-saver for me as I'm on a machine I currently can't upgrade, and Ubuntu Precise is still supported till 2017... ** Bug watch added: LibreOffice Bugzilla #57697 https://www.libreoffice.org/bugzilla/show_bug.cgi?id=57697 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1026356 Title: Bad validation on Scales box on Axis (chart properties) Status in LibreOffice Productivity Suite: Unknown Status in “libreoffice” package in Ubuntu: Triaged Bug description: 1) lsb_release -rd Description: Ubuntu quantal (development branch) Release: 12.10 2) apt-cache policy libreoffice-calc libreoffice-calc: Installed: 1:3.6.1~rc2-1ubuntu5 Candidate: 1:3.6.1~rc2-1ubuntu5 Version table: *** 1:3.6.1~rc2-1ubuntu5 0 500 http://archive.ubuntu.com/ubuntu/ quantal/main i386 Packages 100 /var/lib/dpkg/status 3) What is expected to happen in a terminal: cd ~/Desktop wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1026356/+attachment/3227705/+files/GraphExample.ods localc --nologo GraphExample.ods 1. Double click on the graph 2. Right click on the y-axis Format Axis 3. Select the Scale tab 4. Uncheck Automatic for any of the values and try enter a number (You must change the value). 5. Click OK and it works. 4) What happens instead is you will see an error message stating that numbers are required. These are the steps I used to create the sample spreadsheet: 1. Create new spreadsheet 2. In column A write the numbers 1 to 5 on rows 1 to 5. 3. In column B write the numbers 1 to 5 on rows 1 to 5. 4. Select all the numbers Format Cells. 5. In the Numbers tab select Text under the list of Categories. 6. Click OK. 7. Click the chart button (with the numbers still selected) 8. Select an XY scatter graph (I've tested with points-only and points with lines) 9. Click Finish. You now have a graph that gives the error message when trying to change the scale. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libreoffice-calc 1:3.5.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Thu Jul 19 00:15:50 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1026356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1026356] Re: Bad validation on Scales box on Axis (chart properties)
Warning: launchpad's autogenerated hyperlinks in my previous post are wrong; the explicit https://; link is the only correct one. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1026356 Title: Bad validation on Scales box on Axis (chart properties) Status in LibreOffice Productivity Suite: Unknown Status in “libreoffice” package in Ubuntu: Triaged Bug description: 1) lsb_release -rd Description: Ubuntu quantal (development branch) Release: 12.10 2) apt-cache policy libreoffice-calc libreoffice-calc: Installed: 1:3.6.1~rc2-1ubuntu5 Candidate: 1:3.6.1~rc2-1ubuntu5 Version table: *** 1:3.6.1~rc2-1ubuntu5 0 500 http://archive.ubuntu.com/ubuntu/ quantal/main i386 Packages 100 /var/lib/dpkg/status 3) What is expected to happen in a terminal: cd ~/Desktop wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1026356/+attachment/3227705/+files/GraphExample.ods localc --nologo GraphExample.ods 1. Double click on the graph 2. Right click on the y-axis Format Axis 3. Select the Scale tab 4. Uncheck Automatic for any of the values and try enter a number (You must change the value). 5. Click OK and it works. 4) What happens instead is you will see an error message stating that numbers are required. These are the steps I used to create the sample spreadsheet: 1. Create new spreadsheet 2. In column A write the numbers 1 to 5 on rows 1 to 5. 3. In column B write the numbers 1 to 5 on rows 1 to 5. 4. Select all the numbers Format Cells. 5. In the Numbers tab select Text under the list of Categories. 6. Click OK. 7. Click the chart button (with the numbers still selected) 8. Select an XY scatter graph (I've tested with points-only and points with lines) 9. Click Finish. You now have a graph that gives the error message when trying to change the scale. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libreoffice-calc 1:3.5.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Thu Jul 19 00:15:50 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1026356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 40537] Re: [Upstream] [hardy] OpenOffice cannot write to NFS files
This is nothing short of appalling: - Issue still present in LibreOffice on Precise (LTS) - It's been 7 (seven) years - Currently, the workaround is to edit a file that gets overwritten with every update: http://ubuntuforums.org/showthread.php?t=1645957p=11891452#post11891452 The attached patch yields control over these essential flags back to /etc/libreoffice/soffice.sh , which is part of libreoffice-common but is ignored by /usr/lib/libreoffice/program/soffice (in the same package). It would be trivial for the package maintainer to apply this fix, with no loss of functionality whatsoever. People who are on NSFv3 simply would have to edit a flag in /etc/libreoffice/soffice.sh one time; since it's in /etc , later updates should leave it alone. Nothing changes for anyone else. ** Patch added: libreoffice.patch https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/40537/+attachment/3706957/+files/libreoffice.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to openoffice.org in Ubuntu. https://bugs.launchpad.net/bugs/40537 Title: [Upstream] [hardy] OpenOffice cannot write to NFS files Status in The OpenOffice.org Suite: Confirmed Status in “openoffice.org” package in Ubuntu: Fix Released Status in “openoffice.org” package in Debian: Fix Released Bug description: SOLUTION: 1. Use NFSv4 if possible 2. Install nfs-common package if not installed == Opening a file within an NFS mounted filesystem causes OpenOffice to show the file in read-only mode, and remove the margins and various other editing widgets from the application window. Any attempt to save a document to an NFS mount results in an error dialog that contains the text:- Error saving the document Filename.odt: General Error. General input/output error. This makes the application extremely awkward to use in an office type environment, and is a huge step backwards in functionality from the OpenOffice.org 1.1.4 package it replaced for me. This bug is know in debian as bug #335742. It was closed by un upstream release. In breezy, there is no way to work around the bug wich make ooo unusable in breezy in an office environment with NFS. A partial solution would be to release a backport for openoffice.org2 from dapper, as the version in dapper works. To manage notifications about this bug go to: https://bugs.launchpad.net/openoffice/+bug/40537/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1032456] Re: Canon inkjets (and some other printers) print only half of the last page after 20120801 upgrade to v1.5.3-0ubuntu2
Confirmed with Canon MP520 on Precise . Tested very thoroughly with all different combinations of flags. Didn't work: lpadmin -p Canon-PIXMA-MP520 -o usb-unidir-default=true Didn't work: lpadmin -p Canon-PIXMA-MP520 -o usb-no-reattach-default=true Did work: both of the above flags set at the same time. Details: $ lsusb Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 003 Device 014: ID 04a9:1724 Canon, Inc. Bus 003 Device 003: ID 0409:0059 NEC Corp. HighSpeed Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:5719 IMC Networks Bus 003 Device 004: ID 0409:0059 NEC Corp. HighSpeed Hub Bus 003 Device 005: ID 046d:c042 Logitech, Inc. G3 Laser Mouse Bus 003 Device 006: ID 046d:c313 Logitech, Inc. Internet 350 Keyboard Bus 003 Device 007: ID 0b95:7720 ASIX Electronics Corp. AX88772 Bus 003 Device 008: ID 067b:2305 Prolific Technology, Inc. PL2305 Parallel Port Bus 003 Device 009: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port Bus 003 Device 010: ID 0d8c:0006 C-Media Electronics, Inc. Storm HP-USB500 5.1 Headset My 2c: it very much sounds like the remedy to bug 987485 and bug 997040 is worse than the disease, and that the above 2 flags should be made the default rather than the exception. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1032456 Title: Canon inkjets (and some other printers) print only half of the last page after 20120801 upgrade to v1.5.3-0ubuntu2 Status in “cups” package in Ubuntu: Fix Released Status in “cups” source package in Precise: Fix Released Bug description: My Canon i560 was working fine until the update two days ago. Now it fails every single job, printing half a page and then ejecting the page when a USB reset is issued. Same printer works fine when printing through Windows in Virtualbox with USB passthrough. Summary: the USB backend improvements have rendered my printer useless with CUPS. Unloading the usblp module makes no difference - the USB reset is what aborts the print job. [ 224.008042] usb 3-1: reset full-speed USB device number 3 using uhci_hcd [ 224.161701] usblp0: USB Bidirectional printer dev 3 if 0 alt 0 proto 2 vid 0x04A9 pid 0x108 Kubuntu 12.04 [IMPACT] Everyone with a Canon inkjet connected to USB and also users of some other printer models on USB get printouts with the last page being incomplete. This happens for every job. For everyone with a Samsung printer the problem of bug 995111 shows up again. [TESTCASE] Unfortunately, for reproducing this bug one needs the actual hardware. Connect a Canon inkjet (or other models mentioned in this bug report) to the USB and print from a completely updated Precise system. The last page of each job will come out incomplete. Connect a Samsung printer to the USB and print from a completely updated Precise system. You will get printouts with weird characters (at least from the second job on) as described in bug 995111. After installing the proposed package all these problems should disappear. [Regression Potential] Regression risk is very low. The fix is not doing the USB device reset on the printer after the job for most printers. The fix contains an exception rule for Samsung printers and Prolific Technology USB-Parallel adapters, to avoid reoccurring of bug 987485 and bug 997040. It is still possible that some printers are treated incorrectly in terms of whether they need a reset after the job or not. As most printers work both with and without reset this risk is very low. All reported problems are solved with the proposed fix. *** dpkg -l *cups*|grep ii ii bluez-cups 4.98-2ubuntu7 Bluetooth printer driver for CUPS ii cups 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - server ii cups-bsd 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - BSD commands ii cups-client 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - client programs (SysV) ii cups-common 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - common files ii cups-filters 1.0.18-0ubuntu0.1OpenPrinting CUPS Filters ii
[Desktop-packages] [Bug 411358] Re: Thunderbird2 gconf gmt problem 'Bad key or directory name' because of plus symbol (+)
There seems to be a regression; the bug came back in Thunderbird 13.0.1 and 14.0 (what I have here) on Lucid. Here's the upstream bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=541130 ** Bug watch added: Mozilla Bugzilla #541130 https://bugzilla.mozilla.org/show_bug.cgi?id=541130 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/411358 Title: Thunderbird2 gconf gmt problem 'Bad key or directory name' because of plus symbol (+) Status in Mozilla Thunderbird Mail and News: Unknown Status in “thunderbird” package in Ubuntu: Confirmed Bug description: Here is an error message for Thunderbird 2 in Jaunty gnubyexample@k8amd:~$ thunderbird GConf Error: Bad key or directory name: /desktop/gnome/url-handlers/GMT+02/command: `+' is an invalid character in key/directory names gnubyexample@k8amd:~$ date;uname -a;cat /etc/*version*;dpkg -l | grep underbird Sun Aug 9 14:48:37 BST 2009 Linux k8amd 2.6.28-14-generic #47-Ubuntu SMP Sat Jul 25 00:28:35 UTC 2009 i686 GNU/Linux 5.0 ii enigmail 2:0.95.7-1ubuntu2 Enigmail - GPG support for Thunderbird ii thunderbird 2.0.0.22+build1+nobinonly-0ubuntu0.9.04.1 mail/news client with RSS and integrated spam filter support ii thunderbird-locale-en-gb 1:2.0.0.14+1-0ubuntu2 Thunderbird English language/region package From reading this extract ( http://osdir.com/ml/os.solaris.opensolaris.desktop/2008-03/msg00020.html ): Subject:Re: GConf/Thunderbird error on Solaris Nevada Hi Mats,I believe you download the contribute builds of Thunderbird 2, and run it on snv_70. For some reason, the fix is upstreamed to Thunderbird 3 alpha, but not community version of Thunderbird 2. Fixed in snv_68 means the fix was integrated to Thunderbird bundled with snv_68. ...it seems that the fix for this in thunderbird2 might require some manual intervention as although the problem is well know, the fix was only incorporated in the newer thunderbird3. Have just checked the Karmic version at: http://packages.ubuntu.com/karmic/thunderbird which currently shows that version 2 of thunderbird is planned for Karmic release. As thunderbird3 is at Beta 3 right now I can perhaps see why debian and ubuntu are sticking with Thunderbird2 just now. http://www.mozillamessaging.com/en-US/about/press/archive/2009-07-21-01 However it does seem a shame to ship a new release with this known gconf issue unpatched. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/411358/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 411358] Re: Thunderbird2 gconf gmt problem 'Bad key or directory name' because of plus symbol (+)
** Also affects: thunderbird via https://bugzilla.mozilla.org/show_bug.cgi?id=541130 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/411358 Title: Thunderbird2 gconf gmt problem 'Bad key or directory name' because of plus symbol (+) Status in Mozilla Thunderbird Mail and News: Confirmed Status in “thunderbird” package in Ubuntu: Confirmed Bug description: Here is an error message for Thunderbird 2 in Jaunty gnubyexample@k8amd:~$ thunderbird GConf Error: Bad key or directory name: /desktop/gnome/url-handlers/GMT+02/command: `+' is an invalid character in key/directory names gnubyexample@k8amd:~$ date;uname -a;cat /etc/*version*;dpkg -l | grep underbird Sun Aug 9 14:48:37 BST 2009 Linux k8amd 2.6.28-14-generic #47-Ubuntu SMP Sat Jul 25 00:28:35 UTC 2009 i686 GNU/Linux 5.0 ii enigmail 2:0.95.7-1ubuntu2 Enigmail - GPG support for Thunderbird ii thunderbird 2.0.0.22+build1+nobinonly-0ubuntu0.9.04.1 mail/news client with RSS and integrated spam filter support ii thunderbird-locale-en-gb 1:2.0.0.14+1-0ubuntu2 Thunderbird English language/region package From reading this extract ( http://osdir.com/ml/os.solaris.opensolaris.desktop/2008-03/msg00020.html ): Subject:Re: GConf/Thunderbird error on Solaris Nevada Hi Mats,I believe you download the contribute builds of Thunderbird 2, and run it on snv_70. For some reason, the fix is upstreamed to Thunderbird 3 alpha, but not community version of Thunderbird 2. Fixed in snv_68 means the fix was integrated to Thunderbird bundled with snv_68. ...it seems that the fix for this in thunderbird2 might require some manual intervention as although the problem is well know, the fix was only incorporated in the newer thunderbird3. Have just checked the Karmic version at: http://packages.ubuntu.com/karmic/thunderbird which currently shows that version 2 of thunderbird is planned for Karmic release. As thunderbird3 is at Beta 3 right now I can perhaps see why debian and ubuntu are sticking with Thunderbird2 just now. http://www.mozillamessaging.com/en-US/about/press/archive/2009-07-21-01 However it does seem a shame to ship a new release with this known gconf issue unpatched. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/411358/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
