I can confirm "Daniel Pietrucha (texar)"'s experience.
Boot into the recovery console and run
# dpkg-reconfigure resolvconf
...
# apt update # worked immediately afterwards.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to n
For what it is worth - I have been through **almost** all of v304
(nvidia-current from USC) to latest xorg-edgers - in the end, here is
the only currently working option for me, pseudo-code;
purge-ppa ppa:xorg-edgers # purged the mesa libraries mentioned above among
other things.
apt-get purge
For what it is worth: I have pulled out nvidia-340 (xorg-edgers) and am
now down to 331.89 and settings from -340 - makes no difference.
"opencl_library=libnvidia-opencl.so.331.89"
in "~/.config/darktable/darktablerc"
$ darktable -d opencl
[opencl_init] opencl related configuration options:
[ope
I think this is something that is unrelated to nvidia and/or darktable -
I had updates of "lib-mesa" on 2014-07-10 (Thursday) and believe I
didn't run darktable much yesterday (Friday).
It seems as darktable at least gets a bit further, with "opencl_library
=libnvidia-opencl.so.1" in "~/.config/da
Public bug reported:
The following has a direct relation to not being able to save changed
settings:
nvidia-settings and the package files have an inconsistency that makes
it hard if not impossible to get any changes to keep more than for the
moment (at most).
The settings file: /etc/alternativ
> the smae and more:
http://askubuntu.com/questions/477553/ubuntu-14-04-cant-get-nvidia-prime-working/496873#496873
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1341140
6 matches
Mail list logo
