Build Transmission on Windows

[cadusilva]

cadusilva

Let's test this:

In your Transmission-Qt installation directory, create a new directory with name translations, move your transmission_pt_BR.qm file to that directory, run the application.

Ref: http://doc.trolltech.com/4.6/internationalization.html and http://doc.trolltech.com/4.6/qt-conf.html

No deal. Didn't work.
To see if the problem is with the translation or the program, I'll modify the Russian translation for the Transmission think she is Portuguese and see if it is applied.

EDIT: It did not work at all. I tried:

- Using folder name translations;
- Use folder pt_BR inside translations;
- Use a filename as only pt_BR.qm;
- Rename the folder translations to l10n;
- Change the russian file to be recognized as Portuguese ...

I tested both in the Transmission-QT folder as the folder transmission in AppData/Roaming. Nothing worked.

[rb07]

cadusilva
I was right the first time: the file goes along side the application.

What we seem to have wrong is the file name, it should be transmission-qt_pt_BR.qm, nothing else is used. Looks like everybody has the file name wrong (the .ts files with the source code, the English .qm file, all named wrong).

I debugged the application and the relevant sequence is as follows:

• Qt gets the locale(s) from the registry. Its plural since Windows can use several languages, and in many cases if it doesn't find the specific locale (language_location, as in pt_BR or es_MX) it goes for the language alone.
• Qt looks for a qt.conf along side the application. That file is not needed but could be used to set different file locations; when it doesn't find it then it looks for the original location of the Qt installation, the one only the builder has, then at the application directory.
• Finally Qt looks for the translation files, 1st: the specific one, for instance yours transmission-qt_pt_BR.qm, if not found it keeps looking for transmission-qt_pt.qm, transmission-qt_en.qm. When none is found it just uses the untranslated strings.

[cadusilva]

One problem solved and another showing. Only the context menus were in the new language. Everything else remains in english.



I checked with the QTLinguistic and everything is translated, but in the end only the context menus are appearing translated. It is good that we're debugging it to help in the internationalization of Transmission-QT and find out problems and things that need to be updated.

[rb07]

Only the context menus were in the new language. Everything else remains in english.

That could be a build created problem, I'll have to see if I disabled local languages while building the Transmission library.

If not, then is a bug worth reporting on the Wiki. Your image is perfect, I would only add markings highlighting the parts in English, and those in Portuguese.

There are no accents, ñ, tildes, cedillas, anywhere? Those would look really nice on a screenshot.

[cadusilva]

There are two images with accents. The brazilian language does not contain the character Ñ, but in fact is very similar to spanish in many parts, yet is quite different. I know english well even more than spanish, which I only know a few things very insignificant ... (laughs)

Once I was talking with a friend, she began to speak a little spanish because it is similar to portuguese. But it is not so simple!

[rb07]

I checked my configure parameters, and I didn't use --disable-nls (do not use Native Language Support) so in theory libtransmission should work using the locale language.

"In theory", I've never tested the console tools for instance... Testing now under Cygwin... no, they don't display in a different language. I even rebuild transmission-2.12 with NLS enabled, intltool+iconv+gettext+... installed, and nothing gets installed from the po directory.

The only way to find out is to dive into the Qt code and see where those untranslated parts are coming from, if they could be translated by Qt but are not, or if they come from libtransmission and should be translated there.

[cadusilva]

I checked my configure parameters, and I didn't use --disable-nls (do not use Native Language Support) so in theory libtransmission should work using the locale language.

"In theory", I've never tested the console tools for instance... Testing now under Cygwin... no, they don't display in a different language. I even rebuild transmission-2.12 with NLS enabled, intltool+iconv+gettext+... installed, and nothing gets installed from the po directory.

The only way to find out is to dive into the Qt code and see where those untranslated parts are coming from, if they could be translated by Qt but are not, or if they come from libtransmission and should be translated there.

Ok, I'll wait for new instructions.

[msdobrescu]

Hello,

I try to get a new bt client on Windows, after I have discovered that Vuze was sending e-mails without noticing me.
I have installed the latest QT setup from your link (rb07's).
In my case it opens, asks me for some initial settings, stay open for 30 secs, and then crashes.
I use Windows 7 64 bit.
What should I do to get at least a log?

[cadusilva]

Hello,

I try to get another bt client on Windows, after I have discovered that Vuza was sending e-mails without noticing me.
I have installed the latest QT setup from your link (rb07's).
In my case it opens, asks me for some initial settings, stay open for 30 secs, and then crashes.
I use Windows 7 64 bit.
What should I do to get at least a log?

So you downloaded and installed this executable, but the program does not stay open for even half a minute? I also use Transmission-QT on Windows 7 x64, but never had problems with it.

Still think rb07 may want to investigate.

[msdobrescu]

So you downloaded and installed this executable, but the program does not stay open for even half a minute? I also use Transmission-QT on Windows 7 x64, but never had problems with it.

Indeed, that build. It crashes every time.

[rb07]

msdobrescu
Start the program form a command console, you may get some error messages that way.

When you say "it crashes", you mean the full show with the Windows panel asking if you want to report this to Microsoft? Does that panel has further info?

[msdobrescu]

msdobrescu
Start the program form a command console, you may get some error messages that way.

When you say "it crashes", you mean the full show with the Windows panel asking if you want to report this to Microsoft?

Hi, I have opened a console, but I have no idea how to run it otherwise but giving the command "transmission-qt". Are there any other parameters?
It opens the application window, the message saying "Transmission is a file sharing program [...]", I press <I Agree>, then it comes the "Change Session" dialog, I let is as it is - starting a local session. Then, it stays for a while (10-30 secs) and "transmission-qt.exe has stopped working" Windows message appears. There is no other info, neither in console.

The event log contains two entries:

Faulting application name: transmission-qt.exe, version: 0.0.0.0, time stamp: 0x4ce1e706
Faulting module name: transmission-qt.exe, version: 0.0.0.0, time stamp: 0x4ce1e706
Exception code: 0xc0000005
Fault offset: 0x000cec4a
Faulting process id: 0x1b8
Faulting application start time: 0x01cb89475296ada4
Faulting application path: C:\Program Files (x86)\Transmission-Qt\transmission-qt.exe
Faulting module path: C:\Program Files (x86)\Transmission-Qt\transmission-qt.exe
Report Id: 987b48bc-f53a-11df-be31-f5e8e5083ba0

Fault bucket 2190075434, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: transmission-qt.exe
P2: 0.0.0.0
P3: 4ce1e706
P4: transmission-qt.exe
P5: 0.0.0.0
P6: 4ce1e706
P7: c0000005
P8: 000cec4a
P9:
P10:

Attached files:
C:\Users\admius\AppData\Local\Temp\WERE1D3.tmp.WERInternalMetadata.xml

These files may be available here:
C:\Users\admius\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_transmission-qt._a9d02ab0f16283329bda812f8a18d4128b66626e_07d9ee8f

and

Analysis symbol:
Rechecking for solution: 0
Report Id: 987b48bc-f53a-11df-be31-f5e8e5083ba0
Report Status: 0

[msdobrescu]

The report says:

Version=1
EventType=APPCRASH
EventTime=129345861543137989
ReportType=2
Consent=1
UploadTime=129345861543688021
ReportIdentifier=7017a855-f353-11df-85d1-c77773f5bc96
IntegratorReportIdentifier=7017a854-f353-11df-85d1-c77773f5bc96
WOW64=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=transmission-qt.exe
Sig[1].Name=Application Version
Sig[1].Value=0.0.0.0
Sig[2].Name=Application Timestamp
Sig[2].Value=4ce1e706
Sig[3].Name=Fault Module Name
Sig[3].Value=transmission-qt.exe
Sig[4].Name=Fault Module Version
Sig[4].Value=0.0.0.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=4ce1e706
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=000cec4a
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7600.2.0.0.256.1
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=0a9e
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=0a9e372d3b4ad19135b953a78882e789
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=0a9e
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=0a9e372d3b4ad19135b953a78882e789
UI[2]=C:\Program Files (x86)\Transmission-Qt\transmission-qt.exe
UI[3]=transmission-qt.exe has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files (x86)\Transmission-Qt\transmission-qt.exe
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\syswow64\kernel32.dll
LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[4]=C:\Windows\syswow64\ADVAPI32.DLL
LoadedModule[5]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[6]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[7]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[8]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[9]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[10]=C:\Windows\syswow64\COMDLG32.DLL
LoadedModule[11]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[12]=C:\Windows\syswow64\GDI32.dll
LoadedModule[13]=C:\Windows\syswow64\USER32.dll
LoadedModule[14]=C:\Windows\syswow64\LPK.dll
LoadedModule[15]=C:\Windows\syswow64\USP10.dll
LoadedModule[16]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7600.16661_none_ebfb56996c72aefc\COMCTL32.dll
LoadedModule[17]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[18]=C:\Windows\syswow64\IMM32.DLL
LoadedModule[19]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[20]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[21]=C:\Windows\syswow64\NSI.dll
LoadedModule[22]=C:\Windows\system32\WINNSI.DLL
LoadedModule[23]=C:\Windows\syswow64\OLE32.dll
LoadedModule[24]=C:\Windows\syswow64\OLEAUT32.DLL
LoadedModule[25]=C:\Windows\system32\WINMM.DLL
LoadedModule[26]=C:\Windows\system32\WINSPOOL.DRV
LoadedModule[27]=C:\Windows\syswow64\wldap32.dll
LoadedModule[28]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[29]=C:\Program Files (x86)\Transmission-Qt\dbus-1.DLL
LoadedModule[30]=C:\Windows\system32\mswsock.dll
LoadedModule[31]=C:\Windows\System32\wshtcpip.dll
LoadedModule[32]=C:\Windows\System32\wship6.dll
LoadedModule[33]=C:\Windows\system32\DNSAPI.dll
LoadedModule[34]=C:\Windows\system32\rasadhlp.dll
LoadedModule[35]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[36]=C:\Windows\system32\uxtheme.dll
LoadedModule[37]=C:\Program Files\Logitech\SetPoint\x86\GameHook.dll
LoadedModule[38]=C:\Program Files\Logitech\SetPoint\x86\lgscroll.dll
LoadedModule[39]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4927_none_d08a205e442db5b5\MSVCR80.dll
LoadedModule[40]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4927_none_d08a205e442db5b5\MSVCP80.dll
LoadedModule[41]=C:\Windows\system32\ntmarta.dll
LoadedModule[42]=C:\Windows\system32\dwmapi.dll
LoadedModule[43]=C:\Windows\system32\wintab32.dll
LoadedModule[44]=C:\Windows\system32\userenv.dll
LoadedModule[45]=C:\Windows\system32\profapi.dll
LoadedModule[46]=C:\Windows\SysWOW64\ctagent.DLL
LoadedModule[47]=C:\Windows\system32\Wacom_Tablet.dll
LoadedModule[48]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[49]=C:\Windows\system32\rsaenh.dll
LoadedModule[50]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[51]=C:\Windows\system32\dhcpcsvc6.DLL
LoadedModule[52]=C:\Windows\system32\dhcpcsvc.DLL
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=transmission-qt.exe
AppPath=C:\Program Files (x86)\Transmission-Qt\transmission-qt.exe

[rb07]

I have opened a console, but I have no idea how to run it otherwise but giving the command "transmission-qt". Are there any other parameters?

None needed (meaning, yes you can use other parameters, but no you don't need to use any if you just want to get the same effect as running it from the shortcut or Programs menu).

Exception code: 0xc0000005

In all the garbage that Windows reports... that line means "Access Violation error". Google it, usual causes: faulty RAM, Windows' DEP (Data execution prevention) which shouldn't be happening... unless Qt (or MingW or one of the libraries the application depends on) does something for exception handling.

This sounds familiar... about 3 pages back there is a report that also says the application crashed, but with a message about the C++ runtime library, could this be the same? (the different report caused by the presence of Microsoft's Visual Studio ).

I don't know, I've never was able to reproduce the problem (but I have DEP disabled since it interferes with many Cygwin programs). In fact, the application has never crashed, period, but then again I don't use a 64-bit version of Windows.

Perhaps you can solve the mystery: do you use any other Qt application?

I also could mark the executable with the SafeSEH flag, which is what I've seen done by the Cygwin developers.

[msdobrescu]

Hi, I am not sure as not all the apps report using Qt.
But I believe Amarok does.
I have installed Amarok from Amarok-2.4-git-win32-20101003.exe.
I have uninstalled Amarok, but no effect. Transmission has the same behavior.
DEP disabling did not solve the problem.