[Solved] Greek accented characters and Qt Applications

Hello.
This is my first day with Arch linux.
My problem has to do with greek accented characters like ά, ή, ό etc.
I can type these characters on my browsers, rox file manager and other applications but not on Qt based applications like Skype and TeXmaker.
At first when I tried to type ά on skype I got nothing.
Later I installed ibus-qt and now I get á instead of ά, é instead of έ, etc.
Thanks in advance for any help.
PS: I include the results of locale -a and locale commands in case it helps:
# locale -a
C
POSIX
el_GR
el_GR.iso88597
el_GR.utf8
en_US
en_US.iso88591
en_US.utf8
greek
# locale
LANG=C
LC_CTYPE="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_COLLATE="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_PAPER="C"
LC_NAME="C"
LC_ADDRESS="C"
LC_TELEPHONE="C"
LC_MEASUREMENT="C"
LC_IDENTIFICATION="C"
LC_ALL=
Last edited by Paris (2013-07-22 00:41:19)

I just created a /etc/rc.conf file and added:
HARDWARECLOCK="UTC"
TIMEZONE="Europe/Athens"
KEYMAP="us"
CONSOLEFONT="ter-v16b" #it's Terminus font for console, just install terminus-font from community
CONSOLEMAP=
LOCALE="en_US.UTF-8"
DAEMON_LOCALE="no"
USECOLOR="yes"
This fixed my problem.

Similar Messages

  • Problems with Greek accented characters

    After the update to AIR 2.0.2 I cannot input into any application greek with accented characters.
    Tried TweetDeck and Twhirl and neither work (used to before the update)
    Is this a bug or it needs some configuration
    I am working on Fedora13 but heard the same problem reported on Ubuntu.
    Have not tried on MS Windows or MacOSX

    Hi,
    I'm using Adobe AIR 2.0.3 on Windows machine. I wrote an app in Aptana Studio (build: 2.0.5.1278522500) with ExtJS library and I found the problem with polish national characters like ż and Ż (all the other national characters like ą, ę, ń are possible to input).
    In order to reproduce, here you have the sample code in ExtJS:
    http://dev.sencha.com/deploy/dev/examples/form/anchoring.html
    As you will see - it is possible to input ż and Ż in text fields.
    Now, use the same code to build AIR applicaton and then run the application. It is not possible to input those characters in Air window. Right Alt+z acts like undo operation - it removes last entered text. All the other characters work fine.
    Here is the code I used:
    <html>
        <head>
            <title>New Adobe AIR Project</title>
            <link rel="stylesheet" type="text/css" href="lib/ext/resources/css/ext-all.css" />
            <link rel="stylesheet" type="text/css" href="lib/ext/air/resources/ext-air.css" />
            <script type="text/javascript" src="lib/air/AIRAliases.js"></script>
            <script type="text/javascript" src="lib/ext/adapter/ext/ext-base.js"></script>
               <script type="text/javascript" src="lib/ext/ext-all.js"></script>
            <script type="text/javascript" src="lib/ext/air/ext-air.js"></script>
            <script type="text/javascript">
            Ext.onReady(function(){
        var form = new Ext.form.FormPanel({
            baseCls: 'x-plain',
            labelWidth: 55,
            defaultType: 'textfield',
            items: [{
                fieldLabel: 'Send To',
                name: 'to',
                anchor:'100%'  // anchor width by percentage
                fieldLabel: 'Subject',
                name: 'subject',
                anchor: '100%'  // anchor width by percentage
                xtype: 'textarea',
                hideLabel: true,
                name: 'msg',
                anchor: '100% -53'  // anchor width by percentage and height by raw adjustment
        var window = new Ext.Window({
            title: 'Resize Me',
            width: 500,
            height:300,
            minWidth: 300,
            minHeight: 200,
            layout: 'fit',
            plain:true,
            bodyStyle:'padding:5px;',
            buttonAlign:'center',
            items: form,
            buttons: [{
                text: 'Send'
                text: 'Cancel'
        window.show();
            </script>
        </head>
        <body>
        </body>
    </html>
    Is it possible to input those characters or is there a workaround for this (disable undo operation or so) ?
    I really appreciate any help.
    Kind regards,
    Marcin.

  • Console UTF-8 Greek accent characters

    LOCALE="en_US.UTF-8"
    DAEMON_LOCALE="no"
    KEYMAP="gr"
    CONSOLEFONT="iso07.14"
    CONSOLEMAP="8859-7_to_uni"
    Having this configuration I can view Greek characters (even accented), switch keyboard from English to Greek (using Alt+Shift) and write Greek characters (example: αβωδσφηξ) but not accented ones (example: άέήίύόώ ϊϋ ΰΐ). Accented characters are produced by first pressing a "dead" key (semi-colon/colon key in my case). I am always referring to console, everything's fine under X.
    If I change my configuration to this:
    LOCALE="en_US.iso88591"
    DAEMON_LOCALE="no"
    KEYMAP="gr"
    CONSOLEFONT="iso07.14"
    CONSOLEMAP=
    I can even type accented characters in console but then other issues come up related to the locale not being UTF-8.
    Isn't there a way to produce accented characters (multibyte UTF sequences they are) in a UTF-8 console?
    I have gone through tons of documentation and sites and still haven't figured this out :-/ Is this a limitation of the kernel not supporting multibyte sequences? (http://www.linuxfromscratch.org/lfs/vie … nsole.html <- see bottom of page)

    ksmanis wrote:Having this configuration I can view Greek characters (even accented), switch keyboard from English to Greek (using Alt+Shift) and write Greek characters (example: αβωδσφηξ) but not accented ones (example: άέήίύόώ ϊϋ ΰΐ). Accented characters are produced by first pressing a "dead" key (semi-colon/colon key in my case). I am always referring to console, everything's fine under X.
    I have the following configuration and i can properly write accented characters to console (urxvt).
    LOCALE="en_US.UTF-8"
    DAEMON_LOCALE="yes"
    KEYMAP="us"
    CONSOLEFONT= <= empty
    CONSOLEMAP= <= empty
    To properly write greek with alt+shift at keyboard i have this file named "10-keyboard.conf " in /etc/X11/xorg.conf.d/
    Section "InputClass"
    Identifier "Generic Keyboard"
    MatchIsKeyboard "yes"
    Option "CoreKeyboard"
    Option "XkbRules" "xorg"
    Option "XkbModel" "pc105"
    Option "XkbLayout" "us,el"
    Option "XkbOptions" "grp:alt_shift_toggle,compose:menu,grp_led:scroll"
    EndSection
    I hope i helped you

  • Accented characters and UTF-8

    Hi all,
    I have a problem with accented characters. I read that Plumtree 5.0 is completely Unicode enabled and all HTTP responses from remote web services are converted to Unicode (UTF-16). So the portal sends back to the client browser all pages in UTF-8.
    We have a lots of portlet (ASP and JSP) that write data in external DB, for example SQLServer. When I fill an html form with accented characters that have to be saved in our DB, they are saved in UTF-8 because the gateway converts the HTTP response. We want that the data are saved as if we don't use the portal (without conversion). I tried to change the Charset with the ASP code (Response.Charset). This solves only the problem of displaying the right characters in the browser.
    Could you explain me better how the portal make the conversion and how can I solve my problem?
    Thank you very much,
    Alberto Marchiaro

    It might be helpful to clarify a few things first: 1. Both Java and VB Script will store strings in UTF-16/Unicode. If you have some code in your ASP file that looks like this: Dim strDatastrData = Request.Form("SomeName") then if you were to examine memory for the variable strData, you would see 16 bit characters. The same is true for Java. 2. String data is almost never sent over HTTP as UTF-16/Unicode. 3. Both Java and VBScript perform an implicit character set transcoding when reading string data out of a request or when writing string data out to a response. 4. ASP will perform the transcoding according to the value of the Session.CodePage value. If you have Session.CodePage to 65001, then ASP will expect the string data to be in UTF-8 and it will transcode UTF-8 in the request into UTF-16 in VB Script. Similarly, a Session.CodePage value of 65001 will cause "Response.Write" to convert UTF-16/Unicode into UTF-8. 5. All of the above is separate from how Java or VB Script interact with the database. Generally speaking an ASP module will use ODBC to communicate with the database. The ODBC layer knows that VB Script keeps strings in UTF-16/Unicode. The ODBC layer will perform the proper conversion into the database character set. Plumtree always recommends using UTF-16/Unicode in the database. You can do this relatively easily by declaring your database columns using the "N" datatypes such as NCHAR and NVARCHAR. However even if you using some other character set, the ODBC layer should always properly transcode from VBScript. The importantly thing to remember is that data that is sent over HTTP is never written directly to the database without going through some ASP or JSP code. Since the ASP and JSP code always uses UTF-16/Unicode, there should never be any issue with how the data is sent over HTTP. Here is an explanation for how Session.CodePage, Response.CharSet and Session.LCID work in ASP:****************************************************
    1. Response.CharSet
    2. Session.CodePage
    3. Session.LCID
    Here is an explanation of these properties and why they are important to non-English ASP gadget writers:
    1. Response.CharSet
    This property will cause the HTTP contentType header to be set with the specified character set. The HTTP header is the best way to tell the recipient what the character set is. The Plumtree HTTPGadgetProvider will read the ContentType header and then know how to properly trancode the portlet text into UTF-16/Unicode. Here
    is an example of how to set this property:
    Response.CharSet = "UTF-8"
    2. Session.CodePage
    This property tells the ASP engine which character set to send text in. Please remember that all text is encoded in Unicode on the Web Server. It only gets turned into the client character set when it is send down to the client. The Session.CodePage tells the engine which codepage to transcode into when sending down to the client. Please note that this property is an "integer" property not a string. So you have to know the number of the codepage that you would like to transcode into. Here is an example of how to use this property:
    Session.CodePage = 65001
    3. Session.LCID
    This property tells the ASP engine which locale is being used. The locale is used by various VBScript functions such as FormatDateTime in order to format the date correctly for the locale. If the locale is a French locale, then the date will be formatted according to French rules. The locale does not really effect the character set, but if the portlet writer is going to the trouble of setting the other properties, then they should also set the LCID too. Here is an example of how to set this property:
    Session.LCID = 1041
    Please note that the examples that I am using are the appropriate examples for Japanese and UTF-8. The values for these properties are different for different character sets. For example, for ISO-2022-JP, the values would be:
    Request.CharSet = "iso-2022-jp"
    Session.CodePage = 50220
    Session.LCID = 1041
    A very helpful URL to figure out the values to use with Request.CharSet and Session.CodePage is the following:
    http://msdn.microsoft.com/library/default.asp?url=/workshop/Author/dhtml/reference/charsets/charset4.asp

  • Accented Characters and Diacritic folding flag

    Hi,
    When using "--diacritic-folding" flag in dgidx, is there a way to ignore certain characters from mapping accented characters to simple ASCII equivalents?
    For e.g, i have this flag enabled but i need "ñ" and "n"to behave as two different characters.
    Is this possible?
    Thanks
    Edited by: mk.s on Apr 12, 2013 5:33 AM

    There is no out of the box capability for this that I am aware of. You could raise a feature request via support.oracle.com to allow you to be able to define exceptions, and if you do so I'd recommend including some use cases to explain the business requirement.
    The only way I can think of doing this with the current software is a workaround - you would have to have a pre-processing step to map the character to a different code point, then when you submit your search apply the same translation. I've done this previously to get around issues with unsupported (in older Endeca releases) code points in the Thai language, and it does work but you have to add a manipulator to your pipeline (or do the transformation in the data extract) and have some simple code before you send the query on to Endeca (before ENEQuery if via the API).
    Thanks
    Michael

  • Accented characters showing up as ? in JRE1.3 but ok in 1.2

    I'm implementing a database web interface product that utilizes JSPs (on SunOS 5.7).
    The problem is in the search form. When using accented characters (French language), the JSP calls on URLEncode, but all accented characters show up as '?'.
    However, when editing a record, using accented characters is not a problem (i.e., the accented characters are properly stored in the fields).
    Back on the server, I ran a small program to output accented characters and also to call java.net.URLEncoder to convert the characters.
    The default JDK is J2SE (1.3.1). Compiliing and running the program results in question marks.
    Using JDK 1.2, the accented characters show up fine.
    It would appear that URLEncoder is not at fault, but instead, JDK 1.3.1 doesn't seem to handle the accented characters.
    I figure there must be a setting somewhere, but I'm not sure where.
    Here's the program I used (written in Win98, using standard Win-based character set and Unicode format \u00xx; in Unix, "more" displays the Win accented characters fine but "vi" displays them as \xxx; compiles and displays perfectly when using JDK 1.2):
    import java.net.*;
    class mine {
    public static void main(String args[]) {
    System.out.println("�����������") ;
    System.out.println(URLEncoder.encode("�����������")) ;
    System.out.println("\u00e0\u00e2\u00e4");
    System.out.println("\351");
    System.out.println("\351\347\356\364\373\340\350\342\344\374\357") ;
    The output with JDK 1.2 is:
    �����������
    %E9%E7%EE%F4%FB%E0%E8%E2%E4%FC%EF
    ���
    The output with JDK 1.3.1 is:
    %3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F

    Between jdk1.2 and jdk 1.3 the default encoding of the vm changed.
    You can get it by executing:
    System.out.println("Default Encoding:" + System.getProperty("file.encoding"));
    or
    System.out.println("Default Encoding:" + (new java.io.InputStreamReader(System.in)).getEncoding());
    The default encoding is used during the conversion of bytes to strings and vice verca.
    Assume your default encoding is ISO8859_1. Then calling new String(byte[]) is equivalent to calling
    new String(byte[], "ISO8859_1")
    Now if you are converting a character from one encoding scheme to another and there is no mapping
    for this character in the target scheme. Then the character will be replaced by a default character
    which is (quite often) the question mark.
    You can set the default encoding for a vm by passing it as a command line parameter
    java -Dfile.encoding=ISO8859_1
    java -Dfile.encoding=Cp1252

  • When I use Greek accenting and polytonic characters in a title, Final Cut Pro X quits unexpectedly. What should I do?

    When I try to write a title in Greek using the Greek alphabet, Final Cut Pro X quits unexpectedly, the moment I press the button for the Greek accenting (" ' "). This happens only when I press the button. If for example, I write the title in TextEdit and then copy paste it in FCPX then the title is pasted correctly and the program does not quit.
    An example of title: "Εγώ", so as soon as I press the accenting and then "ω", then everything freezes and FCPX quits.
    It must be a bug, but it really causes a problem. Temporarlily, I always c/p to textEdit and then paste it to FCPX. But I am also using Polytonic Greek system (fonts), so it is a bugger to always c/p. Is there a solution to this?
    Thank you.

    This seems to be a bug, as there was another thread that reported this exact same problem but using Finnish (I believe).
    Do you have Motion? You can try doing your titles there and then export/import into FCPX.

  • Greek language notes display loses accented characters

    I can type in Greek in TextEdit, save the file as Unicode (UTF-16), and drag it into my iPod Notes folder.
    In OS10.4 I can use accented characters in TextEdit but, when the file is loaded onto the iPod, it omits the accented characters. They aren't displayed incorrectly - they simply aren't displayed at all.
    Anyone ever tried uploading Greek to an iPod? Any Greek users out there?
    Martin

    Yes, the accented characters appear OK on my wife's video iPod.
    I suppose there's no chance that Apple will update the software on my not-very-old color iPod?
    No, I thought not. Money-grabbing *****s.
    I love Apple but not ALL the time.

  • I need a Vietnamese keyboard. Recommendations? A keyboard that officially works with iPad and displays all the characters and their accent marks for typing.

    Where do I find an excellent and reliable Vietnamese keyboard for new iPad? A keyboard that displays all the characters and the accent marks so typing can be easily accomplished. The iPad keyboard selection for Vietnamese really only seems to change the Return key to the Vietnamese language. iPad is sold all over the world....my interest is Viet Nam.....the full keyboard.

    Thanks.....my Vietnamese expert spouse says this tip will work just fine.  I was not aware of the hold down function. Slow typing but accomplishes the objective native on the iPad.
    You are correct.....most Apps that I find seem to be based only on a copy/paste method of input.
    You solved the problem.

  • Issue with ENEQuery java api and searching terms with accented characters

    Hi,
    we are using ENEQuery to query the mdex engine. When search terms contain accented characters (like á,í etc), even though the terms are decoded (using java.net.URLDecoder), the term gets send to dgraph is encoded. for e.g a search for "sofá", from the dgraph logs "sof%c3%a1" and fetch in 0 results
    ENEQuery query = new ENEQuery();
    final ERecSearchList searches = new ERecSearchList();
    final ERecSearch eRecSearch = new ERecSearch("search interface name", "term");
    searches.add(eRecSearch);
    query.setNavERecSearches(searches);
    Any suggestions?
    Thanks

    Hi,
    Does your indexed data (which you hope to match) contain "sofá" or "sofa" (no diacritic)? If the latter, and in-general, you may benefit from the dgidx flag --diacritic-folding* as described in documentation "Mapping accented characters to unaccented characters".  If you are running the latest version, this is all that should be required to generate a match.
    Best
    Brett

  • I copied my library to my new computer and I have some songs with greek characters and when I click them to play they change into something which is not readable. I have delete them and copy them again and also delete and re-download itunes

    I copied my library to my new computer and I have some songs with greek characters and when I click them to play they change into something which is not readable. I have delete them and copy them again and also delete and re-download itunes.

    im so happy I have a iTunes Card Code absolutely free! I got it at http://linkbitty.com/freeitunes2014

  • [SOLVED] Playing sound simultaniously from wine and other applications

    I'm using Pulseaudio with the following packages installed:
    ~> pacman -Q | grep 'alsa\|pulse'
    alsa-lib 1.0.27.2-1
    alsa-plugins 1.0.27-2
    alsa-utils 1.0.27.2-1
    lib32-alsa-lib 1.0.27.2-1
    lib32-libpulse 5.0-1
    libpulse 5.0-1
    pulseaudio 5.0-1
    pulseaudio-alsa 2-2
    When running a wine application sound works, unless a linux application is playing sound. If that is the case, no sound is playing from the wine app until sound from the linux application stops (for example by pausing smplayer).
    Is there any way to make sound work simultaneously from wine and native applications?
    Other information that may be relevant:
    Architecture - x86_64
    Desktop - KDE
    Wine application - BabasChess
    Last edited by CarbonFixer (2014-04-16 16:14:10)

    V1del wrote:Install lib32-alsa-plugins and set wine to use the default resp (System Standard) card in winecfg pulsemixers should show an [alsa-plugin] wine stream
    Thanks
    Was missing that package.

  • We cannot type Polish (non-latin) characters in WebDynpro applications

    We cannot type Polish (non-latin) characters in WebDynpro application (in runtime) because 'Browser Help Shortcuts' are fired.
    To type a polish character in polish keyboard you need to press AltGr + letter (ie. AltGr + a/c/e/s/o/l/z/x/n). To type an uppercase polish character you need to press AltGr + Shift + letter. This comination is in fact the same as pressing Alt + Ctrl + Shift + letter (because AltGr produces Alt + Ctrl) and it fires some of 'Browser Help Shortcuts'. For example AltGr + Shift + O should produce a letter O with a dash on it's top but instead it fires 'Show nesting of HTML containers'.
    We tried to turn off sap-wd-lightspeed, but then other key combinations are reserved for u2018Browser Help Shortcutsu2019.
    We need to be able to use AltGr + Shift + a/c/e/s/o/l/z/x/n in runtime.
    Product: SAP NW 7.11 SP04
    WebDynpro for Java
    I hope there is a somewhere a hidden parameter that solves our problem Maybe we're in some kind of debug mode?
    Thanks for your help!!

    The funny thing is that bold font [when message unread in message list] shows OK, ie in greek, but when i click on unread message, it is assumed to have been read, so it changes over to medium [non bold] and the encoding changes as well into the one that is not greek and thus unreadable.  In ~/.sylpheed/sylpheedrc the fonts are:
    widget_font=
    message_font=-microsoft-sylfaenarm-medium-r-normal-*-*-160-*-*-p-*-iso8859-7
    normal_font=-monotype-arial-medium-r-normal-*-12-*-*-*-*-*-iso8859-7
    bold_font=-monotype-arial-bold-r-normal-*-12-*-*-*-*-*-iso8859-7
    small_font=-monotype-arial-medium-r-normal-*-12-*-*-*-*-*-iso8859-7
    In /etc/gtk, for gtk1.2 apps the file refering to greek encoding [el] seems to be fine [exactly the same as in slackware 9.1].

  • Sms with accented characters

    Hi,
    I hope somebody with some SMS/SMPP experience would be able to fix the problem or
    advise as what to do. OK Now we have an application which is supposed to send an
    SMS to a recipient on certain occassions and this SMS might contain accented characters.
    Now in SMPP apparently we have three encoding schemes namely
    1) 7 bit GSM encoding
    2) 8 bit binary
    3) UCS-2
    Now the third one is out of question since it would reduce the size of the message
    to 70 characters which is not acceptable. 2nd one which is 8 bit binary with I assume
    DCS value 4(or at least thats what we are using) seems to support only latin characters.
    It works for latin characters i.e., iso-8859-1 which does have some accented characters.
    however for other than latin we have some problems e.g hex value for small phi in
    greek (iso-8859-7) is f6. If you look at the corresponding value of f6 in Latin 1(iso-8859-1)
    it is �. Now if you send greek characters setting the DCS value to 4 and u send three
    phi's what you would recieve on the recipient device are three �. So it seems that
    the 8 bit binary supports only iso-8859-1.
    Now if I try to do some encoding into GSM 7 bit. and send three phi's thought I dont
    recieve � but not phi's at the recieving end. The DCS value for the purpose I am
    using is 0. How am I encoding it to GSM 7 bit.
    I am creating the following array
    private static final char [] GSM_7Bit_CHARACTERS = {
    '@', '\243', '$', '\245', '\350', '\351', '\371', '\354', '\362', '\307',
    '\n', '\330', '\370', '\r', '\305', '\345', '\u0394', '_', '\u03A6', '\u0393',
    '\u039B', '\u03A9', '\u03A0', '\u03A8', '\u03A3', '\u0398', '\u039E', '\033',
    '\306', '\346',
    '\337', '\311', ' ', '!', '"', '#', '\244', '%', '&', '\'',
    '(', ')', '*', '+', ',', '-', '.', '/', '0', '1',
    '2', '3', '4', '5', '6', '7', '8', '9', ':', ';',
    '<', '=', '>', '?', '\241', 'A', 'B', 'C', 'D', 'E',
    'F', 'G', 'H', 'I', 'J', 'K', 'L', 'M', 'N', 'O',
    'P', 'Q', 'R', 'S', 'T', 'U', 'V', 'W', 'X', 'Y',
    'Z', '\304', '\326', '\321', '\334', '\247', '\277', 'a', 'b', 'c',
    'd', 'e', 'f', 'g', 'h', 'i', 'j', 'k', 'l', 'm',
    'n', 'o', 'p', 'q', 'r', 's', 't', 'u', 'v', 'w',
    'x', 'y', 'z', '\344', '\366', '\361', '\374', '\340'
    Storing all the values in a Map in teh same order and then for each character in the
    message sending the byte value of the index. If I do a snoop in the snoop I see the
    right hex values as per GSM Encoding table but on the recipient device I see garbage.
    Any ideas as to how can greek and other european character set support be added to
    this application?
    Am I using the wrong DCS value or any body with some other ideas.

    I don't know about the exact character sets for the 7 and 8-bit SMS, but I doubt it's any different then character sets for anything else... So, in this case, the 7-bit set will only be able to handle the first 128 chars, which is A-Za-z0-9 and some punctuation. 8-bit would go into the extended ASCII chars in the table here:
    http://www.asciitable.com/
    There might be some restrictions or differences.
    Basically, 7-bit is ASCII. 8-bit is ASCII+Extended or ISO8895-1. The chars your talking about sending get into the other ISO8895-X sets, which I believe would be out of range. The USC-2 should give you these, however. So either you send shorter messages, or you send ASCII text.
    It would also depeend on the device to be able to display those characters in the first place. Just like on any web site, if you don't have a font that has the necessary characters, it just displays as ? or a box or whatever.

  • Special characters and TextInput

    Hei,
    I have a small application in Flex 2 with several TextInput
    controls. When I want to enter any special characters, like
    umlaute, accented vowels, etc. they are not entered. (Using
    Seamonkey or Firefox under Ubuntu Linux, either KDE or xfce). But
    they are properly entered in Camino under Mac OSX.
    Any ideas how can I solve this ? (Seamonkey and FF are set to
    use utf-8 encoding, and special chars entered in the url field are
    utf-8).
    Thanks, Ale

    ale500
    Did you find some workaround ? I'm using flex 3, and got the
    same problem. The application works fine under windows+ff or
    windows+IE but in ubuntu+ff 3.x 2.x not.
    Thanks for your attention!
    Saldanha

Maybe you are looking for