Hi, since COVID-19 forced everyone to dig up old webcams, I thought I'd share
my "universal" workaround (sorry it's a clunky one):
Step 1 (one time): sudo apt install v4l2loopback-utils
Step 2 (redo after reboot): sudo modprobe v4l2loopback devices=1
exclusive_caps=1
Step 3 (before starting a
> disabling it increases power consumption of CPU at least by 80% in
idle state
That doesn't say much at all. _Suppose_ the CPU's power consumption is
5W in C6 state, and it indeed increases by 80%, then it becomes 9W, or
4W more. I could live with that - at least until a better fix becomes
Any progress on fixing this in the LTS version?
AFAIC this is a pretty high-profile security issue, and may not very
prudent to leave open for months after it's fixed upstream. Imagine the
storm of bad press if Microsoft or Apple were to pull something like
this - or even if this bug report
The good news: released fix works.
What's a bit worrisome, though, is that I had to *manually* run
sudo apt-get install update-manager update-manager-core python3-update-manager
in order to be able to use update-manager to install all other updates, some of
which were long overdue because of
I do get that you're trying to motivate someone to tweak the Ambiant-
Mate theme, and I do agree that it is not particularly comfortable to
use in Pluma. However, I don't think threatening to recommend another
distro will impress many people, given that all one needs to do is go
into
** Bug watch added: Non-GNU Savannah Bug Tracker #25731
http://savannah.nongnu.org/bugs/?25731
** Also affects: glob2 via
http://savannah.nongnu.org/bugs/?25731
Importance: Unknown
Status: Unknown
** Bug watch added: Debian Bug tracker #592412
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
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
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
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
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
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
*bump*
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753
Title:
Nvidia binary driver FTBS due to DKMS layer violation
To manage notifications about this bug go to:
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753
Title:
Nvidia binary
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
@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
@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
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
@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
@ 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
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
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 are
** Changed in: nvidia-drivers-ubuntu
Assignee: done (mnmarkonissinen) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1268257
Title:
nvidia-331-updates 331.38-0ubuntu3:
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
@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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
@ 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
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 it?
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
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 (and
** 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 Ubuntu
Bugs, which is subscribed
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
** 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 Ubuntu
Bugs, which is
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1026356
Title:
Bad
I had the same confusion as you. The only way I could make sense out of it all
is that Canonical did not obtain the same (non-transferable) distributor
license as Fedora core (and perhaps Debian), and instead must abide by the
end-user license license:
Thanks Marc! I suspected as much, but I thought I'd ask to be sure.
Since it's just released, sysadmins will be happy to find the above
clarification in this thread, which helps planning reboots.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Sorry for the naive question, but how severe are the security
implications of this? Does there exist a CVE, or otherwise a discussion
of the implications?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
This seems to have regressed in Precise (orage 4.8.3-1); I'm currently
experiencing the exact same problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/234071
Title:
Multiple windows open on
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=1645957p=11891452#post11891452
The attached patch
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
@Timo: I'm sorry for the clueless question, but can you please explain
why this is marked Fix Released for Precise? Precise is an LTS
version, and it was my understanding that as long as Precise is
supported, fixes to proper bugs should to be backported to the vanilla
(3.2) kernel line. Can you
Same problem with Intel HD Graphics 4000 on Xubuntu Precise
GPU: Intel Corporation Ivy Bridge Graphics Controller
Monitor: Viewsonic VX2025wm connected via HDMI
Kernel: 3.5.0-27-generic
X.Org X Server 1.11.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The above workaround will break every time the package is updated. The correct
workaround (in line with what Sam_ posted) is:
sudo update-alternatives --config javaws
and then choose the number in front of
/usr/lib/jvm/java-7-openjdk-amd64/jre/bin/javaws
Of course, this doesn't change the fact
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/411358
Title:
We tried autofs5.0.5 (natty) and autofs5.0.6 (oneiric), but the problem
persisted (on 32-bit Lucid). Then we tried autofs4.1.4 (karmic) - same
version as mentioned by dezibelz - and the problems went away (still on
32-bit Lucid). But it's obviously not ideal to be running an old
unsupported
By the way, importance = Wishlist ??? This is clearly a regression, ie.
something that used to work as expected, and now doesn't work as
expected anymore. Set the importance as low as you want, but please
don't make it look like a feature request!
Furthermore, the bug heat and # of people
We tried autofs5.0.5 (natty) and autofs5.0.6 (oneiric), but the problem
persisted (on 32-bit Lucid). Then we tried autofs4.1.4 (karmic) - same
version as mentioned by dezibelz - and the problems went away (still on
32-bit Lucid). But it's obviously not ideal to be running an old
unsupported
By the way, importance = Wishlist ??? This is clearly a regression, ie.
something that used to work as expected, and now doesn't work as
expected anymore. Set the importance as low as you want, but please
don't make it look like a feature request!
Furthermore, the bug heat and # of people
I would like to invite anyone reading this to consider installing the
(officially supported) package icedtea6-plugin and test whether their
frequently used Java web applications work with it. I know the open-
source Java implementations have been plagued by all kinds of
compatibility issues, but
For anyone struggling with this problem and searching for workarounds, the
upstream discussion is a good read. Apparently, it is possible to entirely
disable the housekeeping mechanism that is responsible for this problem:
https://bugzilla.gnome.org/show_bug.cgi?id=625609#c6
Doing so will
(1)
This bug was actually fixed as a side effect of the Ubuntu installer not
generating an xorg.conf anymore and letting X autodetect the hardware on
startup instead. X by default does not enable the Emulate3Buttons flag
(I speculate having this flag enabled in the default xorg.conf file was
an
Oops sorry, forget my previous post. In Jaunty and Lucid, X will start
up having the problem, but it will go away as soon as the middle button
is pressed (I'm on Lucid and use the middle button so often I forgot the
bug is still there).
Can anyone check whether the problem is still present in
Yes, my second post corrects the first. The fact that you're getting the
problem at all (I presume you're using Maverick?) pretty much confirms
Jakob Unterwurzacher's post of 2010-09-14 for the case of Maverick, so
we now know that fix committed is still the correct status. What I
don't fully
OK, can anyone check whether the problem is still present in Maverick?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/54191
Title:
Mouse button click delayed
--
ubuntu-bugs mailing list
I just wasted a full, extremely frustrating working day trying to find
why a complicated script involving in-house software and a tangle of
named pipes and background commands stopped working. Now it's after
midnight, I'm still at work, and I found out it's this. I'm right now
very tempted to give
I can confirm this issue in Lucid. Here's a workaround (in a terminal):
setxkbmap cz
setxkbmap us
--
cannot switch keyboard layout after reconnecting keyboard
https://bugs.launchpad.net/bugs/325200
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Ah, so you mean the new parameters are poorly documented???
BTW, xingmux only adds a header, it doesn't touch or affect the audio in any
way:
http://www.gstreamer.net/data/doc/gstreamer/head/gst-plugins-ugly-plugins/html/gst-plugins-ugly-plugins-xingmux.html
It would be clearer and technically
- This is not about bit rate, this is about quality. Getting a higher bit rate
does not automatically equal getting a higher quality. In fact, botching the
psychoacoustics model with a load of settings is a good recipe to get similar
or higher bit rates but a lower quality.
- For assessing
I attached a patch to be applied to /usr/share/gconf/schemas/gnome-
audio-profiles.schemas
What's the next step to get the bug solved?
The next step is to get this patch into Maverick. In an ideal world,
gnome-media should adopt it, then Ubuntu should simply pull it in from
the upstream repo's.
I also submitted a patch upstream which processes the file
gnome-audio-profiles.schemas.in.in , from which gnome-audio-profiles.schemas is
generated at compile time. The package maintainer is free to choose whichever
patch they find most convenient to use. ;)
The gstreamer bug is fixed but the implementation of this fix depends on
sound juicer - updated remote watch accordingly.
** Changed in: sound-juicer
Importance: Critical = Unknown
** Changed in: sound-juicer
Status: Fix Released = Unknown
** Changed in: sound-juicer
Remote watch:
BruceR, the things you're saying are simply not true. This is complex
business and I can understand it confuses you, but please don't make
stuff up. Browse Gnome Bugzilla (links at the end of this post). Look at
the source code. Encode the same sample with gstreamer and with
standalone LAME and do
** Also affects: gnome-media via
https://bugzilla.gnome.org/show_bug.cgi?id=619642
Importance: Unknown
Status: Unknown
--
Sound Juicer - MP3 quality doesn't change
https://bugs.launchpad.net/bugs/195483
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 54191 ***
https://bugs.launchpad.net/bugs/54191
@Fabio Marconi: I finally succeeded in installing Lucid (had some technical
problems doing so and not a lot of time to experiment). The bug is now present
when freshly starting X, but disappears as soon as
Bruce R, please read all the posts carefully. The lame element is known to be
broken, and has been superseded by lamemp3enc. Stop encouraging people to use
the lame element.
https://bugzilla.gnome.org/show_bug.cgi?id=494528
(FYI, Gabriel Bouvigne is one of the core LAME developers).
I did
OK, this might be getting confusing. Just a summary for people who are
new to this bug, and some suggestions for future directions:
- People initially filed this as a sound-juicer bug, while *at that time*, it
was actually a gstreamer bug; the lame element, which was responsible for
encoding
Thanks huug for posting the workaround. What a relief!
Looking at the workaround, fixing this seems trivial (ubuntu's install
scripts should no longer add Emulate3Buttons to xorg.conf unless a a
2-button mouse is detected). Thus, it qualifies as a papercut.
Changing status back to confirmed.
**
Seems that I was was a bit too quick on the trigger with my nobody
takes it serious statement. Sebastian Dröge essentially fixed the bug
upstream, and I have good hopes that it won't be long before the fix
comes to an Ubuntu repository near you :)
--
Sound Juicer - MP3 quality doesn't change
** Also affects: gstreamer via
http://bugzilla.gnome.org/show_bug.cgi?id=494528
Importance: Unknown
Status: Unknown
--
Sound Juicer - MP3 quality doesn't change
https://bugs.launchpad.net/bugs/195483
You received this bug notification because you are a member of Ubuntu
Bugs, which
They rightly marked that bug report resolved because (just like here on
launchpad) it was filed as a Juicer bug, while it really is a bug in the
gstreamer LAME plugin, not in Juicer. The actual bug that causes all our misery
is here:
http://bugzilla.gnome.org/show_bug.cgi?id=494528
The problem
@Christian Niemeyer: I believe vbr-mean-bitrate actually requests ABR
encoding, which conflicts with vbr-quality=4, the switch that requests
VBR encoding.
@tigerdog: Nyquist's theorem dictates that the lowpass frequency needs
to be significantly lower than half of the bitrate (44100) to avoid
In the spirit of open source, I would prefer the OOo developers to give
the user the choice of not embedding the fonts. They can bury it in some
menus and not set it by default so that it takes the users some effort
to shoot themselves in the foot.
That said, Ubuntu does offer a workaround:
Things are actually worse than they seem. As a matter of fact, LAME should only
be invoked with a handful of simple master options (like -V4), each of which
activates myriads of internal encoder parameters. Manually setting those
parameters through advanced switches will disrupt the carefully
Same problem here
Linux 2.6.24-19-generic #1 SMP i686 GNU/Linux
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4
server glx extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig,
Problem is, there are a lot of applications that come with shell scripts
that use /bin/arch, such as xammp, project looking glass, and MOE (the
Molecular Operating Environment). Eliminating /bin/arch breaks them all.
I really think the right thing to do is making the shell script that
invokes
To avoid breaking 3rd party shell scripts, a /bin/arch shell script that
invokes uname -m should be made part of util-linux .
** Changed in: util-linux (Ubuntu)
Status: Won't Fix = New
--
/bin/arch command missing in gutsy
https://bugs.launchpad.net/bugs/148511
You received this bug
Here's a thorough analysis of the bug, including workaround:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=184437
The creators of penguin-command have incorporated said workaround in their
version 1.6.11:
http://user.cs.tu-berlin.de/~karlb/penguin-command/
Summary: the crash is caused by
This is a duplicate of Bug #76179
Here's a thorough analysis of the bug, including workaround:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=184437
The creators of penguin-command have incorporated said workaround in their
version 1.6.11:
http://user.cs.tu-berlin.de/~karlb/penguin-command/
This bug has caused severe problems for me, as I only discovered its
existence 20 minutes before having to use a Feisty machine to give a
presentation that was made on Edgy using a powerpoint template. I found
no better solution than exporting it to PDF on an edgy machine and using
that PDF file
Mike, if there's anything anyone can do to help you getting that iso on
bittorrent, please ask. I'm going to mail a relative a live stick
monday, in the hope of getting them to use Linux, and it would be great
if they could use it in persistent mode.
--
feisty 20070210/herd5 persistent mode
Cal, that's interesting. The problem was not present in Feisty Herd 3.
If someone could copy vmlinuz and initrd.gz from a Herd 3 CD to /usb and
/usb/casper , it may cure the problem with less side-effects than you
experienced. I might even be a viable workaround altogether. It's really
annoying
Looks like I've been a bit too optimistic. I found a Herd 3 image and
applied the same procedure as described by Cal. The good news is that
persistence works, and that the logs written onto casper-rw indicate
that most of the hardware is correctly recognized and initialized. The
bad new is that
85 matches
Mail list logo
