I enabled proposed and updated.
During the upgrade I got a notification about "broken packages", but the
notification was removed.
After the upgrade System Settings/Software & Updates/Additional Drivers was
set to version 340.76 from nvidia-340-updates. However Nvidia X Server
Settings still said that the 331.113 driver was used.
Changed to version 346.82 from nvidia-346 (proprietary, tested).
The changed went OK and now Nvidia X Server Settings shows that the 346.82
driver is used.

2015-07-24 2:59 GMT+02:00 Vadim Peretokin <email address hidden>:

> Hi John,
>
> I think that after you add the repository, just doing an update will
> install the updated new packages.
>
> On Fri, Jul 24, 2015 at 10:46 AM, John Feole <email address hidden>
> wrote:
>
> > Hi Adam,
> >
> > I've never used this -proposed repo and had a coupla questions..(my son
> son
> > Sean Feole works for Canonical as well)
> >
> > I've been using Ubuntu for work/home use since 2006 or so when i was at
> Sun
> > and heard about it via Solaris Engineering...
> >
> > Anyway, I enabled the -proposed  repo, and I see a lot of stuff.  My
> > question is, can I deselect all the other stuff and only load the NVIDIA
> > 346 stuff?  Guess my real question is, what stuff do I need to install to
> > rectify this NVIDIA bug..?
> >
> > Thank You,
> > John Feole
> >
> > On Thu, Jul 23, 2015 at 4:15 PM, Adam Conrad <adconrad@0c3.net> wrote:
> >
> > > Hello Stefan, or anyone else affected,
> > >
> > > Accepted nvidia-graphics-drivers-340 into trusty-proposed. The package
> > > will build now and be available at
> https://launchpad.net/ubuntu/+source
> > > /nvidia-graphics-drivers-340/340.76-0ubuntu0.1 in a few hours, and then
> > > in the -proposed repository.
> > >
> > > Please help us by testing this new package.  See
> > > https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
> to
> > > enable and use -proposed.  Your feedback will aid us getting this
> update
> > > out to other Ubuntu users.
> > >
> > > If this package fixes the bug for you, please add a comment to this
> bug,
> > > mentioning the version of the package you tested, and change the tag
> > > from verification-needed to verification-done. If it does not fix the
> > > bug for you, please add a comment stating that, and change the tag to
> > > verification-failed.  In either case, details of your testing will help
> > > us make a better decision.
> > >
> > > Further information regarding the verification process can be found at
> > > https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you
> in
> > > advance!
> > >
> > > ** Changed in: nvidia-graphics-drivers-340-updates (Ubuntu Trusty)
> > >        Status: Confirmed => Fix Committed
> > >
> > > --
> > > You received this bug notification because you are subscribed to the
> bug
> > > report.
> > > https://bugs.launchpad.net/bugs/1431753
> > >
> > > Title:
> > >   Nvidia binary driver FTBS due to DKMS layer violation
> > >
> > > Status in nvidia-graphics-drivers-331 package in Ubuntu:
> > >   Confirmed
> > > Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
> > >   Confirmed
> > > Status in nvidia-graphics-drivers-340 package in Ubuntu:
> > >   Fix Released
> > > Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
> > >   Fix Released
> > > Status in nvidia-graphics-drivers-346 package in Ubuntu:
> > >   Fix Released
> > > Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
> > >   Fix Released
> > > Status in nvidia-graphics-drivers-331 source package in Trusty:
> > >   Triaged
> > > Status in nvidia-graphics-drivers-331-updates source package in Trusty:
> > >   Triaged
> > > Status in nvidia-graphics-drivers-340 source package in Trusty:
> > >   Fix Committed
> > > Status in nvidia-graphics-drivers-340-updates source package in Trusty:
> > >   Fix Committed
> > > Status in nvidia-graphics-drivers-346 source package in Trusty:
> > >   Fix Committed
> > > Status in nvidia-graphics-drivers-346-updates source package in Trusty:
> > >   Fix Committed
> > >
> > > Bug description:
> > >   Filing this against the 340-updates version but possibly the same
> > >   applies to older versions, too. The nvidia source package produces
> two
> > >   individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
> > >   The problem is that the DKMS build of the nvidia-uvm module runs
> > >   compile steps inside the nvidia modules build directory. This is
> > >   violating the DKMS assumption that each module can be build
> > >   independently (there is no way of describing cross-modules
> > >   dependencies and even more important, the autoinstall step after a
> new
> > >   kernel is installed will run the modules build in parallel).
> > >
> > >   Since nvidia and nvidia-uvm are very dependent on each other the
> right
> > >   course of action seems to be to combine both sources in one DKMS
> > >   module that produces two kernel modules (this is supported by DKMS).
> > >   For the transition this resulting dkms package needs to have a
> > >   breaks/replaces for the nvidia-uvm package.
> > >
> > > To manage notifications about this bug go to:
> > >
> > >
> >
> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions
> > >
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (1412105).
> > 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
> >
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1386990).
> https://bugs.launchpad.net/bugs/1431753
>
> Title:
>   Nvidia binary driver FTBS due to DKMS layer violation
>
> Status in nvidia-graphics-drivers-331 package in Ubuntu:
>   Confirmed
> Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
>   Confirmed
> Status in nvidia-graphics-drivers-340 package in Ubuntu:
>   Fix Released
> Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
>   Fix Released
> Status in nvidia-graphics-drivers-346 package in Ubuntu:
>   Fix Released
> Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
>   Fix Released
> Status in nvidia-graphics-drivers-331 source package in Trusty:
>   Triaged
> Status in nvidia-graphics-drivers-331-updates source package in Trusty:
>   Triaged
> Status in nvidia-graphics-drivers-340 source package in Trusty:
>   Fix Committed
> Status in nvidia-graphics-drivers-340-updates source package in Trusty:
>   Fix Committed
> Status in nvidia-graphics-drivers-346 source package in Trusty:
>   Fix Committed
> Status in nvidia-graphics-drivers-346-updates source package in Trusty:
>   Fix Committed
>
> Bug description:
>   Filing this against the 340-updates version but possibly the same
>   applies to older versions, too. The nvidia source package produces two
>   individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
>   The problem is that the DKMS build of the nvidia-uvm module runs
>   compile steps inside the nvidia modules build directory. This is
>   violating the DKMS assumption that each module can be build
>   independently (there is no way of describing cross-modules
>   dependencies and even more important, the autoinstall step after a new
>   kernel is installed will run the modules build in parallel).
>
>   Since nvidia and nvidia-uvm are very dependent on each other the right
>   course of action seems to be to combine both sources in one DKMS
>   module that produces two kernel modules (this is supported by DKMS).
>   For the transition this resulting dkms package needs to have a
>   breaks/replaces for the nvidia-uvm package.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions
>



-- 
Skickat från min nya mailadress