I also hit this within an hour of installing hippo (21.04) on a new
machine, having made zero configuration changes anywhere. My guess is
that it happened when I accidentally mashed a few keys at once (which
may have included the windows key)...?
--
You received this bug notification because you
Public bug reported:
During apt install of the python3-jmespath package the following is
displayed:
Setting up python3-jmespath (0.9.4-2) ...
/usr/lib/python3/dist-packages/jmespath/visitor.py:32: SyntaxWarning: "is" with
a literal. Did you mean "=="?
if x is 0 or x is 1:
I ran into the same issue.
Here's what appears to be happening:
1. ogg123 has a latent bug in how it handles a pthread mutex-- it always tries
to unlock that mutex before exiting, even if the mutex is unlocked already.
glibc on older CPUs tolerates this, which is why nobody has noticed until
Duplicate of bug #626025?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/583271
Title:
The value of Energy when full is much higher than the value of
Energy (design) so the percentage calculation
Same symptom on a Thinkpad T420s with a Sanyo 42T4845 battery: the
indicator always shows 10% on a full battery and energy-full is 10x what
it should be. Killing upowerd temporarily sometimes restores the right
value.
However, I have also seen upower report all values as 10x (energy,
Here is a workaround for now. Put this in ~/.gimp-2.4/gimprc:
(show-brush-outline no)
I can confirm this works, but as you might guess, the whole brush
outline goes away. When Gimp 2.4.1 is released, a slightly more
sophisticated workaround will be present, where you can use:
(xor-color
** Also affects: xserver-xorg-driver-ati
Importance: Undecided
Status: New
--
Gimp brushes leave garbage pixel trails
https://bugs.launchpad.net/bugs/156556
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Someone saw this on Fedora:
http://www.fedoraforum.org/forum/showthread.php?t=168979
It has a tantalizing reference to debian having identified and fixed the
problem, but there's not enough information to identify what package was
fixed. It does say, however, that an update landed in debian sid
I have heard a rumor that this may have been encountered by Debian, and
that it only appears in systems that have been upgraded (i.e. not clean
installs), and also that the bug is actually due to xorg and gtk
miscommunicating.
So far I have been unable to find any proof of this: mailing list
Here is a bug listing at gnome.org that describes the problem in a
little more detail, and mentions a patch to Gimp that fixes the problem
(though the underlying bug seems to be in xorg or gtk).
http://bugzilla.gnome.org/show_bug.cgi?id=421466
--
Gimp brushes leave garbage pixel trails
Here's a bug report at debian, and a mailing list message from gimp-
user.
Looks like it's related to the ati video drivers; both I and the
reporter have the same video card: an ATI Radeon 7000 / VE / RV100.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=433230
Public bug reported:
Binary package hint: gimp
I just upgraded from Ubuntu 6.10 to 7.10, and now Gimp has a horrible
display artifact: every tool that uses a brush leaves bright green pixel
trails across the image. Though they go away when the window refreshes
(i.e. minimize and then restore
I did some home-directory cleanup right after upgrading to Gutsy. I
know that I deleted some ~/.directories like ~/.local, and ~/.cache,
assuming programs would recreate whatever they need. The next day I
awoke to trackerd using over 1GB of memory. Did the one cause the
other? It's impossible
I have attached the screenshot.
** Attachment added: Screenshot1.png
http://launchpadlibrarian.net/10164784/Screenshot1.png
--
Gimp brushes leave garbage pixel trails
https://bugs.launchpad.net/bugs/156556
You received this bug notification because you are a member of Ubuntu
Bugs, which is
14 matches
Mail list logo
