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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/163918
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639180
Title:
n
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.
--
Yo
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 \
@eggert-cs, have you tried the "ppa:graphics-drivers/ppa" PPA?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639180
Title:
no login possible after update to nvidia 304.132
To manage notifications
@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 Ub
@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 you
@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 instal
@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
Bugs, which is subscribed to Ubuntu.
htt
@skgary, you type it wrongly.
You should type:
sudo
apt-get
install
nvidia-304=304.131-0ubuntu3
I put each word on separate line. Put them into ONE line, inserting spaces
between them. But NO OTHER spaces should be inserted.
(Don't insert spaces within "nvidia-304=304.131-0ubuntu3".)
--
You r
The workaround of using nvidia-304.134 from the graphics-drivers ppa
works fo me too (Ubuntu 16.04.1 LTS, linux x86_64 4.4.0-53-generic).
@skgary, you mean that you can't do `sudo apt-get install
nvidia-304=304.131-0ubuntu3`?
--
You received this bug notification because you are a member of Ubun
*** 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)
*** This bug is a duplicate of bug 1639180 ***
https://bugs.launchpad.net/bugs/1639180
I discovered this is duplicate of #1639180.
** This bug has been marked a duplicate of bug 1639180
no login possible after update to nvidia 304.132
--
You received this bug notification because you are
** Summary changed:
- Handling $ORIGIN strings within DT_NEEDED sections
+ Handling $ORIGIN strings within DT_NEEDED entries
** Description changed:
What documentation says:
- "$ORIGIN sequences within a DT_NEEDED entry or path passed as a parameter to
dlopen() are treated as errors."
- (From
Public bug reported:
What documentation says:
"$ORIGIN sequences within a DT_NEEDED entry or path passed as a parameter to
dlopen() are treated as errors."
(From "System V Application Binary Interface - DRAFT - 10 June 2013" / "Chapter
5 - Program Loading and Dynamic Linking" / "Dynamic Linking"
** 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 c
Note (tiny mistake in previous comment):
- - 'apt list --kept-back' to show packages on hold (= 'apt-mark showhold');
+ - 'apt list --kept-back' to show packages on hold that can be manually
upgraded (⊆ 'apt-mark showhold');
(The fact that the package is on hold, per se doesn't necessary mean
t
Note (tiny mistake in previous comment):
- - 'apt list --kept-back' to show packages on hold (= 'apt-mark showhold');
+ - 'apt list --kept-back' to show packages on hold that can be manually
upgraded (⊆ 'apt-mark showhold');
(The fact that the package is on hold, per se doesn't necessary mean
tha
Sorry, it should be 'Thus' (a.k.a 'Therefore') instead of 'This' in the
last sentence.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641303
Title:
Wish: apt shouldn't show kept-back packages within
IMHO:
'apt list' should have at least 2 keys:
- 'apt list --upgradable' to show packages that will be upgraded;
- 'apt list --kept-back' to show packages on hold (= 'apt-mark showhold');
- 'apt list --upgradable --kept-back' to show both (i.e. union).
And 'apt update' should report only '--upg
Public bug reported:
Should apt consider kept-back packages as upgradable? Current state is:
1. Within 'apt dist-upgrade' it doesn't.
2. Within 'apt list --upgradable' and 'apt update' it does.
For example:
$ sudo apt update
> [...]
> Fetched 94,5 kB in 1s (66,0 kB/s)
> Reading package lists...
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640451
Title:
ksplashqml crashed with SIGABRT in QMessageLogger::fatal()
To manage notifications ab
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
2.4
Public bug reported:
In the man page of "objcopy" the "--strip-unneeded" option:
- is described in OPTIONS section;
- but is forgotten in SYNOPSIS section (don't confuse with
"--strip-unneeded-symbol=" and "--strip-unneeded-symbols=", which aren't
forgotten).
$ lsb_release -rd
Description:U
I suppose, that this info isn't required for this wish.
** Description changed:
+ I'm using KUbuntu 16.04 with linux-image-4.2.0-19-generic.
+
The linux-image-*.*.*-*-generic packages have set of dependencies,
recommendations and suggestions.
However, for some reason, the thermald recommend
Public bug reported:
The linux-image-*.*.*-*-generic packages have set of dependencies,
recommendations and suggestions.
However, for some reason, the thermald recommendation isn't put there, but
instead is put as recommendation for linux-image-generic meta-package.
Put thermald as recommendatio
Public bug reported:
language-pack-kde-en depends on k3b.
Thus I can't remove k3b (I have no DVD drive) without removing
language-pack-kde-en.
More exactly: language-pack-kde-en strictly depends on k3b-i18n, and
k3b-i18n strictly depends on k3b.
** Affects: language-pack-kde-en (Ubuntu)
Im
Yes,
https://alioth.debian.org/tracker/index.php?func=detail&aid=314875&group_id=100114&atid=413095
is the newer version of the same script.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1388423
Title
Public bug reported:
In short, how it looks for me as a user:
I have dctrl-tools package installed. I open bash and type "sudo apt-get remove
dctrl-tools".
Then (for example, in the same bash) I type "sudo dpkg --purge cr", and
this is what I get:
--begin quote--
sasha@sasha-netbook:~/Downloads
Importance: very low, this is feature request.
** Tags added: apt-mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1388423
Title:
Please package completions for apt-mark into bash_completion
To
Public bug reported:
In /usr/share/bash-completion/completions/ there are autocompletions for
apt-get, apt-cache and apt-build, but no apt-mark.
I've implemented one (see attach).
** Affects: bash-completion (Ubuntu)
Importance: Undecided
Status: New
** Tags: apt-mark
** Attachm
** Attachment added: "Minimal ~/.inputrc that causes bug to appear"
https://bugs.launchpad.net/ubuntu/+bug/1202760/+attachment/3741431/+files/.inputrc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Public bug reported:
What I do:
1. Start interactive bash (either by launching Konsole, or by pressing
Ctrl+Alt+F1 and filling login/password).
2. Plug AC adapter in (if it is not plugged) OR plug it out (if it's plugged).
What happens:
Bash asks me "Display all 4354 possibilities? (y or n)".
Ac
33 matches
Mail list logo
