Rendering of Arabic/Transliteration broken since upgrade to 29

Hello,
Mozilla Firefox 29.0.0 - 29.0.1, MacOS X 10.9.2
Problem: Arabic fonts (Lateef, Sheherazade) as well as transliteration Arabic > Latin is broken since update to 29. They were fine before. This happens when loading pages from a database. The protocol uses 'mixed content' and there seems to have been an update in Firefox's handling of such content. However, even explicitly unblocking such content doesn't solve the problem (apparently, one has to deblock every single page or is there an option for an entire domain? Otherwise, this is a pain in the neck and completely impractical). Firefox 'chooses' to select encoding seemingly at random: View > Character Encoding > Unicode/Western. Unfortunately, this version of Firefox scratched the possibility to select default encoding.
Now, the pages loaded do not declare their encoding. However, this was not a problem because FF would use Unicode (UTF-8) by default. Setting instead "Default for Current Locale" is obviously useless. That's where the problem seems to be. Why was the plain default option changed so that we have no longer access to it? As you will understand in mixed environments (using a variety of languages and keyboard layouts), 'default locale' is pointless. Any suggestions are most welcome.

FredMcD. Thank you for the hints. I'm sure they help in most cases. It didn't solve my problem though. Normal websites work actually quite well, it's just the internal ones that have this problem.
cor-el. Thank you also for your hints. I checked and I'm pretty sure that it's not a corrupt font. The problem, as I've mentioned, is that the server does not declare its encoding. This wasn't a problem as long as UFT-8 could be declared as fall-back. Now, as I've written, there is only the option 'Default for Current Locale' which doesn't help. I suppose either Mozilla puts back the older option or we have to do something here. Would love to post link but I'm not sure there is general access to our servers (probably not) but I'll ask.
I attached an exampled of how the 'garbled' text looks. It's more than garbled there just no font 'resolution'.
Thank you both again for taking the time to give advice. I think your hints will come in useful in general use of Firefox.

Similar Messages

Sound broken since upgrade from 2.6.29

I wasn't sure if I should post this here or in the multimedia forum. Anyway...
I have an Echo Audio Mia-midi soundcard and sound hasn't been working properly for me since upgrading from 2.6.29. Both 2.6.30 and 2.6.31 share the same issue and reverting to 2.6.29 always solves the problem. It seems some driver infrastructure has changed, because the two "Line out" level meters are not available in alsamixer anymore. Instead I have VU-meters for front, rear, center, woofer and side. These can't be set however, and seem to have no impact on the output (they are sometimes set to 100% and sometimes to 0%, but output is silent in both cases).
Running echomixer (an Echo Audio specific mixer in alsa-tools) and playing sound shows that there is sound playing at full volume at the subdevice channels, but the "final" output is silent, even though all output channels are set at their proper values, including the output mixer. Raising the monitor mixer, effectively forwarding the input channels to the output works as it should, so as far as I can tell, the issue concerns the software/driver output to the soundcard.
I've tried everything I can think of to solve this, but nothing seems to help. I've run an alsa debug script in both 2.6.29 and 2.6.31, but the only difference worth noting that I can find is connected to the line out level meters. In 2.6.29:
Simple mixer control 'Line',0
Capabilities: pvolume
Playback channels: Front Left - Front Right - Rear Left - Rear Right
Limits: Playback -128 - 6
Mono:
Front Left: Playback 0 [96%] [0.00dB]
Front Right: Playback 0 [96%] [0.00dB]
Rear Left: Playback 0 [96%] [0.00dB]
Rear Right: Playback 0 [96%] [0.00dB]
state.Mia {
control.1 {
comment.access 'read write'
comment.type INTEGER
comment.count 4
comment.range '-128 - 6'
comment.dbmin -12800
comment.dbmax 600
iface MIXER
name 'Line Playback Volume'
value.0 0
value.1 0
value.2 0
value.3 0
Both of these parts are missing from the output in 2.6.31.
I don't know what to do next. Any help would be greatly appreciated.

I wasn't sure if I should post this here or in the multimedia forum. Anyway...
I have an Echo Audio Mia-midi soundcard and sound hasn't been working properly for me since upgrading from 2.6.29. Both 2.6.30 and 2.6.31 share the same issue and reverting to 2.6.29 always solves the problem. It seems some driver infrastructure has changed, because the two "Line out" level meters are not available in alsamixer anymore. Instead I have VU-meters for front, rear, center, woofer and side. These can't be set however, and seem to have no impact on the output (they are sometimes set to 100% and sometimes to 0%, but output is silent in both cases).
Running echomixer (an Echo Audio specific mixer in alsa-tools) and playing sound shows that there is sound playing at full volume at the subdevice channels, but the "final" output is silent, even though all output channels are set at their proper values, including the output mixer. Raising the monitor mixer, effectively forwarding the input channels to the output works as it should, so as far as I can tell, the issue concerns the software/driver output to the soundcard.
I've tried everything I can think of to solve this, but nothing seems to help. I've run an alsa debug script in both 2.6.29 and 2.6.31, but the only difference worth noting that I can find is connected to the line out level meters. In 2.6.29:
Simple mixer control 'Line',0
Capabilities: pvolume
Playback channels: Front Left - Front Right - Rear Left - Rear Right
Limits: Playback -128 - 6
Mono:
Front Left: Playback 0 [96%] [0.00dB]
Front Right: Playback 0 [96%] [0.00dB]
Rear Left: Playback 0 [96%] [0.00dB]
Rear Right: Playback 0 [96%] [0.00dB]
state.Mia {
control.1 {
comment.access 'read write'
comment.type INTEGER
comment.count 4
comment.range '-128 - 6'
comment.dbmin -12800
comment.dbmax 600
iface MIXER
name 'Line Playback Volume'
value.0 0
value.1 0
value.2 0
value.3 0
Both of these parts are missing from the output in 2.6.31.
I don't know what to do next. Any help would be greatly appreciated.

Bash completion broken since upgrade

Hi,
since I did an upgrade the bash autocompletion behaves strange. Completing directories will end in a space instead of an slash. Eg you enter "/et[tab]" and it completes "/etc " instead of "/etc/". This makes navigating directory hierarchies a PITA. Can anyone confirm this? Any known workarounds?

For those still looking for a solution to this:
From: http://aur.archlinux.org/packages.php?ID=16980
Comment by: vl981 on Fri, 31 Dec 2010 03:57:13 +0000
Hi.
For those who use this package and bash completion in same time:
remove the _filedir function from the '/etc/bash_completion.d/acroread'
file provided by the package. See http://forums.adobe.com/thread/745833.
P.S. Updated PKGBUILD and respected acroread files one may found here:
https://github.com/vp1981/pkgbuild/raw/master/acroread/PKGBUILD
https://github.com/vp1981/pkgbuild/raw/master/acroread/PKGBUILD
Last edited by kontax (2011-02-11 10:52:20)

Ethernet broken since upgrading to Yosemite

On my Mac Mini (circa 2010) I upgraded to Yosemite and ever since I can only operate on the WiFi, Ethernet will not configure or work. It is currently stating there is not cable attached - but there is and I have tested the cable on my PC (it works just fine there). Any idea what to do?? Running OS X 10.10

Well, the issue with USB anything is that the device manufacturers have to supply compatible drivers. Check with CableMatters for an updated driver.
http://www.asix.com.tw/download.php?sub=driverdetail&PItemID=131

[fixed] /dev/cdrom broken since upgrade to kernel 2.6.28.8

Yesterday, before I upgraded to these packages:
kernel-2.6.28.8-1 (relevant)
not relevant (see discussion): klibc-udev-140, udev-140
I could use /dev/cdrom fine as a link to my actual CD-drive. For example I used
cdparanoia -Q
while having a Audio-CD inserted and this gave me the TOC of the CD.
After the update I have this:
/dev/cdrom exists but isn't accessible. By default,
cdparanoia stops searching for an accessible drive here.
Consider using -sv to force a more complete autosense
of the machine.
More information about /dev/cdrom:
Checking /dev/cdrom for cdrom...
Could not stat /dev/cdrom: No such file or directory
After some testing I found that my device names somehow "shifted". These both work
cdparanoia -Q /dev/sr0
cdparanoia -Q /dev/sg1
So, yes it works, but before I didn't had to set everything to /dev/sr0, because the default /dev/cdrom just worked.
Is this a bug or a feature in the new udev?
EDIT:
This seems to be not a problem with the udev upgrad, but rather with the kernel upgrade. See discussion below.
Last edited by JonnyJD (2009-03-31 23:30:16)

@skyscraber: I don't know if this is related. My problem boils down to just the kernel upgrade now and I haven't had problems that bad.
@magaso: I also that problem during testing. For me the fix was not using the new kernel with old udev-139. Doing that gave me "/dev/cdrom -> /dev/cd/cdrom-1:0:0:0" and "/dev/cd/cdrom- -> ../sr0".
Now back to the problem that started this thing:
This is NOT because of the upgrade to udev 140. Like I wrote above, I got the new kernel at the same time. Downgrading udev and klibc-udev didn't help with my problem, but downgrading to kernel 2.6.28.7-2 made everything work again.
The symlinks were also NOT the problem, because my symlinks itself work fine, even when the problem occurs. Either way they are like the ones from B:
lrwxrwxrwx 1 root root 21 26. Mär 17:16 /dev/cdrom -> /dev/cd/cdrom-1:0:0:0
lrwxrwxrwx 1 root root 6 26. Mär 17:16 /dev/cd/cdrom-1:0:0:0 -> ../sr0
brw-rw---- 1 root optical 11, 0 26. Mär 17:16 /dev/sr0
So with the old kernel "cdparanoia -Q" works again, without having to specify /dev/sr0 explicitely.

Bad renders in Windows since upgrade to CC 2014

Ever since upgrading to the newest version of CC 2014, Premiere Pro is having issues rendering video segments with noisy black horizontal line noise.
Still images render fine, but any P2 footage renders badly. It reminds me of the way footage used to look if viewed through a monitor that had ground loop problems, (Which this system definitely does not!). It only occurs in my P2 footage shot with the HVX-200, 720p24fps, which rendered pristinely in the older CC version. I am on a Windows 7 machine with approved Nvidia card built especially for the Adobe CC suite by Safe Harbor, have very fast Raid arrays and plenty of Ram etc., and the only video effect applied is the "lighting" effect, one native to the program and not a third party one, so I attribute these glitchy renders to the new release code. Anyone else seeing this problem??

I don't have any of that media to test with. If you care to shoot two or three minutes of junk footage and zip up the card, I can test it here.
Mobile DepositFiles

Since upgrade to 10.4.5: Faxing via shared fax modem broken?

Since upgrading my Macs to Mac OS X 10.4.5 sending faxes via a shard fax doesn’t work anymore. When attempting to send a fax the error message
"Error while printing"
pops up. However, when faxing directly from the Mac with the shared fax modem, everythings works flawlessly.
This used to work prior to upgrading to Mac OS X 10.4.5.
Anyone here with similar experiences?
Werner.
Mac mini Mac OS X (10.4.4)

The kernel panic points to Airport. Either your Airport software is way out of date or your Airport card may not be properly seated or has failed. So the first thing to do is remove the Airport card. If the panics cease, then reinstall the Airport card and see what happens. If it panics again, then remove the Airport card.
The next thing I would do is:
Boot from your OS X Installer. Be sure to use the installer for the version of OS X you have installed. After the installer loads select Disk Utility from the Installer menu (or Utilities menu if using Tiger.) After DU loads select your OS X volume from the list on the left, click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer. Now shutdown the computer for a couple of minutes and then restart normally.
If DU reports errors it cannot fix, then you will need Disk Warrior (3.0.3 for Tiger) and/or TechTool Pro (4.1.1 for Tiger) to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
The next thing I would do is download the 10.4.4 Combo Updater and reinstall the update. Then reinstall the Airport card and see if it works properly.
I would suggest that before installing the update that you first boot into safe mode.

HT6473 Bluetooth is still broken since iOS 8 upgrade

I have an iPhone 4S and ever since upgrading to iOS8 my bluetooth no longer works in my car (Mazda). Both worked perfectly together for years but since the upgrade they no longer work. Have tried resets upgrade to 8.1 and nothing fixes it. Apple have check phone in store and agreed Bluetooth is now not working properly but refuse to take any accountability as it is "out of warranty". very unimpressed

Im having the same issue like others and have had my iPhone 6 has lost the ability to connect to my VW GLI with an RCD-510 headunit. This is not a head unit issue because on day one of the phone with 8.0,8.02 but now I have no connectivity with 8.1.... I have tried to reset the phones network settings, did a full restore , deleted all profiles, chased the ghosts on I cloud and did s clean reinstall of 8.1 to no avail... I cannot downgrade to 8.02 due to the baseband being changed with 8.1 so it seems.
iOS 8.1.1 still does the same thing, and now I have an appointment at the genius bar tomorrow.
Wish me luck, it sounds petty but I just expect my phone to pair to the car just like it did on my iphone5 with ios 7.xx and the iphone 6 on 8.02 and 8.0

Problems since upgrading to Itunes 6.0.1.3

Ever since upgrading to Itunes 6.0.1.3, songs will not update to my Ipod. Called Tech Support twice on this and they suggested: Uninstalling/reinstalling Itunes (done three times so far); Reformatting the Ipod back to factory default (done twice); disabling anti-virus. NONE of this has worked. Also found out that Apple Tech Support is VERY weak on Itunes support. Songs show in my Library, but will not update to Ipod. Any suggestions?

Ever since upgrading to Itunes 6.0.1.3, songs will
not update to my Ipod. Called Tech Support twice on
this and they suggested: Uninstalling/reinstalling
Itunes (done three times so far); Reformatting the
Ipod back to factory default (done twice); disabling
anti-virus. NONE of this has worked. Also found out
that Apple Tech Support is VERY weak on Itunes
support. Songs show in my Library, but will not
update to Ipod. Any suggestions?
Found my solution after spending 1 hour/10 min on phone. Tech referred me to article 93716 (removing Itunes, Empty Temp Directory). I still had the same issue (not all songs updating). I checked Windows Explorer and the files that were NOT updating were located in backup folder I had created at some point during the two-week troubleshooting process. When I moved these folders into the Itunes directory, EVERYTHING started working again (creating playlists, burning CD's, moving music to my Ipod).
I learned that even though Itunes shows everything in your Library broken down by playlist, purchased music, etc.--they could be ANYWHERE on your hard drive. However, to update the Ipod, it appears they need to be in the Itunes directory.
I'm not sure why all this broke in the first place, but here is a list of the articles that I followed:
Article #93698, #32222, 93716. I also learned that the Apple Tech Lady, although very nice, could NOT tell me anything about the directory structure of Itunes, where the songs should be, or much about Itunes in general.

Unable to print with HP Color LaserJet 2605dn since Upgrading to Mavericks

Since upgrading to Mavericks, I've had nothing but problems printing to my HP Color Laserjet 2605dn.
I'm having this problem on both my iMac and my MacBook Pro.
I get errors like:
"unable to write pirnt data broken pipe"
"unable to send data to printer"
"printer not connected"
I've been reading responses to others with similiar issues and I've tried
deleting and re-adding my printer.
reseting my printing system
Installing Guenprint.
re-adding my pirnter with a generic PCL driver.
None seem to correct the problem.
This problem happens both when connected directoy with USB and when connected through the network.
I have no problem printing with my work (Wondows) laptop.
Any help would be appreciated.

Thanks, a brody.
Yesterday (before I read your response), I downloaded the latest firmware (20140413.) (What do they say about great minds?)
I thought the issue may have been resolved.
I was finally able to print my bank statement on both the iMac and MacBook.
Today, I'm back to the the same issues.
Very frustrating, even though I've had the printer for five years, I've printed less than 20,000 pages.
In my mind, it's pointing more and more towards a hardware issue.

CC 7.1: Ridiculous render times since upgrading to mavericks

This is my first time editing a project in Premiere Pro CC7.1 since upgrading to Mavericks. Playback was running very glitchy while trying to play a very simple composition imported from AE. Just a basic motion graphic, nothing too heavy. My computer froze and reset 2 times while trying to play it before rendering, so I am now rendering the sequence to see if this will solve the issue and it's rendering 1 frame every 15-20 seconds.
In the past this same operation would have taken 10-15 seconds total to render.
I'm using a brand new MacBook Pro Retina 15" 2.7GHz with 16GB of RAM.
Has anyone else had this issue and/or any suggestions on how to fix it?
Thanks in advance!!

I have been seeing this and a wide variety of similar problems - the Adobe-Mac community appears to be exploding on the issue of CC and Macs/Mavericks esp. in the last few weeks. A ton of problems people are having after a recent update of Adobe CC program or programs. I see blame being tossed everywhere, and this doesn't look like it's going to die down and go away by itself.
Just my .02, but...
Every major OS upgrade is going to throw off problems with 3rd party (and even 1st party) software as developers identify and squash bugs and incompatibilities - this can take months to work itself out. And is a predicable outcome from having multiple programmers working independently on anything that works together.
Rolling back an OS is often not a viable option. Rolling back a software update is usually easier. Messing about with lots of moving parts can easily compound a problem. So can skipping a step in a complicated set of instructions or following the wrong set of instructions.
A recommendation based on my personal opinion & 20+ years of experience: Don't try to roll back Mavericks, but do roll back to the previous version of CC (before 7.1). If you use Time Machine (and it ran after the Mavericks upgrade and before the CC 7.1 update), this should be pretty easy to do.
Take the time to first make a complete & manual backup of your system to an external drive (if you've got the money, a clone of your hard drive, otherwise an image of your hard drive on something other than your internal hard drive), and a separate live backup of your personal files on an external drive. Just in case...
If you don't/didn't use Time Capsule or the above didn't solve the problem, then you might need to consider one of two options:
Uninstall CC completely, and install CC 'one version' prior to the one that gave you problems. So if you're using Pr 7.1, go back to 7.0. Here's instructions on how to completely remove CC: http://helpx.adobe.com/creative-suite/kb/cs5-cleaner-tool-installation-problems.html and here's instructions for how to get an older version of a CC program: http://helpx.adobe.com/creative-cloud/kb/download-previous-versions-creative-applications. html or http://www.adobe.com/support/downloads/product.jsp?product=98&platform=Macintosh
Rollback the OS to Mountain Lion, but recognize this isn't a trivial exercise and may result in compounding problems, esp. if you ignore a first step of taking a complete backup and/or don't follow the instructions to the letter. Here's a tutorial: https://discussions.apple.com/docs/DOC-6162
Here's a related thread (one of many) with useful info: http://forums.adobe.com/message/5983648#5983648
Like brain surgery (which I've had!), results can vary from one system to another, and you need to own treating every computer as a unique entity. It's hard to exactly replicate a problem even with identical hardware and software/OS. That's another way of saying that all of this is not an iron-clad fix for your problems (my disclaimer) - use at your own risk.
And when you're out of the heat of the moment, please take this opportunity to learn the lesson of backup (that 97% of computer users haven't), and recognize that Time Machine is so very worthwhile to have in your wheelhouse.
Those of us in production environments (or not) can certainly choose to play the blame game, but imo these problems are a result of all our choices:
Apple for not allowing more extensive beta testing
Adobe for not taking full advantage of said beta testing
Power/production users for upgrading anything in a production environment before a) enough time has gone by that show-stopper problems are both identified and resolved and/or b) deploying on a non-production machine and fully testing before trying it out on a production machine.
Being in a production environment to me equates to balancing a need for current software/features against having a stable working environment. I generally put more emphasis on the latter. This is another lesson to learn once you're beyond the heat of the moment and to then keep in your wheelhouse.
And please Adobe:
Own the problem (even if you don't publicly admit it here or anywhere else - I'm personally fine with that)
Don't point fingers, it stirs a pot not worth stirring
Figure out the problem and fix it! It's gonna take time, so please get started if you haven't already.
Giving us progress updates would be nice, but if that's too hard or reputationally risky, skip that but keep working on fixing the problem. Please?

Since upgrading to ver 12 from 9.01 It takes between 15-30 minutes to startup then anything I click just has the spinning wheel ie wait. Both Ie and Chrome work

I had no issues with Ver 9.01 but since upgrading to Ver 12 it takes forever to startup but is unusable when it finally comes up. Any ideas why and how do I fix it. IE 9 and Chrome have no issues.

Try to start Firefox in [[Safe mode|Safe mode]]. This mode disables all extensions, user customizations, hardware acceleration, etc. temporarily for diagnostic and troubleshooting. If Firefox works fine in Safe Mode, then this is likely an add-on issue. Restart Firefox in normal mode, then type "About:addons" (without the quotes) in the address bar. Disable your extensions one by one, restarting Firefox between each one, until you find the trouble maker. Once you do, you can disable that add-on and report the issue to that add-on's developer.
A few other basic trouble shooting things you can try is this:
Run all Windows Updates, install all needed service packs, etc.
Update your graphics driver (Firefox uses your graphics card for some rendering, and an out of date graphics card driver can cause problems. [https://support.mozilla.org/en-US/kb/how-do-i-upgrade-my-graphics-drivers https://support.mozilla.org/en-US/kb/how-do-i-upgrade-my-graphics-drivers].
Update all your plugins (Flash, Java, etc.): [http://www.mozilla.org/plugincheck/ http://www.mozilla.org/plugincheck/].
Download and Install MalwareBytes Anti-Malware, run a full Scan. [http://www.malwarebytes.org/ http://www.malwarebytes.org/]. This helps check that there are no viruses on your computer causing issues. You can uninstall this program after you clean off any infections.

Since upgrade to FCP6 playback has video noise

I'm editing a feature film on FCP and I recently upgraded from FCP5 to FCP6. Since upgrading, I've noticed that anything I view has a lot more video noise and pixels. When I change the sequence settings, it doesn't seem to make a difference. For example, a straight edged counter top will look like it has moving hash marks instead of a straight line. Also when I export a segment into compressor, to make an mp2, the resulting clip has a lot of visible noise around movements. This never happened in the past. I digitized minidv tapes and was able to make very good quality dvds from my FCP project in FCP 5. Now everything looks pretty bad. Certainly not dvd quality anymore.
Anyone have this problem? *I'm pretty desperate.* Thanks all!

Try trashing your render files and re-rendering everything.

Since upgrading to ios8.0.2 I can`nt rotate my screen when looking at photos

since upgrading my 5s iphone to ios 8.0.2 I can`nt rotate my screen useing safari & looking at photos,is there a fix or upgrade planed

MMake sure screen rotation lock isn't on by swiping up from the bottom to open control panel, then look on the top right, there is a lock with an arrow circling it, make sure it's not highlighted. If it isn't try turning your phone off then on again. If that doesnt work try a hated restart by holding done the home and power buttons at the same time until you see the apple on the screen. If that doesn't work you could try restoring your phone or make an appointment with an Apple genius at the Apple Store, your accelerometer may be broken. Hope this helps.

ISight/Quicktime issues since upgrading to Lion

Hello,
I have tried everything but I can't seem to come up with a solution. Problems have arose ever since upgrading to Lion on my early-2008 Macbook Unibody. I have seen many users on this board saying that Lion has broken their iSight as well. Here are my issues.
iSight
- seen in System Profiler (Hooray)
- cannot be seen by any application
- does not work with any other user
Quicktime
- fails for screen recording, audio recording, and video recording ("The Operation Could Not Be Completed")
- can play movies just fine
Solutions I have tried
1. Uninstalled everything 3rd party
2. PMU reset (several times)
3. Repaired Permissions
Any other assistance would be greatly appreciated. Cheers.

• If Apple's http://support.apple.com/kb/HT2090
   suggestions do not help you, (are you certain that you used
   the correct "reset" procedure?) continue with the following.
• Use Disk Utility to repair permissions and then
   download and apply the 10.7.2 Combo Update:
     http://support.apple.com/kb/DL1459
• Repair permissions again immediately following the system restart
   that completes the Combo update.
Properly applying the Combo version of updates
can sometimes correct problems like yours.
Message was edited by: EZ Jim

Rendering of Arabic/Transliteration broken since upgrade to 29

Similar Messages

Maybe you are looking for