#613086 gnome-orca: Bad display of orca's preferences menu when started with non-utf8 locale #613086
- Package:
- gnome-orca
- Source:
- orca
- Submitter:
- Jean-Philippe Mengual
- Date:
- 2020-11-30 17:51:14 UTC
- Severity:
- important
- Tags:
Hi, I'm writing this report from chroot environment (so I changed kernel release by name here). The problem is simple: after a migration lenny to squeeze, orca doesn't work anymore on the desktop (alt-ctrl-d). Moreover, alt-F1 doesn't open the menu. When I'm on gnome-terminal, it works. On Iceweasel, it works too. alt-Space works in the terminal. But when I do alt-F1, alt-F2, alt-ctrl-d, it doesn't display anything (only (X-nautilus-desktop and Icon). I precise also that gnome-orca is very few reactive (slow) when I go to such parts on the system. When I see nothing is displayed, I do alt-tab to come to the terminal and I've to wait a long time before having my terminal. Actually, ins-space works, ins-q doesn't. Last strange thing: in the file written by --debug option, I get "no script gnome-terminal.py". I'll attach the file, which contains --debug output and orca -l result. Thanks for your help. I cannot go to squeeze in such conditions now, the desktop is nearly unusable for me. Regards,
Not sure the file was attached by reportbug. Jean-Philippe MENGUAL Le samedi 12 février 2011 à 19:44 +0100, Jean-Philippe Mengual a écrit :
Hi, I upgraded my wheezy and I was 1st surprised because after upgrade, Orca worked properly. The upgrade upgraded: Upgrade: libtalloc2:i386 (2.0.1-1, 2.0.5-1), libc-bin:i386 (2.11.2-10, 2.11.2-11), base-files:i386 (6.0, 6.1), aspell:i386 (0.60.6-4, 0.60.6-6), smbclient:i386 (3.5.6~dfsg-3, 3.5.6~dfsg-5), libc-dev-bin:i386 (2.11.2-10, 2.11.2-11), libapr1:i386 (1.4.2-6, 1.4.2-7), whois:i386 (5.0.10, 5.0.11), liblucene2-java:i386 (2.9.2 +ds1-1, 2.9.3+ds1-1), pidgin-data:i386 (2.7.3-1+squeeze1, 2.7.9-2), libsmbclient:i386 (3.5.6~dfsg-3, 3.5.6~dfsg-5), libc6-i686:i386 (2.11.2-10, 2.11.2-11), libxfont1:i386 (1.4.1-2, 1.4.3-2), samba-common-bin:i386 (3.5.6~dfsg-3, 3.5.6~dfsg-5), locales:i386 (2.11.2-10, 2.11.2-11), newsbeuter:i386 (2.3-1, 2.4-1), libssl-dev:i386 (0.9.8o-4, 0.9.8o-5), w3m:i386 (0.5.2-9, 0.5.3-1), libwbclient0:i386 (3.5.6~dfsg-3, 3.5.6~dfsg-5), libc6-dev:i386 (2.11.2-10, 2.11.2-11), libssl0.9.8:i386 (0.9.8o-4, 0.9.8o-5), libdb4.8:i386 (4.8.30-2, 4.8.30-4), libpq5:i386 (8.4.5-0squeeze2, 9.0.3-1), libservlet2.5-java:i386 (6.0.28-9, 6.0.28-10), openssl:i386 (0.9.8o-4, 0.9.8o-5), samba-common:i386 (3.5.6~dfsg-3, 3.5.6~dfsg-5), libconfig-tiny-perl:i386 (2.12-1, 2.13-1), libc6:i386 (2.11.2-10, 2.11.2-11), libaspell15:i386 (0.60.6-4, 0.60.6-6) But after a reboot, I had again the problem. Strange if it becomes random... An update would be maybe useful. I'll try sid too soon. Regards, Jean-Philippe MENGUAL
Hi, I've just tried with newly committed experimental 2.91.6 release of orca. 1st try: I could read the desktop but not alt-F1 menu, not alt-F2 menu. Second try, even desktop wasn't readable anymore. Here's the debug file. Regards, Jean-Philippe MENGUAL
Hi, As I said the bug is solved randomly, one time a day or one time I don't know when and why. Today, I could read desktop one time and desktop then alt-F2 then alt-F1 once. I couldn't reproduce this good working. Anyway, I could log in a debug file when orca accepted to read my desktop (alt-ctrl-d) (but not the rest of gnome environment). It was immediately after I removed ibmtts and speech-dispatcher. But next reboot, it didn't work anymore. So related to speech-dispatcher/ibmtts... not sure. Reminder: it most cases, I cannot read gnome structure, but applications work (iceweasel, terminal, ...). I hope via a comparison of all 3 files I sent, you will explain the problem. I do become mad. :) Regards, Jean-Philippe MENGUAL
retitle 613086 orca has issues with a non-UTF-8 gnome desktop tags 613086 + wontfix thanks Jean-Philippe tried with the full gnome desktop being UTF-8 and it worked fine. It's not the first time we see issues with !utf-8 in Orca. I'm afraid there is no real solution to this: distributions have almost all migrated to utf-8 by default now, and orca maintainer most probably all have, so the !utf-8 case is deemed to have issues. Samuel