Movinge the cursor over the text "In that wiki entry they talk about using the" makes it bold in this page http://armin762.wordpress.com/2013/12/07/aarch64arm64-in-gentoo/ Scolling the page so the text isn't visible resets the text to normal. Using today git version of the intel driver. From xorg.log I got: I have seen this on and of but here it is very visible [ 19.029] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 4000 [ 19.029] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx [ 19.029] (II) intel(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 [ 19.029] (==) intel(0): Depth 24, (--) framebuffer bpp 32 [ 19.029] (==) intel(0): RGB weight 888 [ 19.029] (==) intel(0): Default visual is TrueColor [ 19.029] (**) intel(0): Option "AccelMethod" "sna" [ 19.030] (**) intel(0): Framebuffer tiled [ 19.030] (**) intel(0): Pixmaps tiled [ 19.030] (**) intel(0): "Tear free" disabled [ 19.030] (**) intel(0): Forcing per-crtc-pixmaps? no [ 19.030] (II) intel(0): Output VGA1 has no monitor section [ 19.030] (II) intel(0): Output HDMI1 has no monitor section [ 19.030] (II) intel(0): Output DP1 has no monitor section [ 19.030] (II) intel(0): Output HDMI2 has no monitor section [ 19.030] (II) intel(0): Output HDMI3 has no monitor section [ 19.030] (II) intel(0): Output DP2 has no monitor section [ 19.030] (II) intel(0): Output DP3 has no monitor section [ 19.030] (II) intel(0): Output VIRTUAL1 has no monitor section [ 19.030] (--) intel(0): Output HDMI3 using initial mode 1920x1200 on pipe 0 [ 19.030] (==) intel(0): DPI set to (96, 96) [ 19.030] (II) Loading sub module "dri2" [ 19.030] (II) LoadModule: "dri2" [ 19.030] (II) Module "dri2" already built-in [ 19.030] (==) Depth 24 pixmap format is 32 bpp [ 19.032] (II) intel(0): SNA initialized with Ivybridge (gen7, gt2) backend [ 19.032] (==) intel(0): Backing store disabled [ 19.032] (==) intel(0): Silken mouse enabled [ 19.032] (II) intel(0): HW Cursor enabled [ 19.032] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message. [ 19.032] (==) intel(0): DPMS enabled [ 19.032] (II) intel(0): [DRI2] Setup complete [ 19.032] (II) intel(0): [DRI2] DRI driver: i965 [ 19.032] (II) intel(0): direct rendering: DRI2 Enabled [ 19.032] (==) intel(0): hotplug detection: "enabled" [ 19.032] (--) RandR disabled [ 19.046] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer [ 19.046] (II) AIGLX: enabled GLX_INTEL_swap_event [ 19.046] (II) AIGLX: enabled GLX_ARB_create_context [ 19.046] (II) AIGLX: enabled GLX_ARB_create_context_profile [ 19.046] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile [ 19.046] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control [ 19.046] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects [ 19.046] (II) AIGLX: Loaded and initialized i965 [ 19.046] (II) GLX: Initialized DRI2 GL provider for screen 0 [ 19.048] (II) intel(0): switch to mode 1920x1200@60.0 on HDMI3 using pipe 0, position (0, 0), rotation normal, reflection none [ 19.070] (II) intel(0): Setting screen physical size to 508 x 317
I have not observed this on any machine, gen2-gen7.
hmm I noted the same problem on another machine using a raedon card so I guess this isn't intel specific. Nor is it firefox 25, 24 has the same problem. Not sure what could cause this, maybe the infinality extension to freetype?
It sounds plausible that firefox renders that text with a different attribute during the hover, and fontconfig maps that to a different font resulting in different rendering. I would not have expected that though! Extracting the drawing commands and reconstructing exactly what went on would be like searching for the a fine needle in a large haystack. :|
hmm, I played with disable/enable infinality and the problem went away. Now I cannot get it back even:)
Hmm, I think this is notourbug, but I am not completely sure where the bug lies, so mark it closed until it reappears and we can identify the root cause.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.