September 2012 - Wine-Bugs - list.winehq.org

[Bug 31098] New: 115 Udown can't work since I installed it
by wine-bugs＠winehq.org Dec. 5, 2020

Dec. 5, 2020

http://bugs.winehq.org/show_bug.cgi?id=31098 Bug #: 31098 Summary: 115 Udown can't work since I installed it Product: Wine Version: 1.5.3 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: litimetal(a)gmail.com Classification: Unclassified I downloaded http://pc.115.com/download/115UDown_3.2.8.15.exe then installed it on my fedora 16.But I can't launch it and I know nothing about how to solve it. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

2 28

[Bug 30627] New: Appending text to a large richedit is very slow
by wine-bugs＠winehq.org Dec. 5, 2020

Dec. 5, 2020

http://bugs.winehq.org/show_bug.cgi?id=30627 Bug #: 30627 Summary: Appending text to a large richedit is very slow Product: Wine Version: 1.5.3 Platform: x86 OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: richedit AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Classification: Unclassified Although the pathological case reported in bug 30614 is now fixed, all is not yet well. When repeatedly appending lines, builtin riched20 starts out about 3x slower than native, and at 40k lines, is about 10x slower than native. This is painful for long-running apps that use richedit for verbose logs. (Measured with the attached program and today's git on my i5, appending 1000 lines to an empty richedit control takes builtin hidden: 907 ms builtin visible: 4862 ms native hidden: 368 ms native visible: 4530 ms Appending 1000 lines to a richedit control which already contains 40000 lines takes: builtin hidden: 22169 ms builtin visible: 33002 ms native hidden: 1750 ms native visible: 4807 ms ) Building wine's riched20 with -O1 -fno-inline and profiling with 'perf' shows 62.60% ME_WrapMarkedParagraphs 12.07% ME_PaintContent 9.99% ME_InvalidateMarkedParagraph at 50k lines. Initial inspection seems to show that most of the time in ME_WrapMarkedParagraphs is in the function itself, not in any called functions. Adding trace statements to all callers of ME_WrapMarkedParagraphs, I see one call during EM_EXSETSEL: ME_Repaint Calling ME_WrapMarkedParagraphs and four calls during EM_REPLACESEL: ME_UpdateRepaint Calling ME_WrapMarkedParagraphs ME_UpdateScrollBar Calling ME_WrapMarkedParagraphs ME_Repaint Calling ME_WrapMarkedParagraphs ME_UpdateScrollBar Calling ME_WrapMarkedParagraphs This is the case whether the window is hidden or not. Bug 13355 (which Dylan says is separate, since it's about richedit being slow on a single large call to WM_SETTEXT) suggests in comment 14 ways to remove some redundant calls to ME_WrapMarkedParagraphs, and to let one of them return early. In addition to those ideas, for this bug, it would be useful if ME_WrapMarkedParagraphs (and ME_InvalidateMarkedParagraph) could avoid making a linear scan across all paragraphs. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

2 18

[Bug 26541] New: Dragon Saga doesn't start
by wine-bugs＠winehq.org Dec. 5, 2020

Dec. 5, 2020

http://bugs.winehq.org/show_bug.cgi?id=26541 Summary: Dragon Saga doesn't start Product: Wine Version: 1.3.16 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Installing DragonSagaInstaller-0.1.29-20110216.msi went fine, but $ cd ~/.wine/drive_c/Program Files/Gravity/Dragon Saga $ wine Release/DragonSaga.EXE fails like this: fixme:ntdll:NtQueryInformationProcess (process=0xffffffff) Unimplemented information class: ProcessDebugFlags Unhandled exception: privileged instruction in 32-bit code (0x0123980c). Backtrace: =>0 0x0123980c in dragonsaga (+0xe4980c) (0x0032fea0) 1 0x7edaa2fc call_process_entry+0xb() in kernel32 (0x0032feb8) 2 0x7edac593 start_process+0x52(peb=0x1) [dlls/kernel32/process.c:1086] in kernel32 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

2 6

[Bug 28089] New: exception handling code touches stack for exceptions handled by the debugger
by wine-bugs＠winehq.org Dec. 5, 2020

Dec. 5, 2020

http://bugs.winehq.org/show_bug.cgi?id=28089 Summary: exception handling code touches stack for exceptions handled by the debugger Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll AssignedTo: wine-bugs(a)winehq.org ReportedBy: bernhardloos(a)googlemail.com Created an attachment (id=35971) --> (http://bugs.winehq.org/attachment.cgi?id=35971) a hack to work around the problem Wine places the CONTEXT and EXCEPTION_RECORD structures onto the stack past ESP during the unix signal handler and continues with most of the exception handling code outside of the signal handler. Unfortunately and contrary to windows behavior the debugger gets notified only after this happens. Windows doesn't touch the stack at all, if the exception is handled by the debugger. This makes it very hard to single step trough code which keeps useful data past ESP (securom 8 for example). it's easy to show with this small test: void foo() { char *x = 0, *y = 0, *from = 0, *to = 0; char c; x = &c; y = &c - 500; while (y != x) *y++ = 0x55; c = 0x77; /* single step a few times here */ y = &c - 500; while (y != x) { if (*y != 0x55) if (from) to = y; else from = y; y++; } /* to and from shoudl be NULL */ } -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

2 13

[Bug 18508] New: Sony Acid Pro 7 Fails to Install
by wine-bugs＠winehq.org Dec. 4, 2020

Dec. 4, 2020

http://bugs.winehq.org/show_bug.cgi?id=18508 Summary: Sony Acid Pro 7 Fails to Install Product: Wine Version: unspecified Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P3 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: aliendude5300(a)gmail.com Created an attachment (id=21153) --> (http://bugs.winehq.org/attachment.cgi?id=21153) What debug messages appeared during installation of Sony Acid Pro 7 on default Wine installation. The installer for Sony Acid Pro 7 fails to install the necessary files and exits in Wine 1.1.21. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

2 16

[Bug 15301] New: Biliardo 2 installer terminates on launch
by wine-bugs＠winehq.org Dec. 4, 2020

Dec. 4, 2020

http://bugs.winehq.org/show_bug.cgi?id=15301 Summary: Biliardo 2 installer terminates on launch Product: Wine Version: CVS/GIT Platform: PC URL: http://web.tiscali.it/chiesi/software/ita/biliardo2.html OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: nodisgod(a)yahoo.com Created an attachment (id=16125) --> (http://bugs.winehq.org/attachment.cgi?id=16125) Biliardo 2 relay log (rzipped) With current Git (wine-1.1.4-392-gaf78a7b), when attempting to launch the Biliardo 2 installer, a window momentarily appears, but the installer terminates without any further messages. From examination of relay traces, there seems to be an exception being raised while the installer runs, possibly causing the termination. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

2 17

[Bug 21881] New: iScreensaver Designer 3.5 has encountered a problem.
by wine-bugs＠winehq.org Dec. 4, 2020

Dec. 4, 2020

http://bugs.winehq.org/show_bug.cgi?id=21881 Summary: iScreensaver Designer 3.5 has encountered a problem. Product: Wine Version: unspecified Platform: x86 OS/Version: Mac OS X 10.5 Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: reedercolin(a)gmail.com A window comes up saying that iScreensaver.exe encountered a serious problem. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

2 15

[Bug 16208] New: Yousendit desktop tool does not work
by wine-bugs＠winehq.org Dec. 4, 2020

Dec. 4, 2020

http://bugs.winehq.org/show_bug.cgi?id=16208 Summary: Yousendit desktop tool does not work Product: Wine Version: 1.1.9 Platform: Other OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: mico(a)kabelfoon.nl Created an attachment (id=17447) --> (http://bugs.winehq.org/attachment.cgi?id=17447) verbose logging of the application start The yousendit desktop tool does not work. A dialog appears with the text: We're sorry, but we are unable to find the required YouSendIt files. Please reinstall the application. Terminal output is just one line: mico(a)ubuntu64:~$ env WINEPREFIX="/home/mico/.wine" wine "C:\Program Files\YouSendIt\Express\YouSendIt.exe" fixme:jscript:String_toLowerCase Re-installation does not solve the issue Attached a debug log running the app. This is a follow-on of the installation problem which is closed here: http://bugs.winehq.org/show_bug.cgi?id=16159 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

2 27

[Bug 25087] New: GPU-Z shows no informations
by wine-bugs＠winehq.org Dec. 3, 2020

Dec. 3, 2020

http://bugs.winehq.org/show_bug.cgi?id=25087 Summary: GPU-Z shows no informations Product: Wine Version: 1.3.6 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: testing.tigerwolf(a)mail.com Created an attachment (id=31809) --> (http://bugs.winehq.org/attachment.cgi?id=31809) GPU-Z launching back trace GPU-Z shows any information : all fields remains empty. OS : Ubuntu 10.10 amd-64 GPU : ATI Radeon HD Tested version : GPU-Z v0.4.8 Wine : 1.3.6 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

2 28

[Bug 20888] New: Use XDG Base Directory Specification
by wine-bugs＠winehq.org Dec. 3, 2020

Dec. 3, 2020

http://bugs.winehq.org/show_bug.cgi?id=20888 Summary: Use XDG Base Directory Specification Product: Wine Version: 1.1.33 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: cristiklein+wine(a)gmail.com Hello, The XDG Base Directory Specification [1]. Aims at solving two issues: 1) User's home directory is currently filled with hidden files. 2) Application settings, cache and data files are not separated. Wine does not currently respect this standard. - The "*.reg" files and "dosdevices" folder should be moved to $XDG_CONFIG_HOME/wine. - drive_c should be moved to $XDG_DATA_HOME/wine [1] http://standards.freedesktop.org/basedir-spec/basedir-spec-0.6.html -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

2 7