Closed Bug 265806 Opened 20 years ago Closed 20 years ago

Talkback is unusable in Linux l10ns of Firefox

Categories

(Firefox Build System :: General, defect)

Product:
Firefox Build System
Component:
General
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: marcoos, Assigned: bryner)

References

Details

This is how the talkback window looks in recent cs-CZ and pl-PL l10ns of Firefox
under Linux:
http://bugs.firefox.pl/attachment.cgi?id=184&action=view

This is not a problem with the master.ini file (bug 265564), because the
master.ini file exists under Linux.

Is this a problem with the localization? (Did we forget to translate something
in pl-PL?) or is it a more general problem (it seems so, because the Czech one
suffers from the same problem)?

(This bug was first submitted to the AviaryPL bugzilla at
http://bugs.firefox.pl/show_bug.cgi?id=252 )
Also happens to French builds.
Summary: Talkback is unusable in cs-CZ and pl-PL l10ns of Firefox → Talkback is unusable in cs-CZ, fr-FR and pl-PL l10ns of Firefox
I have examined folowing localised builds:
firefox-1.0.pl-PL.linux-i686.tar.gz  
firefox-1.0.fr-FR.linux-i686.tar.gz   
firefox-1.0.es-ES.linux-i686.tar.gz  
firefox-1.0.fi-FI.linux-i686.tar.gz  
firefox-1.0.hu-HU.linux-i686.tar.gz 
firefox-1.0.nl-NL.linux-i686.tar.gz

All of them come from
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-0.9-l10n/ and are
20041022 nightlies.

In neither of them does the talkback work. It seems to be something bigger and
more serious.
confirming on linux.
Flags: blocking-aviary1.0?
windows builds work fine. Linux only
I can confirm that Windows builds are OK (checked latest Windows nightly on a
Windows 2000 machine).

Any idea when this problem first started?  Or has this been the case with all
past localization builds?
this is something specific to talkback on the build machine (karma).  the en-US
builds have the same problem.

en-US build available for internal testing at
karma:/builds/tinderbox/firefox-265806-installer.tar.gz
It has the XTalkback.ad file containing the various strings but it apparently
isn't being referenced by the talkback app.

nothing obviously different between the two systems' mozconfig, env, or OS.
bryner pointed out that the binutils had been updated on the en-US build system,
so updated binutils on karma and am rebuilding it now.
not the binutils: build with the new binutils demonstrates the same problem.
summed / diffed a talkback.xpis between ocean (en-US) and karma and the only
differences are the master.ini (expected) and talkback executable.  next step is
to make fullsoft manually and see if we're getting errors that aren't trapped
but that will have to wait for tomorrow.
still same crap with l10n build from 26th... 
In 26th l10n build, es-ES for linux also shows the image mentioned in comment 1.
I've tried the en-US for linux, but this one works ok.

I'd like to remark that es-ES has nothing related to talkback localization,
which might be the common factor for the failing build, in the same way that
help system failed showing a xml error at the bottom when no help localization
was done.
any chances to have this fixed? It's so frustrating to use RC1 and not be able
to send any bug reported... Also it's not possible to close Talkback window
without killing it's process.
still talkback is unusable in RC2. We should remove it from l10n builds if we 
can't fix it...
Flags: blocking-aviary1.0-L10N?
*** Bug 267907 has been marked as a duplicate of this bug. ***
Czech 1.0rc2 win-zip has working TalkBack - I was able to submit crash. I didn't
try installer variant, but it's worked okay in 1.0rc1 version.
Installer variant of Swedish and German doesn't work.
Zbigniew: I just dowloaded Firefox 1.0rc2 *PL* win-install and quick crash test
(eval of "parent.close()" in JS colsole) will bring up TalkBack agent and I was
able to submit crash (-> TB1742368H).

I deleted content of C:\Document and
Settings\<user>\%appdata%\Talkback\MozillaOrg\Firefox10 before install, so could
somebody with talkback-problem delete this directory and retry it? Maybe some
info resists from previous versions...

(Futhermore, cs-CZ win-installer is also okay)
If I understand correctly this is a Linux only bug?
OS is set to Linux, so please test there.
Oops, I'm sorry, ignore my previous Windows-related comments =(
Summary: Talkback is unusable in cs-CZ, fr-FR and pl-PL l10ns of Firefox → Talkback is unusable in Linux cs-CZ, fr-FR and pl-PL l10ns of Firefox
This isn't going to block us. I'd ship 1.0 with no talkback at all for L10n
builds. If we have it on windows, great. If we get a fix for linux, even better.
But we're not going to block the nov 9 release on this issue.
Flags: blocking-aviary1.0? → blocking-aviary1.0-
I agree with Asa. We should just remove talkback from Linux builds if we can't
get  it working. I *don't* know how it works on MacOS X.
Same thing with da-DK.
Summary: Talkback is unusable in Linux cs-CZ, fr-FR and pl-PL l10ns of Firefox → Talkback is unusable in Linux l10ns of Firefox
As noted, this problem affects all l10n builds coming off of karma, our Linux
l10n build system.  Until we know what the problem is the decision is to ship a
build without talkback enabled rather than ship one with a broken talkback.  The
change to ship without talkback is only happening for the Linux l10n builds,
which excludes en-US.
this bug is fixed

nightly from 08/11/2004 works ok!

Thank You cmp!
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
That's November 8, 2004, right? ;)

bryner found the problem last night and I put a temporary workaround in place on
the Linux l10n build machine today.  A full fix involves setting LANG as needed
before calling xrestool in our build system.  We should change that after 1.0
work is complete.
Flags: blocking-aviary1.0-L10N?
Component: Build Config → General
Product: Firefox → Firefox Build System
You need to log in before you can comment on or make changes to this bug.