[SOLVED] XMBC Interface Rendering Issue

Hi all
After upgrading to gnome 3.8 I noticed that my XBMC interface started to behave strangely, mainly the fan art backgrounds started to flicker a couple of times before showing up and sometimes fails to load at all showing the default background image. This happens to other items such as text etc from time to time as well, but not as often. However once starting to play a video everything looks perfectly good.
I think it has to do with that I had to enable SNA for my Intel graphics driver when I upgraded to gnome 3.8 since this happens both in my Gnome session and in my XBMC session, is there anyone who have stumbled upon something similar and can offer me some help with this issue?
Thanks
// Lazze
Last edited by Lazze (2013-05-06 08:04:52)

Seems to have been fixed after fiddling around in the settings pane, not sure exactly what did it but I think it was related to the v-sync settings in menus.

Similar Messages

[Solved] Default interface routing issues

I have two network interfaces connected to my newly installed ArchLinux server, one LAN and one WAN connection. The trouble is that all traffic that is trying to connect to the wan interface gets no response, while the LAN connection work without any issue.
I am using udev to change my interfaces to lan0 and wan0, and i use netcfg to load the diffrent profiles.
Lan0 uses a static local ip 192.168.0.118 with 192.168.0.2 as gateway
Wan0 uses dhcp with dynamic ip from my ISP.
When i manually bring down my lan0 interface all my traffic goes through wan0 correctly, and it even responds to external calls.
So i belive the issue lies somewhere in the local routing?
I am trying to post all config files needed directly.
/etc/rc.conf
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# LANG in /etc/locale.conf takes precedence
# DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
# startup and during the boot process. If set to 'no', the C locale is used.
# HARDWARECLOCK: set to "", "UTC" or "localtime", any other value will result
# in the hardware clock being left untouched (useful for virtualization)
# Note: Using "localtime" is discouraged, using "" makes hwclock fall back
# to the value in /var/lib/hwclock/adjfile
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# Note: if unset, the value in /etc/localtime is used unchanged
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="sv_SE.UTF-8"
DAEMON_LOCALE="no"
HARDWARECLOCK="UTC"
TIMEZONE="Europe/Stockholm"
KEYMAP="sv-latin1"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
# Replace every !module by an entry as on the following line in a file in
# /etc/modprobe.d:
# blacklist module
# See "man modprobe.conf" for details.
MODULES=()
# Udev settle timeout (default to 30)
UDEV_TIMEOUT=30
# Scan for FakeRAID (dmraid) Volumes at startup
USEDMRAID="no"
# Scan for BTRFS volumes at startup
USEBTRFS="no"
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="yes"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="weed-devil"
# Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
# Wired network setup
# - interface: name of device (required)
# - address: IP address (leave blank for DHCP)
# - netmask: subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
# - broadcast: broadcast address (ignored for DHCP) (optional)
# - gateway: default route (ignored for DHCP)
# Static IP example
# interface=eth0
# address=192.168.0.2
# netmask=255.255.255.0
# broadcast=192.168.0.255
# gateway=192.168.0.1
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=
#interface=eth0
#address=
#netmask=
#broadcast=
#gateway=
# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"
# Enable these netcfg profiles at boot-up. These are useful if you happen to
# need more advanced network features than the simple network service
# supports, such as multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This requires the netcfg package
NETWORKS=(sluggy local)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
# If you are sure nothing else touches your hardware clock (such as ntpd or
# a dual-boot), you might want to enable 'hwclock'. Note that this will only
# make a difference if the hwclock program has been calibrated correctly.
# If you use a network filesystem you should enable 'netfs'.
DAEMONS=(syslog-ng !ufw !network net-profiles @alsa crond dbus sshd lircd sensors mysqld @ddclient @hddtemp httpd samba stunnel sabnzbd sickbeard)
/etc/network.d/sluggy
CONNECTION='ethernet'
DESCRIPTION='A basic dhcp ethernet connection using iproute'
INTERFACE='wan0'
IP='dhcp'
## for DHCPv6
#IP6='dhcp'
## for IPv6 autoconfiguration
#IP6='stateless'
/etc/network.d/local
CONNECTION='ethernet'
DESCRIPTION='A basic static ethernet connection using iproute'
INTERFACE='lan0'
IP='static'
ADDR='192.168.0.118'
GATEWAY='192.168.0.2'
output of route -nl
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.0.2 0.0.0.0 UG 0 0 0 lan0
0.0.0.0 85.24.137.1 0.0.0.0 UG 203 0 0 wan0
85.24.137.0 0.0.0.0 255.255.255.0 U 203 0 0 wan0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 lan0
I have had this server running Ubuntu for the past 2 years with the same setup on the NIC's and there everything worked, so I guess i have become a little lazy.
*EDIT* Updated my post with "code" block instead of quote
Last edited by kurri (2011-11-01 22:07:14)

kurri, please edit your post.
When pasting code, please use [ code ] tags https://bbs.archlinux.org/help.php#bbcode
like this
It makes the code more readable and more convenient to scroll through.

[solved] Pango font rendering issues

I'm having issues with pango rendering of pcf fonts. I was trying to set up a new font for my awesome theme, but my choices are fairly limited because all the pcf fonts are rendered as some default font. So then I was going around googling the issue, and font that awesome renders fonts using pango. I then tried to use pango-view to view the pcf files, and it displayed the same default font. These fonts show up fine in xfontsel and they render properly in urxvt. In my googling I found someone on slackware was facing a similar issue back in 2010, but no solution was posted. Is this a known/common problem, and does anyone know a fix?
Edit: I'm not sure if this matters, but I also have freetype2-infinality installed from the AUR.
Last edited by HalfEmptyHero (2011-12-22 13:10:13)

Wow, I can't believe it was that simple. I had read my fontsconfig rules, however I'm new playing with fonts so none of it really meant anything to me when I originally read it, and I simply changed a few of the default fonts.. Going back over it now, it makes a lot more sense. Thanks for the help.

[SOLVED] TrueType font rendering issues

The problem I have run into is related to TrueType fonts.
I have a netbook that I reinstalled Arch on. I have an i3-wm setup with an i3bar populated by i3status.
I have multiple items that use unicode icons using the ttf-icons font.
I installed two fonts, gohufont and ttf-icons, albeit in an unusualy way. Due to external reasons, the machine doesn't have an Internet connection, so I had to install the fonts sort-of manually.
I downloaded the necessary files for the fonts and did it this way: the gohufont is in pcf format compressed with gzip. I looked at the fonts PKGBUILD file and manually repeated the installation process via `install(1)'. It was installed in /usr/share/fonts/misc. I did the same with ttf-icons and it is installed in /usr/share/fonts/TTF. After doing so, I updated the font cache via `fc-cache -fv'. Both fonts show up in the output of fc-list(1), Gohufont works fine, but the icons font doesn't.
The .i3status.conf contains format lines with icons from the font and the ones that were in the file when it was retrieved from the machine it was running on do actually show up and render in the bar. Upon adding a new unicode symbol from vim via ^v+u+<char code>, it turns into a representation of ^<letter> (the color highlight indicates that it is a unicode char). The other glyphs aren't being rendered properly in vim either, as opposed to all being fine previously. Instead of the actual glyph, they show up as a sequence of: <rounded square with a question mark in it><tilde><letter>[<another tilde><another letter>]<round square with a question mark> (probably the closing symbol). After saving the file, the untouched glyphs still show up properly, but the added ones show up as wide blocks with digit codes in them.
I am using gnome-terminal with a bash shell. Upon opening the font selection dialog in gnome-terminal and selecting the icons font, it is rendered as square blocks with numbers in them (thus, indicating that they didn't render properly).
I also attempted placing them in appropriate subfolders under ~/.fonts and then running `mkfontscale', `mkfontdir' in the ~/.fonts directory and then appending the directory to the font path via `xset fp+ ~/.fonts' and rehashing via `xset fp rehash' and updating the font cache again via `fc-cache -fv'. Still no dice.
I assume this might be a unicode problem, seeing as they're not being rendered in the terminal editor properly either.
xorg-font-util, xorg-font-utils, fontconfig and freetype2 are all installed.
Any tips or pointers would be highly appreciated.
Update: I had forgotten to set the default locale, so it was "C". I have set LANG to en_US.UTF-8 in /etc/locale.conf and have explicitely exported the LANG variable to the same value in my .bashrc. For some reason, it didn't apply after restarting X or logging out and in, so I set it using `localectl set-locale' and that did take effect. Now the old unicode glyph characters are all round squares with questionmarks inside them in the config file when opened in VIM and the new one is still a ^<letter>. The old ones render in the bar but the new one doesn't.
Update2: So apparently, a reboot was necessary for the changes to take effect system wide. The icons now appear in the terminal and everything. I just had to delete the ^<letter> representation of the broken one in the configuration file and re-enter it again. So this seems to be resolved. I will write down a step-by-step solution some time later (might be tomorrow, as I don't have the time at the moment). Anyone looking for a solution will probably find one here.
Last edited by gk (2014-03-17 12:31:11)

Please remember to mark your thread as [Solved] by editing your first post and prepending it to the title.

[SOLVED] firefox 4 rendering issues

Is anyone else having problems like this in firefox4?
several sites i visit turn out like this...
http://i.imgur.com/Zv5WZ.png
This is only happening for me in linux ... not windows7
Anyone know the cause of this?
Last edited by murfMan (2011-03-29 04:46:00)

Check your encoding setting.
From the menu bar >> View >> Character Encoding >> ...

Interface/Gamma issue - Display profiling

If you profile/calibrate your display (with professional software) to Gamma L* - darkish, grey boxes appear in some application-windows. Never happend in Tiger so I figure it's a Leopard issue.*
If you use Gamma 1.8, the Apple default, Photoshops windows (in my case) look perfekt. With Gamma 2.2 they're barely noticable (pretty much only if you know the boxes are there).
All the other settings you can choose while profiling - like temperature, luminance, chromatic adaption, profile-type etc. don't influence windows in this way - but as soon as you change the gamma those boxes appear.
I would very much like to know how you guys deal with it - do you profile your display to 1.8/2.2 (like a CRT) OR do you use L* and live with the boxes OR have you profiled your display properly/with L* but you don't have this nuisance? (!?)
Any help/info would be greatly appreciated.

*So here's what I think happens (+ my idea to solve the grey-boxes issue):*
Some applications use the monitor-profile to draw their interface. Like Photoshop and Graphic Converter. (The only 2 I've installed, I'm sure some video-editing-applications, even players are concerned that's maybe the reason some people think it's 'random'). I think these apps do so to immediately can reflect a change in the profile, without restart.
Now Mac OS X Leopard seems to not allow these applications to do so in certain parts of the interface. (Must be new, that's why there were no issues with Tiger) The window itself is drawn by the OS. That's the reason only elements like the text and buttons are affected.
And the problem is that the OS uses its 'Generic RGB Profile.icc' which contains Gamma 1.8. So if you calibrate your display with Gamma L* (which you really should do and most profiling-software does by default) those grey boxes appear in said applications.
The solution is easy. Replace the system-rgb-profile with one that supports L* - like the eciRGB profiles.
To do so you have to rename the .icc file in finder but also edit the information inside (which can be done with the ColorSync Utility). Then copy it to the System/Library/ColorSync/Profiles folder.
*After that the grey boxes dissapear and everything is back to normal.* There's some difference in the tabular data like the CMM and a chroma-entry, so you might want to re-write your display-profile just to make sure everything's alright.
I haven't seen anything yet but could imagine that the rendering of webpages in safari might be affected. Or rather some webbrowsers' without colour management. (Just a theory, hopefully not...)
*Problem 1:*
Some Adobe apps can see that the current system-profile is identical to your working-space-rgb and reset your rgb-choice to the Generic RGB profile after a restart. (Without changing the 'Colormanagement SYNC'd icon/setting.) This probably could cause trouble if you export or open files.
Solution:
Use a different profile for your system than your Adobe-RGB setting. I used the 'L-Star RGB v2' for the system and the 'eciRGB v2' for Adobe. They're technically identical but for some reason Photoshop and esp. Illustrator now respect my choices and don't reset anything. Works fine for me.
*Problem 2:*
Besides the aforementioned chroma-entry in the Apple default profile (which loss shouldn't cause any issues) there's also the localisation information. Because the profile is named differently in different languages of OS X. I haven't found anything causing trouble (probably because if the profile isn't found it resets back to the english version by default).
Solution:
This would be easy if someone knows about a .icc file editor. If we could add those localised names from the Apple profile no application would ever know. I've only found hexadecimal editors but won't put something like that on my machine, especially since everything works fine.
*I hope Apple comes up with a real solution soon, this seems like too much of a hack - considering the delicate nature of colour management.*
*If you read this and know what I'm talking about and disagree or know any reasons why one would not want to do this - please speak up! I'm sure I'm not the only one who would like to know.*
This is pretty much mirrored on the Adobe forums btw.

Leopard - CS3 - Interface/Gamma issue

Hello there, switched to 10.5(.4) on a MacPro today and now check this out, it's only in Photoshop. Illy and Indesign and Bridge are fine. No other applications are affected.
If you profile/calibrate your display (with professional software) to Gamma L* - darkish, grey boxes appear in the Photoshop dialogue windows.
http://img297.imageshack.us/my.php?image=leopardphotoshop11zg0.png
If you use Gamma 1.8, the Apple default, Photoshop looks perfekt. With Gamma 2.2 they're barely noticable (pretty much only if you know they're there).
All the other settings you can choose like temperature, luminance, chromatic adaption, profile-type etc. don't influence Photoshop-windows in this way - but as soon as you change the gamma those boxes appear.
I would very much like to know how you guys deal with it - do you profile your display to 1.8/2.2 OR do you use L* and live with the boxes OR have you profiled your display properly but you don't have this nuisance? (!?)
Any help/info would be greatly appreciated.

b So here's what I think happens (+ my idea to solve the grey-boxes issue):
Some applications use the monitor-profile to draw their interface. Like Photoshop and Graphic Converter. (The only 2 I've installed, I'm sure some video-editing-applications, even players are concerned that's maybe the reason some people think it's 'random'). I think these apps do so to immediately can reflect a change in the profile, without restart.
Now Mac OS X Leopard seems to not allow these applications to do so in certain parts of the interface. (Must be a new feature!) The window itself is drawn by the OS. That's the reason only elements like the text and buttons are affected.
And the problem is that the OS uses its 'Generic RGB Profile.icc' which contains Gamma 1.8. So if you calibrate your display with Gamma L* (which you really should do and most profiling-software does by default) those grey boxes appear in said applications.
The solution is easy. Replace the system-rgb-profile with one that supports L* - like the eciRGB profiles.
To do so you have to rename the .icc file in finder but also edit the information inside (which can be done with the ColorSync Utility). Then copy it to the System/Library/ColorSync/Profiles folder.
After that the grey boxes dissapear and everything is back to normal. There's some difference in the tabular data like the CMM and a chroma-entry, so you might want to re-write your display-profile just to make sure everything's alright.
I haven't seen anything yet but could imagine that the rendering of webpages in safari might be affected. Or rather some webbrowsers' without colour management. (I'm just guessing.)
b Problem 1:
Some Adobe apps can see that the current system-profile is identical to your working-space-rgb and reset your rgb-choice to the Generic RGB profile after a restart. (Without changing the 'Colormanagement SYNC'd icon/setting.) This probably could cause trouble if you export or open files.
b Solution:
Use a different profile for your system than your Adobe-RGB setting. I used the 'L-Star RGB v2' for the system and the 'eciRGB v2' for Adobe. They're technically identical but for some reason Photoshop and esp. Illustrator now respect my choices and don't reset anything. Works fine for me. (!)
b Problem 2:
Besides the aforementioned chroma-entry in the Apple default profile (which loss shouldn't cause any issues) there's also the localisation information. Because the profile is named differently in different languages of OS X. I haven't found anything causing trouble (probably because if the profile isn't found it resets back to the english version by default).
b Solution:
This would be easy if someone knows about a .icc file editor. If we could add those localised names from the Apple profile no application would ever know. I've only found hexadecimal editors but won't put something like that on my machine, especially since everything works fine.
I hope Apple comes up with a real solution soon, this seems like too much of a hack - considered the delicate nature of colour management.
If you read this and know what I'm talking about and disagree or know any reasons why one would not want to do this - please speak up! I'm sure I'm not the only one who would like to know.

Is that a webkit rendering issue in Safari 5.1?

I add my voice to rendering issues encountered in Safari 5.1, here they are:
1) Fonts look pixelated on some websites. Here's an example drawn from weebly.
The font used here is OFL Sorts Mill Goudy, so I guess there must be a font rendering engine in weebly that allows non web safe fonts to be displayed properly. That works fine in Firefox 5 & 6, and until recently on Safari 5. Chrome 12 has exactly the same issue as Safari 5.1, so it could be a general rendering issue in webkit.
2) Videos on Vimeo show now a black rectangle instead of the video.
3) The "Insert image" feature in this forum takes forever to load, displaying a white rectangle during several seconds. Same issue with the Evernote clip bookmarklet.
Hope these issues will be fixed soon, any help is appreciated if something can be changed in Safari settings.
Note: resetting Safari (including cleaning cache) doesn't solve the described problems. I'm running Snow Leopard 10.6.8 on Mac Pro Quad 2.8 Ghz.

Thanks for helping diagnose this.
However, my testing indicates that this is not a bug with border-collapse: collapse. Here is why:
If I change the value of border-collapse to "separate" and add "border-spacing: 0", the bug remains. To try this, request http://www.panlex.org/cgi-bin/plxu28-bug2.cgi .
If I leave the value of border-collapse unchanged but change the button elements in the cells to plain text, the bug disappears. To try this, request http://www.panlex.org/cgi-bin/plxu28-bug1.cgi .
On the basis of this testing, it would seem to me that the bug is dependent on the button elements and independent of the border-collapse CSS attribute.
This doesn't explain, however, why you have found border-collapse: collapse producing slow results with other large tables and it doesn't do so with my table in http://www.panlex.org/cgi-bin/plxu28-bug1.cgi . It also doesn't explain why you saw the bug disappear when you changed border-collapse on my page but I didn't see it disappear.
Any further diagnostic help would be welcome.

ITunes 7 Rendering Issues

Ahoy hoy,
I became entangled in this problem upon first running iTunes;
Running it for the first few minutes, all is fine, tick-tock, no problems so far.
Then...
If one is inclined to switch applications, to say Firefox etc., hide iTunes, and then switch back to iTunes upon revealing it from that wonderful hiding place that is apple+h, it comes out all DICOMBOGULATED... of which a preview can be seen:
http://www.flickr.com/photos/duffin-tim/243757719/
It renders the interface all like, nineteen-eightees-Commador64-loading-a-game-up-like (I can post more previews of the glitch, some of them look pretty cool); what is the meaning of this?, am I alone in this problem? Coming to mind is a VRAM issue, but I am not one to speculate on such topics as it's not my professional area.
Toogy Boogy,
Tim D.
iBook G4 1Ghz Mac OS X (10.4.7) Sun-spotted monitor; ladybird stickers; fadded 'S' key; burnt-out not working firewire; all else's d

I have seen some wierd GUI rendering issues as well, notably, this one:
http://www.n715dp.com/links/itunes7gui.jpg
I can replicate this happening by closing the window (leaving the application running) and then opening it up again. The only way to make it go away is to click on the iTunes Store source and then back on my library again.

Interface scripring issue

Hi all.
Just playing with extendscript toolkit and ps cs5, i Have an issue with javascript based panels.
Both my attempts and toolscript samples ebete a New window object is created as panel or window disappear as Sion as shown.
Otherwise modals persist (the script us dispenser and my window not garbaged).
How to solve the problem?
ThNk's, Andrea

Oh yeah the mouseover->layer creation is not a problem but only a practical
situation. The answer is "JS cannot be used to create panels"... thank's
it's as i doubt :/
A solution could be using Adobe Configurator 2.0 to draw the panel and JS
for code automation... i just discovered it on Labs: i'll try for a while.
2012/1/18 c.pfaffenbichler <[email protected]>
Re: interface scripring issue created by c.pfaffenbichler<http://forums.adobe.com/people/c.pfaffenbichler>in
Photoshop Scripting - View the full discussion<http://forums.adobe.com/message/4148576#4148576>

Font rendering issue & multimedia keys not working

Hi, yesterday i switched to KDEmod 4.1 and I have two major problems...
One is font rendering issue... I did not change anything in my font-related packages (cairo, freetype, fontconfig, libxft) and i have to add that this setup worked perfectly in KDEmod 3.5.9, but now it looks like this:
This bug occurs only in qt apps and mostly in kmenu... i.e firefox renders my fonts flawlessly...
Second problem are multimedia keys on my keyboard...
They worked in KDE 3.5.9, but now I cannot set them up properly... Sometimes they work, sometimes they don't...
KDE recognizes the pressed key, but when I assign specific action and press the key, just nothing happens...

You might be able to solve your font issue by going to System Settings -> Appearance -> Fonts. I enable ant-aliasing. I also clicked on configure and select "Use sub-pixel rendering" to RGB and the hinting style to Full. I also use the Force fonts DPI to 96 DPI. This makes the fonts pleasing to my eyes.
This is how I got my multimedia keys to work in KDE4.1:
Go to System Settings -> Regional and Language and make sure to set the County or region to your location.
khotkeys needs to be running. I added it to the autostarted progam list. System Settings -> Advanced tab -> Autostart
When I got the multimedia keys working, I was really tring to get the keyboard shortcuts to work. In addition to the above steps, I also deleted
~/.kde4/share/config/kglobalshortcutsrc. I do not know if deleting this file is needed to get the multimedia keys working, but it was to get the keyboard shortcuts woring.
Restart X
Go to System Settings -> Keyboard and Mouse -> Keyboard Shortcuts
I set the volume control in the KMix component section.
To get the keyboard shortcuts to work, go to the menu editor and select the program you want to create a shortcuts for. Click on the advanced tab and create the shortcut in the shortcut field. Save.
Then go to System Settings -> Keyboard and Mouse -> Keyboard Shortcuts. Change the component to KHotkeys. Select the Program and then select the default shortcut that you just created. (This works for the multimedia keys aswell).
Hope this helps,
pudge

Font rendering issue / Mountain Lion / non Apple LCD display

Hello
This font rendering issue or problem is probably well know by Apple crew too but nobody has solved it yet. Only poor solution are available such as try to adjust manually font rendering by writin some scripts concerning anti alias levels...they really dont solve the problem.
Could Apple bring us solution to this by developing or updating Mountain Lion?
So what is the problem: font rendering is very poor in Mountain Lion when using non Apple LCD. For example Fujitsu SL27T-1 LED (LCD displa) shows fonts very nice way in Windows but in Mac OS ML does not. Somebody told me that its about software vs. hardware rendering. Dont know about that but could you bring me the solution which is not advising me to buy Apple display (which is five times more expensive than other manufactures displays).
Br
M. Leino

just want to add that overall fonts look blurry and they are not very sharp.

Can anyone make --this fix-- work for the FONT rendering issue?

I found this bug report and proposed fix on the webkit buglist:
http://bugs.webkit.org/show_bug.cgi?id=14070
Here is a link that one says can be used to fix the
rendering issue with bold fonts.
If anyone can make this work for Safari 3 on XP please let me know....
Here are the text and link to the how to:
You can fix rendering issues by changing language for non-Unicode programs. The
instruction:
http://www.microsoft.com/globaldev/handson/user/xpintlsupp.mspx#EVE
You should restart system after applying setting.
Hope this helps someone
If not, then call apple support and complain....
maybe if their support phones are getting hot... then they
will fix this horrible bug

I don't believe this is a support issue, it's rather a Bugdev issue. Use the Bug-Report field in Safari to report this directly to the engineers. I also think the bug is known and will be solved, it's therefore not really in the range of AppleCare. (Beta Software is usually unsupported!)
MacBook Pro, MacBook, ModBook, iMac, Mac mini, PowerMac G5, iBook, Apple TV Mac OS X (10.4.9)

Font rendering issue in Windows 7 with Aero

I'm running Windows 7 Home Premium 64-bit, and using Firefox 19.0.2. Aero is enabled, but the ClearType font smoothing is turned off.
At completely random intervals, text is rendered like this in Firefox:
http://i49.tinypic.com/vgshv4.png
Sometimes it can be fixed as simply as hovering the mouse pointer over the affected parts. Sometimes I have to mark the text to get it rendered correctly, and sometimes it can be fixed by scrolling the page.
It can happen on any sites with any encoding, regardless of the font size and color, but I noticed it's extremely rarely happens with Japanese text. It never affects the whole page, only random parts of the on-screen text, and sometimes the interface text as well. Also worth mentioning that it never happens when Aero is turned off.
Is this a Firefox bug, or is something wrong with my system? Thanks in advance.

I had the same issue, uninstalling windows update kb2670838 fixed it for me. See also:
http://answers.microsoft.com/en-us/windows/forum/windows_7-networking/text-rendering-issues-in-firefox-after-installing/1aaefaec-ba47-4577-82c3-44b72a50049b

Interface freezing issues and hard drive replacement

Hi, I have an Imac. It was getting slow and kept getting a long time lag on typing etc. So I bought snow leopard, backed up and wiped and reinstalled the lot. Then it started freezing - from moment one (literally). I could move my mouse and stuff was still running but I couldn't click on anything or select anything or get any response at all. Sometimes it would "white out". Only solution was forced reboot.
So I called apple, rand disk utility, kept showing disk errors - file 334576 should be file 334575 etc. Fixed them - they came back after each freeze. So they said its a hardware error.
Took it to shop. They reinstalled and no errors showed in the tests - but then it kept freezing when they tried to use it. Eventually they settled on a hard drive error - fitted a new one (money paid), it didn't freeze in 48 hours of tests and use. They said that if it keeps freezing it must be an intermittent motherboard problem. TBH I'm not convinced because, though it was slow before SNOW, it wasn't freezing!
Anyway, I took it home, put my stuff back on, was fine -
next day, froze twice in 2 mins - once, rebooted, then again, froze instantly before dock had fully popped up! (It seems to freeze in movement a lot - like task switching or dock popping etc).
It was then that I stumbled upon this term online "interface freezing issues" which seems to have been an initial issue with the imac, and there were some early posts about snow too. The problem is exact, if you minus this hard drive error issue, which MAY have been separate problem (cause by shorts caused by excessive cat hair inside computer).
I have read that external drives etc can be a cause, but not heard usb mentioned, only flywire - I have a dual USB port external drive for time machine. But really, this freezing is entirely since snow.
Can I solve this problem?
Do apple acknowledge this problem?
SHould I uninstall it and ask for my money back?
I would like solid, conclusive answers if possible - from people with direct experience. I work online and am also a writer - i am BEYOND dependant on this mac (especially as my partner is seriously ill and I am the sole income just now).
thankyou for reading
Anna
Anyway - ran disk utility - but no errors this time. Which is good.

As for the taking apart part. I'm not too worried. I've read quite a bit on the subject and watched a couple youtube videos. Also, i've taken a iBook G4 apart to it's core to replace that hard drive and did it without a hitch.
I'm a little unsure about the interface for the Optical Drive. From what i've read the HD is a SATA connection. While, the Optical Drive connection is IDE. Is that normal for one computer to have both?
I found two drives both around $100 for each. One is SATA the other is IDE.
SATA
http://www.pioneerelectronics.com/PUSA/Products/BusinessProducts/Blu-rayDisc+DVD Writers/DVDComputerWriters/DVR-TS08
IDE
http://www.newegg.com/Product/Product.aspx?Item=N82E16827118021
Also, the HD from Newegg that I posted above, runs at 3GB/s. I've remember reading somewhere that my iMac will only run the drive at 1.5GB/s. Is that true?

[SOLVED] XMBC Interface Rendering Issue

Similar Messages

Maybe you are looking for