I am trying to run UE with Wine under Linux. UE Version 1.1 was reported in
http://appdb.winehq.org/appview.php?appId=2464 to work without problems using Wine, and hopefully that has not changed for the more recent versions.
I have solved some initial problems with UE by re-compiling Wine with different USE flags (I am using Gentoo Linux). Now I am left with one annoying issue:
When minimizing the UE window to the task bar and opening the UE window again, the Wine console displays the following error message, while UE hangs and does not refresh the window any more:
"This program tried to use a DOMDocument object, but
libxml2 support was not present at compile time."
Any help is appreciated. I use Newsbin Pro so far, but there is no support for proxies and I would be willing to change for UE, provided I can get everything working. Thank you.
Problem with Wine....
i don't think anything changed regarding wine in recent versions, i didn't do anything specific to support wine, just UE is using minimum of system support with internals running on pure language, so if GUI emulation is implemented efficiently there should not be significant performance impact.
did you try to uncheck edit menu->icon in system tray? when the program is minimized to system tray the task bar icon is removed, maybe this causes the exception.
did you try to uncheck edit menu->icon in system tray? when the program is minimized to system tray the task bar icon is removed, maybe this causes the exception.
Problem solved, thank you.
Alex, thank you very much. Unchecking in the edit menu the "icon in system tray" was resolving the problem. I will try to learn more about UE.
is it the program or the system message? if it is ue message what is the exact wording?
UE is using its own "Temp" directory to keep the temporary database, as far as I remember it is not used while saving attachments, it is used though when you open an attachment from the article view or invoke "play". but i'm not sure you are talking about UE temp dir.
if it is linux temp dir check e.g. running out of space (e.g. the directory is on the same partition as the directory where you save attachments and you fill it all so the system cannot write anywhere within the partition) etc., i don't run linux here.
UE is using its own "Temp" directory to keep the temporary database, as far as I remember it is not used while saving attachments, it is used though when you open an attachment from the article view or invoke "play". but i'm not sure you are talking about UE temp dir.
if it is linux temp dir check e.g. running out of space (e.g. the directory is on the same partition as the directory where you save attachments and you fill it all so the system cannot write anywhere within the partition) etc., i don't run linux here.
This problems appears to be wine related. In task manager pane, I get the error 'Couldn't create temp file C:\ue\temp\Rt\" followed by 8 alpha-numeric chars. Earlier version of wine below 0.9.6 work properly. It is affecting saving of article body, article attachment, and importing of search item. I have tried other distros, pre-compiled packages, and compiling my own wine and always the same error. What dll's are used in all three functions, maybe related to disk access? It is possible to use different arguments to compile wine, that may help but default compilation is not working, and users of latest wine versions will be under the assmption that UE does not work properly and perhaps discount using this program.
so it is UE error message then.
it is just a usual file. it is not related to saving attachments it is used while downloading article body or search results. i'll be talking then about download article body since it doesn't make any difference which case.
if you see the error try to open the directory and delete the file. can you delete it? if no tasks the file should disappear withing 1 minute from the directory as well.
if not it would mean the file is locked, maybe wine doesn't close the file handle when e.g. thread exits through throwing exception.
if you can delete it and the file disappears by itself after at most 1 minute and the problem doesn't exist when the file is not there already (but it is very strange since the file name may well vary) something wrong with creating the file while the file exists, it is very difficult to imagine how such a basic file operation could go wrong. if it is a new wine version and there is such a serious bug it is likely to be fixed soon.
if you see the error always even when you start the program and download a single article body, these are file permissions, but then strange how you managed to start the program at all since it keeps its temporary database in the temp directory as well.
it is just a usual file. it is not related to saving attachments it is used while downloading article body or search results. i'll be talking then about download article body since it doesn't make any difference which case.
if you see the error try to open the directory and delete the file. can you delete it? if no tasks the file should disappear withing 1 minute from the directory as well.
if not it would mean the file is locked, maybe wine doesn't close the file handle when e.g. thread exits through throwing exception.
if you can delete it and the file disappears by itself after at most 1 minute and the problem doesn't exist when the file is not there already (but it is very strange since the file name may well vary) something wrong with creating the file while the file exists, it is very difficult to imagine how such a basic file operation could go wrong. if it is a new wine version and there is such a serious bug it is likely to be fixed soon.
if you see the error always even when you start the program and download a single article body, these are file permissions, but then strange how you managed to start the program at all since it keeps its temporary database in the temp directory as well.
I am experiencing exactly the same error with Wine version 0.9.12. I had resolved it earlier by chance with setting of different Wine compile flags and adding various dll files, but I did not note down the configuration at that time. After a fresh install with the standards setup, I have not been able to figure out in the last 4 hours how to solve that problem.
It appears that UE can not write particular files in the Database/Temp directory, while it has no problem with other files, e.g. in the Database/Newsgroups directory. From what I have seen, the files relating to the error message are never created at all.
Example for an error message in the task manager:
"Couldn't create temp file c:\ue\Temp\Rt\5BEE0338"
It seems that there are files created/modified in the c:\ue\Temp\Db directory though. Changing permissions and and changing the location of the data base directory to the logical drive c: did not solve the problem.
It appears that UE can not write particular files in the Database/Temp directory, while it has no problem with other files, e.g. in the Database/Newsgroups directory. From what I have seen, the files relating to the error message are never created at all.
Example for an error message in the task manager:
"Couldn't create temp file c:\ue\Temp\Rt\5BEE0338"
It seems that there are files created/modified in the c:\ue\Temp\Db directory though. Changing permissions and and changing the location of the data base directory to the logical drive c: did not solve the problem.
it opens file with the following attributes (see CreateFile function in MSDN)
CREATE_ALWAYS
GENERIC_READ
GENERIC_WRITE
FILE_SHARE_READ
FILE_SHARE_WRITE
are you able to create the file with the name in the directory manually?
so the file with the same name is not there prior to creation? (it would be logical since the name is rather random)
does it happen always, you start the program, try to download a single body and fails with the error? - i could make a version to retrieve the CreateFile error code and display it in a message box - in such a case if you are ready to check it promptly i could create it fast and PM you the link.
could you check the "Rt" subdirectory access permissions are right? the directory is created automatically by UE on start if it is not there, most likely error i guess would be "access denied" or something like that.
CREATE_ALWAYS
GENERIC_READ
GENERIC_WRITE
FILE_SHARE_READ
FILE_SHARE_WRITE
are you able to create the file with the name in the directory manually?
so the file with the same name is not there prior to creation? (it would be logical since the name is rather random)
does it happen always, you start the program, try to download a single body and fails with the error? - i could make a version to retrieve the CreateFile error code and display it in a message box - in such a case if you are ready to check it promptly i could create it fast and PM you the link.
could you check the "Rt" subdirectory access permissions are right? the directory is created automatically by UE on start if it is not there, most likely error i guess would be "access denied" or something like that.
It seems that even the subdirectory Rt is not created, at least I could not see it after a few download attempts.
Yes, I can create such a directory manually and write files with that name. I have allowed full access (chmod -R a+wrx ue) to avoid any problems with permissions, but that does not help.
Yes, the error happens always and is reproducable. No download is possible.
Since you are saying that Rt subdirectory is generated at startup, but it is not created in my system, I will try to create that directory manually and check again. I can recall that I also tried such things when I got it working at the first time.
Yes, I can create such a directory manually and write files with that name. I have allowed full access (chmod -R a+wrx ue) to avoid any problems with permissions, but that does not help.
Yes, the error happens always and is reproducable. No download is possible.
Since you are saying that Rt subdirectory is generated at startup, but it is not created in my system, I will try to create that directory manually and check again. I can recall that I also tried such things when I got it working at the first time.
it should create the Rt directory right away.
if directory is not there creating files in it will fail, CreateFile requires existing directory.
do you see temp/db directory though? it is created on start right after tmp_db directory.
then (it is only my speculation) maybe the bug in the latest wine is on directory creation if it failed because the directory already exists it doesn't set last error code to ERROR_ALREADY_EXISTS
if you have access to source maybe you can check that, the function name is CreateDirectory if the directory exists already it should set last error to SetLastError(ERROR_ALREADY_EXISTS) and return FALSE.
if directory is not there creating files in it will fail, CreateFile requires existing directory.
do you see temp/db directory though? it is created on start right after tmp_db directory.
then (it is only my speculation) maybe the bug in the latest wine is on directory creation if it failed because the directory already exists it doesn't set last error code to ERROR_ALREADY_EXISTS
if you have access to source maybe you can check that, the function name is CreateDirectory if the directory exists already it should set last error to SetLastError(ERROR_ALREADY_EXISTS) and return FALSE.
The Temp/Db directory is created, while the Temp/Rt directory is not created.
That would indicate that the problem could be solved by manually creating the Rt directory. Are you creating these two directories in a different way? If these directories are created in a sequence, maybe there needs to be a pause function in between?
I have access to the Wine sources and I am compiling these myself, but I probably don't have that much programming experience to find the flaw in a reasonable amount of time.
That would indicate that the problem could be solved by manually creating the Rt directory. Are you creating these two directories in a different way? If these directories are created in a sequence, maybe there needs to be a pause function in between?
I have access to the Wine sources and I am compiling these myself, but I probably don't have that much programming experience to find the flaw in a reasonable amount of time.
For the other problem with the libxml2 library, see the related discussion in the Wine bugtracker:
http://bugs.winehq.org/show_bug.cgi?id=5088
http://bugs.winehq.org/show_bug.cgi?id=5088
i can only guess probably it means that CreateDirectory creates temp/db but then it still indicates failure.
i removed verifying the return code in this particular case only since the program doesn't do with it anything further so maybe in the next version it will create the directory.
if in the next version it will work starting with the empty database directory despite v1.3 not working given the same scenario then the wine bug would be as above (creating directory but still returning failure). also it is legitimate to check whether creating directory has been successful so UE may do it in few other places.
does the program create the 0, 1, ..., F subdirectories in the "Bodies" directory when you start with nothing? if it aborts creating Rt it also should abort creating those directories as well, otherwise it would mean the issue is even more weird.
i removed verifying the return code in this particular case only since the program doesn't do with it anything further so maybe in the next version it will create the directory.
if in the next version it will work starting with the empty database directory despite v1.3 not working given the same scenario then the wine bug would be as above (creating directory but still returning failure). also it is legitimate to check whether creating directory has been successful so UE may do it in few other places.
does the program create the 0, 1, ..., F subdirectories in the "Bodies" directory when you start with nothing? if it aborts creating Rt it also should abort creating those directories as well, otherwise it would mean the issue is even more weird.