Tested in Firefox 22 - works great. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/703191
Title:
BGR-ordered subpixel font rendering appears broken/nonfunctional in
Gnome/GTK+
To manage n
While we await that mythical update I'll gladly take this one. Many
thanks.
I'll test this when it filters down into a build, but as noted upthread,
applying this patch and compiling locally works just fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Can we get this fixed please? It is a real eyesore to those of us with
B-G-R striped monitors.
It's a one-line patch: a simple "break" statement missing in the Cairo
font renderer. The Cairo patch has been available for well over a year,
and it has been fixed in Cairo releases since 1.11.4 (2012
Affects me too, with very much the same configuration as the original
poster: Ubuntu 12.04 64-bit, unity, nvidia.
The corruption most often affects the unity left-side vertical icon
panel, but also frequently the top menu bar, and from time to time also
open application windows. Pretty much every
The rendering bugfix is incorporated into cairo 1.11.4, released
2012-03-12, so that's a little bit of progress I suppose.
For whatever reason, though, now that I'm running Ubuntu 12.04 beta,
even my lovingly hand-patched and compiled version of Cairo doesn't seem
to resolve this problem anymore.
This is a longstanding, obvious, easily verifiable bug with a trivial
fix, as cited above.
It's still present in FF10 final. Can we get this implemented PLEASE?
I have to manually patch and compile each Firefox release. I'm sure
others would benefit from having the fix integrated into the sourc
Perhaps unsurprisingly, this bug can be fixed by making the same patch
that fixes the system-level cairo library.
I manually patched firefox 8.0b3 to test. The patch goes into the cairo
version that's embedded in the firefox source, at
[RELEASE]/gfx/cairo/cairo/cairo/src/cairo-ft-font.c.
--
You
Confirmed in Firefox 7.0.1 here -- I'm the original reporter on Ubuntu
bug 703191 (listed under "See Also"), and I have manually patched Cairo
on my own system using Ingo Ruhnke's patch (attached to freedesktop.org
bug 40456). This solves the problem system-wide EXCEPT in Firefox.
--
You receive
The cairo patch in freedesktop.org solved the problem for me.
I manually applied the patch in cairo 1.10.2, built it and manually
installed it over the packaged version in Natty.
BGR-ordered subpixel font rendering now looks fine systemwide, and
switching back and forth between RGB and BGR has th
Thanks for the additional observation, Ingo, and also for confirming my
original report (despite the fact that resolving this bug won't really
help you one way or the other, given your two-monitor situation).
I tested the recently released Natty Alpha 3 Live CD, and it too shows
this same problem.
** Attachment added: "Screenshot-galculator-vrgb-crop.png"
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/703191/+attachment/1833346/+files/Screenshot-galculator-vrgb-crop.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Attachment added: "Screenshot-galculator-vbgr-crop.png"
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/703191/+attachment/1833345/+files/Screenshot-galculator-vbgr-crop.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Attachment added: "Screenshot-galculator-vrgb.png"
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/703191/+attachment/1833344/+files/Screenshot-galculator-vrgb.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** Attachment added: "Screenshot-galculator-bgr-crop.png"
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/703191/+attachment/1833343/+files/Screenshot-galculator-bgr-crop.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "Screenshot-galculator-rgb-crop.png"
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/703191/+attachment/1833342/+files/Screenshot-galculator-rgb-crop.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm a little dismayed at the lack of action here, because Natty Alpha 2
just came out, and I verified it has exactly the same problem (following
booting from the AMD64 LiveCD).
I have objectively verified my findings. There is NO DIFFERENCE between
RGB-ordered font rendering and BGR-ordered font
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/703191
Title:
BGR-ordered subpixel font rendering appears broken/nonfunctional in
Gnome/GTK+
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
Public bug reported:
I'm filing this bug against gtk+, but frankly I don't know exactly what
package is the culprit. It's occurring somewhere between the Gnome
"Appearance" preference panel and freetype, I suppose.
In summary, subpixel-antialiased font rendering to a Blue-Green-Red
(BGR) ordere
Well, I can't explain why, but my keyboard is BACK after the latest
round of upgrades. I don't see anything in the changelog for kernel
2.6.35-22.25 that suggests why, and nothing bluez-related has been
upgraded other than pulseaudio.
--
Bluetooth: pairing Apple Wireless keyboard constantly disc
I will add that in my case, there's nothing in dmesg, and when I
manually try to reconnect via the blueman UI, after a few seconds I get
a "Host is down (112)" error message.
--
Bluetooth: pairing Apple Wireless keyboard constantly disconnects and reconnects
https://bugs.launchpad.net/bugs/630001
Argh! After many, many months of fighting with the Apple Bluetooth
Keyboard to get it to connect reliably -- and failing -- everything was
finally fixed at the beginning of this year with the discovery that
manually loading the hid_apple module did the trick.
After that, the connection was bullet
*** This bug is a duplicate of bug 421660 ***
https://bugs.launchpad.net/bugs/421660
I do NOT think this is a duplicate of bug #421660. Aside from having
been reported seven months earlier, the symptoms are very different:
#421660 concerns the lack of accessibility of the gksu modal dialog i
Good work, jeroen. I too can confirm the solution, and it worked at the
login screen as well. There was no need to regenerate the initrd.
I agree with RishiRamraj that this falls into the "workaround" category
(and isn't a real fix) until changes are made to get this happening
automatically. Ca
I will confirm this bug is still present in the 9.10 final release. I'm
using the Apple BT aluminum keyboard (first edition) on a Ubuntu 9.10
64-bit system with generic pc hardware.
Like the previous posters, I can get it paired, and it works initially,
but not following a reboot.
I have to log
This bug continues to exist in 9.04, Jaunty final. Nothing has changed
as far as I can tell.
It SURE would be nice to have this fixed, or at least to have the
maintainer weigh in on when someone might take a look.
On my keyboardless system, I still end up having to power-down to get
out of the U
I agree with Michael: If the problem is triggered by the composited
password window, then forget the fanciness. I just want a gksu that
works. I don't care if there's a titlebar.
For the record, I get the same effect Michael does in the screenshot
(gksu_window_mode_compiz.png). The border and
Update:
Seems to result from some interaction between compiz and gksu.
If I use fusion-icon to switch to metacity as WM, even temporarily, then
invoke gksu/gksudo, then there is no problem.
And I can switch right back to compiz.
--
Assistive techologies: password dialogs as normal window + ons
I can confirm.
In Intrepid, on a Samsung Q1 UMPC (the original Celeron-M 900 version),
gksu fails almost every time it runs -- which makes various
administrative tasks difficult to perform, obviously.
The Q1 is a keyboard-less tablet "ultra mobile PC." I have "password
dialogs as normal windows"
There is a workaround -- an ugly one, but it works for me and it's
simple.
If I just manipulate the user drop-down list on the "Authenticate"
dialog, by just clicking on it, and then clicking somewhere else to
close the list, then the rest of the desktop becomes accessible,
including the Onboard o
Ah -- thanks for the clarification. The fix sounds great. I look
forward to trying it.
As for Feisty+1, the developers of OSS have indicated a willingness to
collaborate with Ubuntu on how restricted-manager works with OSS. You
may contact Dev Mazumdar ([EMAIL PROTECTED]) or Hannu Savolainen
([
Confirmed.
The ALSA ice1712 module exports an alias of
pci:v1412d1712sv*sd*bc*sc*i* -- exactly the correct scope.
The comparable OSS envy24 module exports no alias whatsoever, and I
don't know why. That is the case for each of the OSS modules I spot-
checked (I didn't look at all of them
I wouldn't be too quick to close this -- I'm getting the same error with
kvm-18 compiled from source (Feisty AMD64 2007-03-31 daily image, kernel
2.6.20-13). The same kvm release worked fine on Edgy, kernel 2.6.17-11
(same system).
It's possible this has nothing to do with the kvm package, but ra
I'll do a little thinking-out-loud here myself:
I agree an overly-generous modalias might potentially cause this -- I'm
curious and will follow up on that tonight to see what modinfo has to
say on the OSS modules. If it is the case, I will email 4Front myself
and ask them to consider changing tha
Screenshot attached. The only modules actually "in use" (and
appropriately so) are the NVIDIA accelerated graphics driver (not seen
in this shot), the Open Sound System 'envy24' driver module (not seen),
the OSS 'hdaudio' driver module (not seen), the OSS 'ossusb' driver
module (not seen), and the
Attached is a single file containing output from both "restricted-
modules --list" and "lsmod".
** Attachment added: "module-listings.txt"
http://librarian.launchpad.net/7150143/module-listings.txt
--
restricted-manager shows all unused OSS modules as "needs computer restart"
https://bugs.lau
Right, I'm talking about installing non-free OSS after installing
Ubuntu, and then looking in restricted-manager. I am using OSS because
ALSA doesn't support one of my audio interfaces. And the kernel is
stock from the installation CD image.
OSS seems to install a module for *every* known sound
Public bug reported:
Binary package hint: restricted-manager
In Feisty restricted-manager 0.17 (from the 2007-03-31 daily cd image),
all unused Open Sound System (OSS) modules not required on my system
continuously show up as "needs computer restart." The ones that
correspond to real hardware do
37 matches
Mail list logo
