subject:"\[Bug 1431753\] Re\: Nvidia binary driver FTBS due to DKMS layer violation"

Right, that usually doesn't happen when you upgrade to a new version of
the same driver (for example upgrading nvidia-331 from 331.19 to
331.25). However, when you are migrated to a different driver package,
e.g. from nvidia-331 to nvidia-340, you will lose your settings, because
they are different packages and they provide different alternatives

Yes, I know. But since in this case installing a different driver
packages was forced by an update (without even a warning or asking for
confirmation, btw), whatever process was responsible for that should
take that into account and take care of migrating the settings.

This, while unfortunate, is not a bug,

Yes it is. You are only giving a diagnosis of the exact cause of the bug
(which by the way I already knew), but that doesn't make it less of a
bug.

and we cannot change it, due to
the way alternatives work.

I seriously doubt that's IMPOSSIBLE to fix. It may not be easy, but if you can
do it manually, it can be done automatically. You only need to produce a script
that looks at the settings (alternatives, or whatever) before uninstalling the
old package, and then applies them (with all the necessary remappings and
modifications) after installing the new one.
It may be a lot of work but it's NECESSARY and it was part of fixing this
issue. A part that hasn't been done.

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

 Support for Optimus is something that we provide using our own system

Cool! (except it doesn't work, but I'll file a separate bug, though I'm
surprised there's none already if it's supposed to work, as it's widely
known that it doesn't at all)

So this page (among a few that I remember having read) must be out of date?
https://wiki.ubuntu.com/Ubuntu/Wishlist?highlight=%28nvidia%29%7C%28optimus%29

Whish list
- NVIDIA Optimus integration (though this may be up to NVIDIA, not Canonical)


-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

I knew it must have already been reported.
Here it is:
https://bugs.launchpad.net/xorg-server/+bug/1220426

Importance undecided and unassigned sinse 2013

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

On 14-08-15 10:52:23, teo1978 wrote:
This, while unfortunate, is not a bug,

Yes it is. You are only giving a diagnosis of the exact cause of the bug
(which by the way I already knew), but that doesn't make it less of a
bug.

The alternatives switched back to automatic mode, and in automatic mode
the nvidia alternative has a higher priority than mesa's (which is what
you want).

You can either select the mesa alternative, call ldconfig, and update
the initramfs, or uninstall the nvidia package (as I recommended).

and we cannot change it, due to
the way alternatives work.

I seriously doubt that's IMPOSSIBLE to fix. It may not be easy, but if you
can do it manually, it can be done automatically. You only need to produce a
script that looks at the settings (alternatives, or whatever) before
uninstalling the old package, and then applies them (with all the necessary
remappings and modifications) after installing the new one.
It may be a lot of work but it's NECESSARY and it was part of fixing
this issue. A part that hasn't been done.

Such work is not necessary, as yours is really an unsupported corner
case. If you insist on keeping the nvidia driver installed and disabled,
against what we recommend, that is your problem.

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

If you have a machine that works, and you run automatic updates, and
your machine stops working, there's a bug. If there's anything wrong in
the machine configuration when you are updating, it must be detected, a
warning given, and the option to continue at your own risk or skip that
update.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-08-14 Thread Jerry

Unfortunately, to get newer versions and hopefully out of Nvidia kernel
update hell, I went from LTS to the next regular unsupported, hoping to go
beyond that one to contemporary, but all went astray into unstable and
unbootable, probably in the filing to upgrade multiple times, repository
problems and bugs in same...

Possibly waiting a bit on 15.10alpha to mature and upgrade nonbootable disk
from cdr/dvdr/usbstick/netboot to get back to a working system.

Waiting for godot was too frustrating.

On Fri, Aug 14, 2015, 09:36 teo1978 teo8...@gmail.com wrote:

 If you have a machine that works, and you run automatic updates, and
 your machine stops working, there's a bug. If there's anything wrong in
 the machine configuration when you are updating, it must be detected, a
 warning given, and the option to continue at your own risk or skip that
 update.

 --
 You received this bug notification because you are subscribed to a
 duplicate bug report (1405597).
 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 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:
   Invalid
 Status in nvidia-graphics-drivers-331-updates source package in Trusty:
   Invalid
 Status in nvidia-graphics-drivers-340 source package in Trusty:
   Fix Released
 Status in nvidia-graphics-drivers-340-updates source package in Trusty:
   Fix Released
 Status in nvidia-graphics-drivers-346 source package in Trusty:
   Fix Released
 Status in nvidia-graphics-drivers-346-updates source package in Trusty:
   Fix Released

 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


-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

Such work is not necessary, as yours is really an unsupported corner
case. If you insist on keeping the nvidia driver installed and disabled,
against what we recommend, that is your problem.

And how was I supposed to know what you recommend?

Back in the days when I installed Ubuntu on my machine, there was a friendly
interface somewhere like Software Updates Additional Drivers or
something, where I could choose to install and use the NVidia drivers.
Then, when I saw they wouldn't work, I went to the same interface and chose not
to use them. No warning appeared telling me that was not recommended or that
I should uninstall the drivers.

Should I have read the whole Ubuntu documentation, like Let's see if
what I just did through the standard interface is not recommended, and
if they recommend doing something else like uninstalling the driver.

It's not that I insist in keeping the driver installed and disabled. I
did that ages ago and forgot about it. And I very much doubt it's that
much of a corner case. Right in this thread you have another user to
whom the exact same thing happened.

And even if we are few, we got in our situation by just using what then
was the user interface (I mean, we didn't tinkle and mess around with
stuff), so if we got to a situation that was not supported, something
was wrong in Ubuntu in the first place, and if we got into a situation
which was then supported and then stopped being, then it's Ubuntu
responsibility to make sure that automatic updates take that into
account and keep things working.

And also, if a piece of software is designed in such a way that if you stop
using it yoy have to uninstall it otherwise it may be harmful, it is badly
designed.

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

On 13-08-15 16:50:40, teo1978 wrote:
  By design a driver will be enabled if you install it.

 However, if it is disable when you UPGRADE the driver, it shouldn't be
 reenabled.

Right, that usually doesn't happen when you upgrade to a new version of
the same driver (for example upgrading nvidia-331 from 331.19 to
331.25).  However, when you are migrated to a different driver package,
e.g. from nvidia-331 to nvidia-340, you will lose your settings, because
they are different packages and they provide different alternatives
(note: the alternatives are what allows you to enable or disable a
driver).

This, while unfortunate, is not a bug, and we cannot change it, due to
the way alternatives work.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

On 13-08-15 16:45:47, teo1978 wrote:
  2) Optimus is supported by the NVIDIA driver.

 That's not what NVidia told me. I asked for support and they told me it's 
 officially unsupported on Linux.
 And what I can tell for sure is that it doesn't work. The screen switching 
 issue is well known.

That only means that, if something goes wrong, you're on your own (at
least as far as NVIDIA are concerned). Support for Optimus is something
that we provide using our own system. What the NVIDIA driver supports is
part of the RandR 1.4, which we use for Optimus.

I won't comment on the screen switching issue, unless I see the relevant
logs (in a separate bug report), as it could depend on a number of
things (including your hardware configuration).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

On 14-08-15 13:24:50, teo1978 wrote:
Such work is not necessary, as yours is really an unsupported corner
case. If you insist on keeping the nvidia driver installed and disabled,
against what we recommend, that is your problem.

And how was I supposed to know what you recommend?

Back in the days when I installed Ubuntu on my machine, there was a friendly
interface somewhere like Software Updates Additional Drivers or
something, where I could choose to install and use the NVidia drivers.
Then, when I saw they wouldn't work, I went to the same interface and chose
not to use them. No warning appeared telling me that was not recommended or
that I should uninstall the drivers.

Different use cases were supported in 12.04. For example, you could have
multiple nvidia drivers installed at the same time. That changed after
12.04.

And also, if a piece of software is designed in such a way that if you
stop using it yoy have to uninstall it otherwise it may be harmful, it
is badly designed.

Ok, that implies that all drivers are badly designed. It's your opinion.
This, however, is a bug report.

Now please stop posting, as this bug report is closed.

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

  And also, if a piece of software is designed in such a way that if you
  stop using it yoy have to uninstall it otherwise it may be harmful, it
  is badly designed.

 Ok, that implies that all drivers are badly designed. It's your opinion.

Don't pretend you are stupid when you aren't. This driver used to have an 
option (nicely accessible through user interface) which allowed to just not use 
it. It was *designed* to be either used or not used. And when not used, it 
would do nothing and interfere with nothing.
So, the newer version doesn't that anymore? Then you can't replace one version 
with another without performing some check. The update is incomplete and buggy 
if it does that.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-08-14 Thread graingert

Guys it's a closed source driver. I'm being a hypocrite here, but chillax.
On 14 Aug 2015 21:16, teo1978 teo8...@gmail.com wrote:

   And also, if a piece of software is designed in such a way that if you
   stop using it yoy have to uninstall it otherwise it may be harmful, it
   is badly designed.
 
  Ok, that implies that all drivers are badly designed. It's your opinion.

 Don't pretend you are stupid when you aren't. This driver used to have an
 option (nicely accessible through user interface) which allowed to just not
 use it. It was *designed* to be either used or not used. And when not used,
 it would do nothing and interfere with nothing.
 So, the newer version doesn't that anymore? Then you can't replace one
 version with another without performing some check. The update is
 incomplete and buggy if it does that.

 --
 You received this bug notification because you are subscribed to a
 duplicate bug report (1411195).
 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 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:
   Invalid
 Status in nvidia-graphics-drivers-331-updates source package in Trusty:
   Invalid
 Status in nvidia-graphics-drivers-340 source package in Trusty:
   Fix Released
 Status in nvidia-graphics-drivers-340-updates source package in Trusty:
   Fix Released
 Status in nvidia-graphics-drivers-346 source package in Trusty:
   Fix Released
 Status in nvidia-graphics-drivers-346-updates source package in Trusty:
   Fix Released

 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


-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

 Different use cases were supported in 12.04

That's my point: you can't just drop supported usecases and do nothing
about it. If I'm doing something supported and I upgrade, and that's not
supported any more, the upgrade MUST guide me through a way to fix
whatever is wrong.

 Now please stop posting, as this bug report is closed.

I'm posting because it must be reopened.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-08-14 Thread LocutusOfBorg

Are you aware that each comment triggers THOUSAND of emails to other
users?

Please respect them, and use private messages with your exchanges with
Alberto.

This particular bug is FIXED. it might have triggered regressions, or
something new I do not know, and opening new bugs is the correct way to
handle it.

You can't close the same bug twice, and you can't reopen a fixed bug.

Leave with the design of LP, and go in a new bug.

thanks.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

 Are you aware that each comment triggers THOUSAND of emails to other
users?

Are you aware that you can unsubscribe if you want to?

 You can't close the same bug twice, and you can't reopen a fixed bug.

No I can't but there are definitely people who can.


 This particular bug is FIXED. it might have triggered regressions, 
  and opening new bugs is the correct way to handle it.

Well that's a way of seeing it (I'd say a bugfix that fixes half of the
bug or does it in the wrong way is not a complete fix and hence leaves
the bug not fixed).

Ok, I'll go open a new issue.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

 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.

I was not talking about the Optimus issue (I never argued that should be part 
of this issue, though I admit I did make some OT comment about that).
I was talking about the fact that the update that fixes THIS very issue causes 
the reenabling of NVidia drivers which were previously disabled, hence changing 
 a system configuration that should not be touched.

But anyway, since I've been told that the fact that the fix to this bug
is broken is a separate bug, I've filed a separate bug. That wouldn't
have generated such a long exchange if Alberto didn't insist in claiming
that the fix is not broken at all, that everything is ok, and that there
is no additional problem to be fixed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-08-14 Thread LocutusOfBorg

Are you aware that you can unsubscribe if you want to?

yes, but this doesn't change the point.

No I can't but there are definitely people who can.

it would be useless.

Well that's a way of seeing it (I'd say a bugfix that fixes half of the bug or 
does it in the wrong way is not a complete fix and hence leaves the bug not 
fixed).

Ok, I'll go open a new issue.

this is how debhelper works, and how the syntax of closing bugs works on LP and 
Debian.
if you want to fix this bug go on the new open bug and help Alberto with the 
stuff he requested.

Unfortunately dealing with closed and proprietary software is not so
easy, and I'm telling this with my Debian Developer hat on.

Sorry for that, but posting here will annoy people, and for sure not
help you.

And since I'm a DD, I'll follow the bug you created, and try to help there, 
because I'm not bothered by your mails, but other people are.
(thinking about freedom is also caring about other people's issues)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-08-14 Thread KennoVO

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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-08-14 Thread Alexander Chr. Tornow

Sup guys,

quick update: Seems Alberto was right, my family and friends switched
back to Nouveau via the driver utility and were then able to install the
new tested and recommended Nvidia drivers 346.82 via the stable repo
provided by Ubuntu. No need to use -updates. System stability and speed
has been restored! I can't verify this myself, since I have given up on
Nvidia (running on AMD and Intel + Open Source drivers now), thus: I
have added a screenshot that a friend sent me to this post, showing the
new drivers available to Nvidia users.

Thanks @whoever fixed this!

Cheers,
Alex

** Attachment added: New Nvidia drivers.
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340-updates/+bug/1431753/+attachment/4445056/+files/20150814054438.jpg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-08-14 Thread J K Cunningham

On 08/14/2015 01:46 PM, teo1978 wrote:
 Are you aware that each comment triggers THOUSAND of emails to other
 users?

 Are you aware that you can unsubscribe if you want to?


I unsubscribed from this bug report days ago and it's still sending me 
your silly tirades.
Would you please STFU?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-08-13 Thread Anna

I have a smilar case as teo1978. - I have a dell laptop with Optimus
technology with both Intel and Nvidia GPU.

Before the upgrade from 331 to 340 I never managed to get the Nvidia GPU
running, so I just used Intel instead. After the upgrade, the Nvidia GPU
was turned on by default but something was wrong with the configuration
in the xorg.conf file. Because of this I got a black screen after
rebooting.

The solution that I linked a few posts up actually has a thorough
explanation of what happened. It shows how to fix the xorg.conf file and
how to prevent ubuntu from changing it back after reboot (it was crucial
for me).

After all that my laptop started to actually use the Nvidia GPU for both
daily use and manually running simulation on GPU.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

So, the issue I pointed out is definitely confirmed.

Please, whoever can, change back the status at least for 340-Tursty,
because the fix is partially broken.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

Or should we file a separate bug?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-08-13 Thread dino99

hey all users still complaining:

- be sure to have a clean nvidia driver installation: not a system where the 
driver receive upgrades but still with borked settings behind the scene
- so sudo apt-get purge nvidia* is mandatory first, then install the required 
driver

- as the '331' driver is now deprecated, and replaced by the '340' one,
that means the still opened '331' are useless

So this report is closed now; meaning you need to open a new report if
you really need

** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu Trusty)
   Status: Triaged = Invalid

** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu)
   Status: Confirmed = Invalid

** Changed in: nvidia-graphics-drivers-331 (Ubuntu Trusty)
   Status: Triaged = Invalid

** Changed in: nvidia-graphics-drivers-331 (Ubuntu Trusty)
 Assignee: Alberto Milone (albertomilone) = (unassigned)

** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu Trusty)
 Assignee: Alberto Milone (albertomilone) = (unassigned)

** Changed in: nvidia-graphics-drivers-331 (Ubuntu)
   Status: Confirmed = Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-08-13 Thread Robin

Teo,

the Optimus issue is definitely a *separate bug*, requiring its own 
resolution.

R.

On 13/08/15 14:48, teo1978 wrote:
 Or should we file a separate bug?


-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-08-13 Thread Alberto Milone

Just to clarify:

1) Do not install the driver unless you want to use it. Uninstalling the
driver will not break your system. By design a driver will be enabled if
you install it. We keep an option to disable the driver but that's only
to be used by gpu-manager (which is part of ubuntu-drivers-common), in
order to support hybrid graphics. That is not meant to be disabled
manually.

2) Optimus is supported by the NVIDIA driver. @teo1978 feel free to file
a separate bug report about the external screen issue.

3) Optimus seems to fail with 340 on some systems, and even with 346 on
others. We moved from the modesetting driver (which NVIDIA recommend
but it's not the only driver that works) to intel because some systems
didn't work (either at all or correctly). On such systems using the
modesetting driver is the only solution. Please file a separate bug
report about this (and file it against ubuntu-drivers-common)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

 2) Optimus is supported by the NVIDIA driver.

That's not what NVidia told me. I asked for support and they told me it's 
officially unsupported on Linux.
And what I can tell for sure is that it doesn't work. The screen switching 
issue is well known.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

 hey all users still complaining:

 - be sure to

No man, if one had a system that was working and properly set up, and
after getting an update it is broken (or something that was correctly
configured gets misconfigured, or any configuration unnecessarily
changed at all), there is a bug.

We aren't supposed to be sure to anything. The updates should make
sure to not screw up a working system.

The bug should NOT be closed, unless a new one is opened for the issue
caused by the fix to this bug.

I am not going to waste my time reconfiguring my system every time a new
update comes out and screws up the settings that I already had to
manually fix.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

 Uninstalling the driver will not break your system

On another machine, merely *installing* it did break the system. So
forgive me if I'm skeptical that uninstalling it will not break my
system. I take that as a should not.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

 By design a driver will be enabled if you install it.

However, if it is disable when you UPGRADE the driver, it shouldn't be
reenabled.

 We keep an option to disable the driver but [...] That is not meant to
be disabled manually.

I don't know about now, but at the time I installed the driver, there was a 
nice graphical interface, accessible somewhere from the System Settings menu 
(back when Ubuntu had a menu), where you could choose whether to use NVidia 
proprietary drivers. And I chose not to.
It wasn't some arcane command line that I found out by googling around, it was 
something that was made accessible to a normal user. If things have changed 
since, you must take into account that there are machines still around that 
have been upgraded since those times. I can't remember exactly which Ubuntu 
version that was. It may have been 13.04, or 12.something

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

 Teo,

 the Optimus issue is definitely a *separate bug*, requiring its own
 resolution.

I was not talking about the optimus issue.
I was talking about the fact that the update of the NVidia drivers overwrote 
some system settings that shouldn't have been touched. Before the update, my 
system was set up to not use nVidia drivers; after the update, it was set to 
use them. That's a bug in the update that was released.

I'm not quite sure whether or not that should be considered a separate
issue, because it is an issue directly caused by the fix to this issue.
That is, the fix to this issue caused a bug of its own.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

@lbertomilone please see https://bugs.launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-340/+bug/1483388 and mark its importance as
critical (prevents boot) as soon as possible.

Also feel free to correct anything that may be wrong in the report.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

@albertomilone please see https://bugs.launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-340/+bug/1483388 and mark its importance as
critical (prevents boot) as soon as possible.

Also feel free to correct anything that may be wrong in the report.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-08-12 Thread Anna

After upgrading my 331 drivers  to 340 I got black screen.

This solution worked for me: http://vxlabs.com/2015/02/05/solving-the-
ubuntu-14-04-nvidia-346-nvidia-prime-black-screen-issue/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-08-12 Thread Alberto Milone

On 11-08-15 22:45:43, teo1978 wrote:
 So, will my 331 drivers be automagically replaced with 340, or with
 whatever version fixes the bug? (or perhaps they have already?) Because
 otherwise, the bug is not fixed for me nor for the millions of people
 having ubuntu 14.04 with 331 drivers. Anyway, if that's not going to be
 automatic, what should I do to get that?

Yes, 331 will be replaced by 340 through a system update. If you prefer
346 you can install it manually from our repositories (as long as your
graphics card is supported).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

Yes, 331 will be replaced by 340 through a system update.

Nice, but is it possible that it not only replaces 331 by 340 but ALSO
ENABLES THEM?

Because I'm under the impression that that just happened to me, and
that's a bug.

Ages ago, when I first enabled NVidia drivers, I had this problem that
every time I would connect and disconnect an external screen, the
computer would start to randomly freeze at any moment. It turned out it
was because the lack of support of NVidia drivers for Optimus technology
on Linux. So I SWITCHED TO NOUVEAU, and had never been using NVidia
drivers ever since, which was/is the only option for those like me who
have an Optimus device. And that issue disappeared (though the NVidia
drivers were still installed and gave me the compile error at every
kernel upgrade).

Now, THE FREEZING ISSUE HAS REAPPEARED.
I suspect the update not only replaced 331 with 340 drivers, but also enabled
them while I had explicitly disabled them in favour of Nouveau.

Please how do I disable them again?
And please change back the status of this bug until this part is fixed too.

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

and I'm pretty sure it's also the cause of this:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1483388

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

They are installed.
The issue is that they were configured not to be used, and now they are.
I don't remember where the setting is but you decide whether to use nVidia 
drivers or not, even without uninstalling them.
And this setting shouldn't be changed by the update: the fact that it is is a 
bug.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

And I'm pretty scared of uninstalling the drivers without first
disabling them, because I don't trust at all the package uninstallation
process to handle things well.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

Indeed, I think I installed Bumblebee, because I thought that it would handle 
automatic switching between intel and nvidia as needed, but no way! it turns 
out it just allows you (or is supposed to allow, because I never managed to do 
even that)  to manually run stuff on NVidia. So, in practice I have (or used to 
have until this update) bumblebee, nvidia drivers, and the intel GPU actually 
used all the time with the nvidia card just sleeping and useless. And I don't 
care, as long as my system doesn't start freezing every time I unplug the 
external screen.
All was fine (except for the errors showing up at kernel updates), and now 
everything is broken again (i.e. nvidia drivers being used, and causing random 
freezes because they don't support Optimus - or at least that's the diagnosis I 
was given when I first had the problem a couple of years ago)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-08-12 Thread Alberto Milone

On 12-08-15 13:33:31, teo1978 wrote:
Yes, 331 will be replaced by 340 through a system update.

Nice, but is it possible that it not only replaces 331 by 340 but ALSO
ENABLES THEM?

Because I'm under the impression that that just happened to me, and
that's a bug.

Now, THE FREEZING ISSUE HAS REAPPEARED.
I suspect the update not only replaced 331 with 340 drivers, but also enabled
them while I had explicitly disabled them in favour of Nouveau.

Please how do I disable them again?
And please change back the status of this bug until this part is fixed too.

If you uninstall the drivers, you won't get any updates. Also, this bug
report shouldn't affect you at all if the nvidia drivers are not
installed.

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

 Please keep your subjective comments to yourself

I think my comments were pretty objective.
Ubuntu fails at providing a decent user experience, and it's getting worse.
Ubuntu sucks at supporting NVidia (which is probably mostly NVidia's fault, but 
other distros do better nonetheless).
Ubuntu spends very little effort in improving its desktop operating system 
since their interest have moved to mobile.
Ubuntu fails at fixing bugs in a decent time.

Now all of this may well be OT here, but they are facts, with little
margin of subjectivity.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

Just to make it clear, the status of this bug report was marked as
Fix released because the fix was actually released, and it's available
to you as long as you have the trusty-updates repositories enabled
(which should be enabled by default).

The latest status updates are about drivers 340+ versions. 331/Trusty is
still confirmed/triaged. Last time I checked, I had 331 installed. And I
remember getting the crash at some kernel update not long ago, but I
don't know when the last kernel update was.

So, will my 331 drivers be automagically replaced with 340, or with
whatever version fixes the bug? (or perhaps they have already?) Because
otherwise, the bug is not fixed for me nor for the millions of people
having ubuntu 14.04 with 331 drivers. Anyway, if that's not going to be
automatic, what should I do to get that?

For a bug to be fix released, it requires that the issue must
disappear without me doing anything except for accepting the automatic
updates.

@Alexander donating money to Ubuntu? I hope you are kidding. That money is
going to be wasted in making Ubuntu worse, which is the only thing Canonical
does (whenever it does change something). Just see how Nautilus evolves or
how grub still bricks a machine on dist-upgrade, just to name the top examples
that come to my mind.
You'd better donate directly to Alberto Milone or to whomever actually is
actually doing something useful, or even something non-destructive.
Canonical has stopped giving a shit about desktop a while ago; apparently they
are focusing on mobile (is Ubuntu mobile even a fucking thing?!?)

Canonical wants to improve the situation for Nvidia users in the future

OMFG, whants to and in the future? For god's sake. It's been what?
20 years since NVidia has been the leader in the market of GPUs?

I am DEFINITELY done with Ubuntu. How long it will take for me to switch
to OpenSUSE is just a matter of how damn lazy I am.

(and you can bet I'll never buy a machine with an NVidia card again)

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

  http://www.phoronix.com/scan.php?page=news_itempx=Ubuntu-Better-
Gaming-Drivers

Btw that's going to be practically useless as long as there's no support
on linux for Optimus. Most computers with NVidia cards now seem to have
that shit.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-08-11 Thread Jerry

I flagged as security, since holds back kernel updates which escalated sec
probs, if not causes them.  Ianal
On Aug 11, 2015 3:21 AM, ciro santoro 1431...@bugs.launchpad.net wrote:

 I installed last updates on my ubuntu 14.04 and, after reboot, it starts
 and remains with a black screen.. I listened the ubuntu welcome sound and
 nothing appens :(

 2015-08-08 20:51 GMT+02:00 Nathanaël Naeri 1431...@bugs.launchpad.net:

  Packages nvidia-331-* are now transitional packages for version 340
  where this bug has been fixed, so I guess they can be marked as Fix
  Released too. Thanks everyone involved esp. Alberto for your work.
 
  --
  You received this bug notification because you are subscribed to a
  duplicate bug report (1409930).
  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 Released
  Status in nvidia-graphics-drivers-340-updates source package in Trusty:
Fix Released
  Status in nvidia-graphics-drivers-346 source package in Trusty:
Fix Released
  Status in nvidia-graphics-drivers-346-updates source package in Trusty:
Fix Released
 
  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
 


 --
 Ciro Santoro

 --
 You received this bug notification because you are subscribed to a
 duplicate bug report (1405597).
 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 Released
 Status in nvidia-graphics-drivers-340-updates source package in Trusty:
   Fix Released
 Status in nvidia-graphics-drivers-346 source package in Trusty:
   Fix Released
 Status in nvidia-graphics-drivers-346-updates source package in Trusty:
   Fix Released

 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

Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-08-11 Thread ciro santoro

I installed last updates on my ubuntu 14.04 and, after reboot, it starts
and remains with a black screen.. I listened the ubuntu welcome sound and
nothing appens :(

2015-08-08 20:51 GMT+02:00 Nathanaël Naeri 1431...@bugs.launchpad.net:

 Packages nvidia-331-* are now transitional packages for version 340
 where this bug has been fixed, so I guess they can be marked as Fix
 Released too. Thanks everyone involved esp. Alberto for your work.

 --
 You received this bug notification because you are subscribed to a
 duplicate bug report (1409930).
 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 Released
 Status in nvidia-graphics-drivers-340-updates source package in Trusty:
   Fix Released
 Status in nvidia-graphics-drivers-346 source package in Trusty:
   Fix Released
 Status in nvidia-graphics-drivers-346-updates source package in Trusty:
   Fix Released

 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



-- 
Ciro Santoro

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

So, I'm lucky enough to be able to USE my machine just because I'm not
actually using NVidia drivers?

My problem with this bug is only that I get an error message about something 
crashing every time there's a kernel update. I thought that was it, but I see 
there are people whose system stop booting or becomes unusable because of this, 
WTF!
That is, what, everybody using ubuntu 14.04 with an NVidia card that doesn't 
have the Optimus technology (which renders the nvidia card useless on linux, 
but on the up side, avoids this bug, apparently)?
And it's been a year without fixing.

I'm done with Ubuntu.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-08-11 Thread Alberto Milone

@ciro: that could be caused by a number of things. If you can ssh into
the machine, or VT switch by pressing CTRL+ALT+F2, please collect the
following data:

1) the output of dkms status
2) the dmesg output
3) /var/log/Xorg.0.log
4) /var/log/gpu-manager.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-08-11 Thread Peter Varlien

I had the same experience.

It turned out thet my xorg.conf file had been renamed with a .back
suffix. I copied it back and restarted, and all was good.

On August 11, 2015 9:14:05 AM CEST, ciro santoro 1431...@bugs.launchpad.net 
wrote:
I installed last updates on my ubuntu 14.04 and, after reboot, it
starts
and remains with a black screen.. I listened the ubuntu welcome sound
and
nothing appens :(

2015-08-08 20:51 GMT+02:00 Nathanaël Naeri
1431...@bugs.launchpad.net:

 Packages nvidia-331-* are now transitional packages for version 340
 where this bug has been fixed, so I guess they can be marked as Fix
 Released too. Thanks everyone involved esp. Alberto for your work.

 --
 You received this bug notification because you are subscribed to a
 duplicate bug report (1409930).
 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 Released
 Status in nvidia-graphics-drivers-340-updates source package in
Trusty:
   Fix Released
 Status in nvidia-graphics-drivers-346 source package in Trusty:
   Fix Released
 Status in nvidia-graphics-drivers-346-updates source package in
Trusty:
   Fix Released

 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



-- 
Ciro Santoro

-- 
You received this bug notification because you are subscribed to a
duplicate bug report (1410245).
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 Released
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Fix Released

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

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-08-11 Thread Alexander Chr. Tornow

@teo1978:

Yeah, I fully agree. I recommended Ubuntu LTS to everyone I know that
has been willing to either give Ubuntu a try or to users that have
completely switched from Windows. My words, after they asked me why I
recommend LTS over normal Ubuntu: Use LTS if you prefer stability,
support and reliability.

And now I am eating my own words.

It's nice to see this bug is getting fixed... finally... but it's sad it
took so long in the first place. A lot of my friends were left with an
unstable or malfunctioning system and that's a real show stopping issue,
especially because the issue came unexpected after updating the system
as usual. Ever since reporting this bug, I have switched to an AMD 6000
series GPU, using the open and free AMD drivers Ubuntu ships and
activates at default. It's been awesome so far, gaming-wise as well.

So, personally, I am not going to lose any sleep over this issue
anymore. But my friends are still using Nvidia hardware + Ubuntu
14.04.2/3 LTS and I'd like to know if the faulty Nvidia drivers (331.x?)
available via the Ubuntu repos have been replaced with the drivers
mentioned in this bug report that include the fix - or is the solution
to activate the unstable testing/proposed repo the only way out of this
mess?

Any kind of feedback is appreciated!

Thanks!

Cheers,
Alex

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-08-11 Thread Alberto Milone

Just to make it clear, the status of this bug report was marked as Fix
released because the fix was actually released, and it's available to
you as long as you have the trusty-updates repositories enabled (which
should be enabled by default).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-08-11 Thread Alberto Milone

On 31-05-15 03:23:09, KennoVO wrote:
 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?

Yes, the update is available in 14.04, and works with the kernels 14.04
ships with.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-08-11 Thread Alexander Chr. Tornow

@Alberto:

PERFECT! Thanks for the info! I'll let my family and friends know ASAP.

One more question: Does trusty-updates mean the Nvidia -updates
repo?

And because I am very pleased by this work, I'll donate some cash to
Ubuntu tonight.

Again; thank you, even though it took a while.

Cheers,
Alex

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-08-11 Thread Alexander Chr. Tornow

Oh btw, for everyone else interested in this subject, Canonical wants to
improve the situation for Nvidia users in the future:
http://www.phoronix.com/scan.php?page=news_itempx=Ubuntu-Better-Gaming-
Drivers

+1 @Jorge Castro!

This is something that openSUSE has been doing for many years and I
welcome the idea.

Cheers,
Alex

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-08-11 Thread el_gallo_azul

Yeah
(*pff*)   De: josh joshuaglennmur...@gmail.com
 Para: el_gallo_a...@yahoo.com 
 Enviado: Miércoles 12 de agosto de 2015 9:16
 Asunto: Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer 
violation
   
Dude no one cares this is a bug reporting place not an opinion catcher.
On 12 Aug 2015 11:46, teo1978 teo8...@gmail.com wrote:

  Please keep your subjective comments to yourself

 I think my comments were pretty objective.
 Ubuntu fails at providing a decent user experience, and it's getting worse.
 Ubuntu sucks at supporting NVidia (which is probably mostly NVidia's
 fault, but other distros do better nonetheless).
 Ubuntu spends very little effort in improving its desktop operating system
 since their interest have moved to mobile.
 Ubuntu fails at fixing bugs in a decent time.

 Now all of this may well be OT here, but they are facts, with little
 margin of subjectivity.

 --
 You received this bug notification because you are subscribed to a
 duplicate bug report (1412043).
 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 Released
 Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Fix Released
 Status in nvidia-graphics-drivers-346 source package in Trusty:
  Fix Released
 Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Fix Released

 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


-- 
You received this bug notification because you are subscribed to a
duplicate bug report (1401725).
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 Released
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Fix Released

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

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-08-11 Thread Sezer Yalcin

Please keep your subjective comments to yourself. This is a bug report.
Even Linus said Nvidia is very ignorant about linux. So if you need graphics 
with less issues, but Intel which really pays attention to linux. or Use ATI 
and see the worst! 

Nvidia's self packaged drivers always fail at distro specific script. So
they really don't care much. Their target customer is GTA5 players who
spend rich dad's money, not blender users with limited budget.

After ATI experience, I am glad Nvidia works somehow.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-08-11 Thread josh

Dude no one cares this is a bug reporting place not an opinion catcher.
On 12 Aug 2015 11:46, teo1978 teo8...@gmail.com wrote:

  Please keep your subjective comments to yourself

 I think my comments were pretty objective.
 Ubuntu fails at providing a decent user experience, and it's getting worse.
 Ubuntu sucks at supporting NVidia (which is probably mostly NVidia's
 fault, but other distros do better nonetheless).
 Ubuntu spends very little effort in improving its desktop operating system
 since their interest have moved to mobile.
 Ubuntu fails at fixing bugs in a decent time.

 Now all of this may well be OT here, but they are facts, with little
 margin of subjectivity.

 --
 You received this bug notification because you are subscribed to a
 duplicate bug report (1412043).
 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 Released
 Status in nvidia-graphics-drivers-340-updates source package in Trusty:
   Fix Released
 Status in nvidia-graphics-drivers-346 source package in Trusty:
   Fix Released
 Status in nvidia-graphics-drivers-346-updates source package in Trusty:
   Fix Released

 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


-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-08-08 Thread Nathanaël Naeri

Packages nvidia-331-* are now transitional packages for version 340
where this bug has been fixed, so I guess they can be marked as Fix
Released too. Thanks everyone involved esp. Alberto for your work.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

This bug was fixed in the package nvidia-graphics-drivers-346 -
346.82-0ubuntu0.2

---
nvidia-graphics-drivers-346 (346.82-0ubuntu0.2) trusty-proposed; urgency=medium

  * debian/templates/control.in:
- Add conflicts/replaces for old releases of nvidia-opencl-icd-331 and
  of nvidia-opencl-icd-331-updates, and for the current releases of
  nvidia-opencl-icd-304 and of nvidia-opencl-icd-304-updates that still
  conflict with and replace opencl-icd (LP: #1465706).

nvidia-graphics-drivers-346 (346.82-0ubuntu0.1) trusty-proposed;
urgency=medium

  * Initial release (LP: #1465706, LP: #1431753).

 -- Alberto Milone alberto.mil...@canonical.com  Wed, 29 Jul 2015
12:33:47 +0200

** Changed in: nvidia-graphics-drivers-346 (Ubuntu Trusty)
   Status: Fix Committed = Fix Released

** Changed in: nvidia-graphics-drivers-340-updates (Ubuntu Trusty)
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

This bug was fixed in the package nvidia-graphics-drivers-340-updates -
340.76-0ubuntu0.1

---
nvidia-graphics-drivers-340-updates (340.76-0ubuntu0.1) trusty-proposed; 
urgency=medium

  * Initial release (LP: #1465706, LP: #1431753).
  * Changes in this backport, compared to wily:
- Try to clean up the libraries and links left by the 331 series.
- Allow nvidia-opencl-icd-$flavour to replace nvidia-opencl-icd-331 and
  nvidia-opencl-icd-331-updates for a smooth upgrade.

 -- Alberto Milone alberto.mil...@canonical.com  Thu, 25 Jun 2015
11:46:49 +0200

** Changed in: nvidia-graphics-drivers-346-updates (Ubuntu Trusty)
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

This bug was fixed in the package nvidia-graphics-drivers-346-updates -
346.82-0ubuntu0.2

---
nvidia-graphics-drivers-346-updates (346.82-0ubuntu0.2) trusty-proposed; 
urgency=medium

  * debian/templates/control.in:
- Add conflicts/replaces for old releases of nvidia-opencl-icd-331 and
  of nvidia-opencl-icd-331-updates, and for the current releases of
  nvidia-opencl-icd-304 and of nvidia-opencl-icd-304-updates that still
  conflict with and replace opencl-icd (LP: #1465706).

nvidia-graphics-drivers-346-updates (346.82-0ubuntu0.1) trusty-proposed;
urgency=medium

  * Initial release (LP: #1465706, LP: #1431753).
  * Changes in this backport, compared to wily:
- Make nvidia-libopencl1-$flavour the default alternative dependency
  instead of ocl-icd-libopencl1 (which is still in universe in trusty).

 -- Alberto Milone alberto.mil...@canonical.com  Wed, 29 Jul 2015
12:30:05 +0200

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation