Alberto, thank you sooo much, that is great news. Especially since there seems
to be another wave of bitter comments and confusion on lp:1268257 . Two
questions:
- Am I understanding correctly that you'll fix the problem for the 331 driver
AND that we'll have the option of using the 340 or 346 d
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?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.
** Also affects: nvidia-graphics-drivers-331-updates (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subsc
The workaround in post #100 works at the level of the individual user,
but it's a bit flawed in the sense that it will be undone every time the
driver (not the kernel) is updated. In addition, if I understand the
legal aspects correctly (IANAL), it does not qualify as a fix because
Canonical cannot
As long as the current LTS (i.e. 331) drivers are not fixed, I think it
is wrong to set the status for nvidia-drivers-ubuntu to "Fix Released".
Can someone with the necessary permissions please undo the status change
by royalsabz (mehrshad-5843) ? And set the importance to "High", while
you're at i
Oh come on, this is completely wrong! This bug is *NOT * fixed for the
331 driver (and also not for "NVIDIA Drivers Ubuntu" because 331 is the
most recent driver available in 14.04 LTS (Trusty)). Why doesn't
launchpad allow to correct this mistake by setting it back the
"Confirmed"??? If the devs a
@ Sébastien BOUISSET (sbouisset): your're using the non-LTS branch of
Ubuntu. I've been repeating ad nauseam during the last few weeks that
the issue is NOT FIXED in the LTS branch, which uses the 331 driver, and
is popular with professional users.
--
You received this bug notification because yo
This is my current Hanlon-compliant(*) theory as to why the fix is not
backported:
- Anyone looking up this bug will land at the top of the page, where the status
is displayed. A small percentage will make random changes to the status by lack
of attention or understanding.
- This bug report is v
@Bill Turner, wb4alm (wb4alm): FYI, "Triaged" means that a bug
supervisor has determined that the bug report contains all necessary
information to start working on it. This is in my opinion the (only)
correct status for nvidia-graphics-drivers-331 and nvidia-graphics-
drivers-331-updates (note that
Dear Alberto and others, Could you please please backport this fix to
the 331 driver, which is the most recent one available for 14.04 LTS
(Trusty)? Or at the very least explain why this might not be as trivial
as it sounds? This bug impacts a massive amount of Trusty users, and
failing to get a gr
@Adam Koczur (sbv): nice, that is a step in the right direction!
However, I have to point out that pretty much everyone who is affected
by this bug is running the 3.13 kernel that comes with Trusty; those who
are running newer (non-LTS) kernels all have newer nvidia drivers
(except the ones with le
@Adam Koczur (sbv): you do indeed appear to have the wrong bug report;
the bug we're (effectively) talking about *here* is also triggered by
331.113-0ubuntu0.0.4 from nvidia-331-updates (it's what I'm running) and
is described more accurately at lp:1431753 . In case you wonder why the
heck this is
Fix confirmed on 2 very different machines both running Ubuntu 14.04
"Trusty" with the 3.13 kernel. Detailed notes:
AMD workstation with only a discrete nvidia GPU (nothing else)
Synaptic complained about conflicts when selecting updated driver
For anyone who didn't get the message, fixed versions of the the 440
driver (with legacy GPU support) and the 446 driver (which only supports
relatively recent GPUs) are now available in the official trusty-
proposed repository. A few people (including me) have reported trying
them with the 3.13 ke
Mat, I am happy you got past your blank-screen problem, even though the
things mentioned in my previous post may or may not have played a role
in solving it.
To be perfectly clear toward other people who come across this
discussion, the points (1)-(4) in my previous post DO NOT represent a
step-by
Sezer, you're not going to believe this, but the issue you're having
with steam has nothing to to with the nvidia driver, but is caused by a
completely unrelated kernel bug that just happened to occur at the same
time people started testing the fix for the nvidia driver; see
lp:1479093 . The fix fo
Sorry, but 331 is still the most recent driver supported by the LTS
release. While "LTS" doesn't seem to mean much to Canonical anymore, at
least try to keep up the appearance. Especially for a bug that affects
thousands of users, not all of whom will be willing/skilled to upgrade
their kernels (an
Can someone please, please apply the fix that worked for 346 and 340 to
331 also? Or at the very least explain why this might not be as trivial
as it sounds? As I pointed out in lp:1431753, 331 is still the most
recent driver supported by the current LTS release. This is a bug that
affects thousand
@ awol (awol99) : I'll do you one better. At my workplace, we just
started the process of gradually upgrading all our machines from 12.04
Precise to 14.04 Trusty. After starting with a few, we've hit this bug.
Yesterday, I had a discussion about it with the person responsible for
software maintenan
You might have meant to say 14.04. Which is still supported till March
1019. That's a very long time for Canonical to claim to be supporting
something that's so broken...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-dri
@stephen (stephen-puttick) : I don't think that's needed; it is my
understanding from lp:1431753 that this bug is already fully
characterized, and fixed for the 340 and 346 drivers in Utopic and
Vivid. Furthermore, the fact that the fix appears to be performed at the
level of the metadata strongly
** Changed in: nvidia-drivers-ubuntu
Assignee: done (mnmarkonissinen) => (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu.
https://bugs.launchpad.net/bugs/1268257
Title:
nvidia-331
The fact that there are so many accidental edits to the status of this
bug seems to indicate it's getting large numbers of views. Canonical,
your LTS user base is bleeding. For pity's sake, make it stop.
Talking about accidental edits, can someone please, please set the
status for "NVIDIA Drivers
Confirmed with Canon MP520 on Precise . Tested very thoroughly with all
different combinations of flags.
Didn't work: lpadmin -p Canon-PIXMA-MP520 -o usb-unidir-default=true
Didn't work: lpadmin -p Canon-PIXMA-MP520 -o usb-no-reattach-default=true
Did work: both of the above flags set at the same
This is nothing short of appalling:
- Issue still present in LibreOffice on Precise (LTS)
- It's been 7 (seven) years
- Currently, the workaround is to edit a file that gets overwritten with every
update: http://ubuntuforums.org/showthread.php?t=1645957&p=11891452#post11891452
The attached patch
** Bug watch added: freedesktop.org Bugzilla #49987
https://bugs.freedesktop.org/show_bug.cgi?id=49987
** Also affects: df-libreoffice via
https://bugs.freedesktop.org/show_bug.cgi?id=49987
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are
*** This bug is a duplicate of bug 1026356 ***
https://bugs.launchpad.net/bugs/1026356
** This bug has been marked a duplicate of bug 1026356
Bad validation on Scales box on Axis (chart properties)
--
You received this bug notification because you are a member of Desktop
Packages, which i
I linked this to upstream bug #49987 , but on second thought, upstream bug
#57697 contains more recent and relevant info (they ought to mark one a
duplicate of the other).
https://www.libreoffice.org/bugzilla/show_bug.cgi?id=57697
Between the 2 upstream reports, it appears the bug occurs in 3.5.
Warning: launchpad's autogenerated hyperlinks in my previous post are
wrong; the explicit "https://"; link is the only correct one.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/102
There seems to be a regression; the bug came back in Thunderbird 13.0.1
and 14.0 (what I have here) on Lucid. Here's the upstream bug report:
https://bugzilla.mozilla.org/show_bug.cgi?id=541130
** Bug watch added: Mozilla Bugzilla #541130
https://bugzilla.mozilla.org/show_bug.cgi?id=541130
--
** Also affects: thunderbird via
https://bugzilla.mozilla.org/show_bug.cgi?id=541130
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/4
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
*bump*
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1431753
Title:
Nvidia binary driver FTBS due to DKMS layer violation
Status in nvidia-graphics-drive
No, this is *not* fixed for 331 and 331-updates; in fact, nothing has
changed. The "fix released" status presumably was set by yet another
inattentive user who landed onto this Launchpad page after getting a
whoopsie error. Unfortunately, the status cannot easily be reverted to
"triaged" because of
34 matches
Mail list logo
