[Ubuntu-x-swat] [Bug 1639180] Re: no login possible after update to nvidia 304.132

2017-02-20 Thread Oleksandr Pikozh
I confirm that after upgrade to 304.135-0ubuntu0~gpu16.04.1 my KUbuntu 16.04.1 LTS (linux x86_64 4.4.0-63-generic) no more logs in in graphics mode. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.

[Ubuntu-x-swat] [Bug 1639180] Re: no login possible after update to nvidia 304.132

2017-01-23 Thread Oleksandr Pikozh
Yes, I confirm that nvidia-304=304.134-0ubuntu0.16.04.1 is now not only in PPA, but also in xenial-{updates,security}/restricted repos. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.

[Ubuntu-x-swat] [Bug 1639180] Re: no login possible after update to nvidia 304.132

2017-01-13 Thread Oleksandr Pikozh
BTW: sudo apt-add-repository --remove ppa:graphics-drivers/ppa can (and should) be used instead of: sudo rm /etc/apt/sources.list.d/graphics-drivers-ubuntu-ppa-xenial.list (I just didn't know that apt-add-repository has --remove option.) And the recipe in #68-#69 in only for Ubuntu 16.04.1. --

[Ubuntu-x-swat] [Bug 1639180] Re: no login possible after update to nvidia 304.132

2017-01-13 Thread Oleksandr Pikozh
Yes, there is: 1. To try PPA: sudo add-apt-repository ppa:graphics-drivers/ppa sudo apt-get update sudo apt-get install nvidia-304=304.134-0ubuntu0.16.04.1 \ nvidia-opencl-icd-304=304.134-0ubuntu0.16.04.1 \ libcuda1-304=304.134-0ubuntu0.16.04.1 \

[Ubuntu-x-swat] [Bug 1639180] Re: no login possible after update to nvidia 304.132

2017-01-11 Thread Oleksandr Pikozh
@eggert-cs, have you tried the "ppa:graphics-drivers/ppa" PPA? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1639180 Title: no login possible after update to nvidia

[Ubuntu-x-swat] [Bug 1639180] Re: no login possible after update to nvidia 304.132

2016-12-20 Thread Oleksandr Pikozh
@skgary, as for `1`, as I've said, just do: sudo apt-get install nvidia-304=304.134-0ubuntu0.16.10.1 Or: sudo apt-get install nvidia-304 (it'll do the same as 304.134-0ubuntu0.16.10.1 is the newest version available to you). -- You received this bug notification because you are a member of

[Ubuntu-x-swat] [Bug 1639180] Re: no login possible after update to nvidia 304.132

2016-12-20 Thread Oleksandr Pikozh
@skgary, so, after you upgraded to 16.10, you now have two ways: 1. Either to install the newest version (134) from PPA. It's ok to try it. (Although, you said it doesn't work for you? Or it's just because wrong command line?) 2. Or to try quite dirty way of installing packages-for-16.04 into

[Ubuntu-x-swat] [Bug 1639180] Re: no login possible after update to nvidia 304.132

2016-12-20 Thread Oleksandr Pikozh
@skgary, yes, within 16.10 package versions are different. You have: (1) Either `sudo apt-get install nvidia-304=304.134-0ubuntu0.16.10.1` (or just `sudo apt-get install nvidia-304` as it's currently newest version available to you) to install the newest version (134). (2) Or try manually

[Ubuntu-x-swat] [Bug 1639180] Re: no login possible after update to nvidia 304.132

2016-12-20 Thread Oleksandr Pikozh
@skgary: 1. Have you put "=" after "nvidia-304" as suggested in Jan Herold (yzle)'s and my comments? 2. What it output of `apt-cache policy nvidia-304` (list of available versions)? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to

[Ubuntu-x-swat] [Bug 1640451] Re: ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

2016-12-12 Thread Oleksandr Pikozh
*** This bug is a duplicate of bug 1639180 *** https://bugs.launchpad.net/bugs/1639180 @frautukka, I'm not experienced in this... Propositions: (a) Report upstream? (I reported upstream to KDE, but they say it's not their issue; IMHO, they're right. We should report upstream to nvidia.) (b)

[Ubuntu-x-swat] [Bug 1640451] Re: ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

2016-11-15 Thread Oleksandr Pikozh
** Description changed: I'm unable to start plasma after nvidia nvidia-304 package upgrade (and reboot). The related KDE bug report is (at least, KDE crash handler (DrKonqi) considered my report a duplicate): https://bugs.kde.org/show_bug.cgi?id=372229. However, I discovered that the

[Ubuntu-x-swat] [Bug 1640451] Re: ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

2016-11-10 Thread Oleksandr Pikozh
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1640451 Title: ksplashqml crashed with SIGABRT in

[Ubuntu-x-swat] [Bug 1640457] Re: Xorg assert failure: Xorg: ../../nouveau/pushbuf.c:238: pushbuf_krel: Assertion `bkref' failed.

2016-11-09 Thread Oleksandr Pikozh
apt-cache policy libdrm-nouveau2 libdrm-nouveau2: Installed: 2.4.67-1ubuntu0.16.04.2 Candidate: 2.4.67-1ubuntu0.16.04.2 Version table: *** 2.4.67-1ubuntu0.16.04.2 500 500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status