August 2010 - Wine-bugs - list.winehq.org

[Bug 18292] New: Make 8.3 names for LFNs more "Windows-like"
by wine-bugs＠winehq.org 10 Apr '11

10 Apr '11

http://bugs.winehq.org/show_bug.cgi?id=18292 Summary: Make 8.3 names for LFNs more "Windows-like" Product: Wine Version: 1.1.20 Platform: PC URL: http://source.winehq.org/source/dlls/kernel32/path.c OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: kernel32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: kennybobs(a)o2.co.uk When Windows creates 8.3 names for long file names, it does so in the form Progra~1 and increments the number by one with each new creation of a similar filename. So, Program Files --> Progra~1 Programmers --> Progra~2 Program Blah blah --> Progra~3 and so on. Under Wine, the 8.3 filenames seem somewhat random (PROG~HAE for example). Is it possible to implement this behaviour? It would make it easier to guess short path names, which makes it easier to add paths to the registry (when needed for workarounds, for example). -- 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.

1 8

[Bug 22059] New: when /dev/input/event* device is accessible, wine fails to consider calibration and correction factors of the linux joydev driver
by wine-bugs＠winehq.org 10 Apr '11

10 Apr '11

http://bugs.winehq.org/show_bug.cgi?id=22059 Summary: when /dev/input/event* device is accessible, wine fails to consider calibration and correction factors of the linux joydev driver Product: Wine Version: 1.1.40 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dinput AssignedTo: wine-bugs(a)winehq.org ReportedBy: corvus-wine(a)cybertrench.com Created an attachment (id=26862) --> (http://bugs.winehq.org/attachment.cgi?id=26862) joydev log with event file accessible Linux provides the possibility to correct joystick raw values automatically when accessing /dev/input/js* devices, both autodetected/scaled and "hand-calibrated" with tools like "jscal" if wine uses /dev/input/js* for joystick access, it also takes the correction factors into account, so a joystick that has been calibrated under linux, will be calibrated correctly under wine. However if the /dev/input/event* file corresponding to the joystick device is accessible (at least for reading) wine seems to bypass the joydev driver and accesses the device on a lower (event) level, thus unaware of the calibration data and correction factors - whether manually set and autodetected! As a result programs run under wine that use a joystick but offer no inbuilt calibration option (which is most, since under native win32 joysticks are calibrated system wide in the input device area of the control center) will behave strangely as joysticks are potentially off-centered - mis-scaled - axis flipped - or even unable to cross the zero position at all. Depending on the actual joystick hardware and the required corrections. the attached log1.txt shows the output of a joystick using program (il2fb flightsim) started with dinput WINEDEBIUG output grep'd for "joydev" when the event device is accessible (and the joystick is unusable due to miscalibration > WINEDEBUG=+dinput wine il2fb.exe 2>&1 |grep joydev log2.txt shows the same output with /dev/input/event5 (the joystick event device) chmodded to 000 in this case the axis and buttons are mapped completely different, but centered and scaled correctly (given that the jopystick had been calibrated under linux using jscal) for obvious reasons this bug is only visible if the axis values reported by the event device, especially min and max: ... > cur=97, min=0, max=255, fuzz=0, flat=15 ... are not equal to the actually reachable minimum and maximum values. newer joysticks often autoscale in hard/firmware and actually reach those min/max values with little need for calibration, while some, especially older models, are in dire need of correction values since the actual range (as in this case) is more like 30 to 120 -- 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.

1 5

[Bug 22212] New: Random Crashes in Sacred 2
by wine-bugs＠winehq.org 09 Apr '11

09 Apr '11

http://bugs.winehq.org/show_bug.cgi?id=22212 Summary: Random Crashes in Sacred 2 Product: Wine Version: 1.1.41 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: JakobRau(a)web.de When playing sacred 2. from time to time wine crashes (sometimes in game (singleplayer and LAN), sometimes in the menu). It does not happen too often, but it is still annoying. I am using Wine 1.1.41. on Ubuntu Lucid. I am starting the game like this: WINEPREFIX=~/.wine/sacred2 wine sacred2.exe WINEDEBUG=+relay wouldn't work, but I hope you can get some stuff out of the logfile anyway. If you can help me getting it to start with +relay, I will be happy to post the log. -- 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.

1 11

[Bug 20552] New: Memory leak in alloc_thread_tls?
by wine-bugs＠winehq.org 08 Apr '11

08 Apr '11

http://bugs.winehq.org/show_bug.cgi?id=20552 Summary: Memory leak in alloc_thread_tls? Product: Wine Version: 1.1.32 Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Valgrinding the chromium tests shows the leak 514 bytes in 2 blocks are definitely lost in loss record 796 of 971 by RtlAllocateHeap (heap.c:1421) by alloc_thread_tls (loader.c:889) by MODULE_DllThreadAttach (loader.c:1184) by start_thread (thread.c:464) on e.g. the following tests: ipc_tests: IPCChannelTest media_unittests: PipelineImplTest VideoRendererBaseTest WinAudioTest net_unittests: DirectoryListerTest ListenSocketTest ProxyScriptFetcherTest SingleThreadedProxyResolverTest TCPPingerTest TelnetServerTest URLRequestTestFTP URLRequestTestHTTP URLRequestTest To reproduce: mkdir demo cd demo wget -c http://kegel.com/wine/chromium/chromium-tests.tar.bz2 tar -xjvf chromium-tests.tar.bz2 valgrind --trace-children=yes --leak-check=full wine src/chrome/Debug/net_unittests.exe --gtest_filter=TCPPingerTest.Ping -- 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.

1 4

[Bug 16703] New: Wineconsole: Fallback from curses to window based backend
by wine-bugs＠winehq.org 08 Apr '11

08 Apr '11

http://bugs.winehq.org/show_bug.cgi?id=16703 Summary: Wineconsole: Fallback from curses to window based backend Product: Wine Version: CVS/GIT Platform: All OS/Version: All Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: wine(a)martin.st Created an attachment (id=18362) --> (http://bugs.winehq.org/attachment.cgi?id=18362) Patch for fixing the curses->user backend fallback Wineconsole currently falls back to a curses based terminal if the user has specified the other one and it is unable to create windows. However, the converse fallback doesn't work in all cases. If the curses backend fails by being unable to load the curses library, wineconsole doesn't try the window based backend. The attached patch solves this issue. -- 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.

1 13

[Bug 12808] New: indexed bitmaps support is broken
by wine-bugs＠winehq.org 08 Apr '11

08 Apr '11

http://bugs.winehq.org/show_bug.cgi?id=12808 Summary: indexed bitmaps support is broken Product: Wine Version: unspecified Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: gdi32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: misha-cn-ua(a)ya.ru This bug occurs in every application, written using AlphaControls from http://www.alphaskins.com The problem: skins in that controls usually consist of indexed 8-bit bitmaps, which at runtime are converted to 24-bit, splitted into parts and used to draw controls. Under Wine such conversion results to messed up display, the program's interface is very poor. A workaround is to manually convert skin bitmaps to 24-bit, then program work almost normally, however there some other glitches (track bars). The easiest way to show the bug is to run AlphaControls demo application under Wine. That demo can be freely downloaded from this page: http://www.alphaskins.com/ademos.php -- 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.

1 21

[Bug 16704] New: wineconsole: Allow specifying the console backend to use when wineconsole is launched implicitly
by wine-bugs＠winehq.org 08 Apr '11

08 Apr '11

http://bugs.winehq.org/show_bug.cgi?id=16704 Summary: wineconsole: Allow specifying the console backend to use when wineconsole is launched implicitly Product: Wine Version: CVS/GIT Platform: All OS/Version: All Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: wine(a)martin.st Created an attachment (id=18363) --> (http://bugs.winehq.org/attachment.cgi?id=18363) Proposed patch for fixing the issue When wineconsole is launched implicitly, when an application in wine opens a console, it currently defaults to using the user backend of wineconsole, without any possibility of changing which backend to use. The console application to launch can be changed using the WINECONSOLE environment variable, and wine appends --use-event=xx to that command line when launching the console program. Setting WINECONSOLE to "wineconsole --backend=curses" is ignored, since wineconsole chooses the user backend as soon as the --use-event argument is parsed. This isn't necessary, since the user backend is the default one. By removing the explicit setting of the user backend when parsing the --use-event argument, choosing another backend through the WINECONSOLE environment variable works as expected. The attached patch implements this proposed change. -- 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.

1 15

[Bug 18829] New: K-Meleon 1.5.x : Crash sometimes during browsing
by wine-bugs＠winehq.org 08 Apr '11

08 Apr '11

http://bugs.winehq.org/show_bug.cgi?id=18829 Summary: K-Meleon 1.5.x : Crash sometimes during browsing Product: Wine Version: 1.1.23 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jujuland.46(a)wanadoo.fr -------------------------------------------------------------------------------- K-Meleon Version : 1.52 K-Meleon profile : in program folder (set during setup) K-Meleon Extensions : none K-Meleon kplugins : standard Netscape plugins : none Wine version : 1.1.23 Ubuntu : 8.10 kernel : 2.6.27-14-generic Program Launch : ./K-M_152.sh -------------------------------------------------------------------------------- shell (K-M_152.sh) used with a console to launch K-Meleon and to keep log cd "/opt/Program Files/K-Meleon152" ./k-meleon.exe -------------------------------------------------------------------------------- Crash sometimes during browsing: --------------------------------------------------------------------------------------------- -- 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.

1 24

[Bug 22549] New: Cannot open external links in help file.
by wine-bugs＠winehq.org 07 Apr '11

07 Apr '11

http://bugs.winehq.org/show_bug.cgi?id=22549 Summary: Cannot open external links in help file. Product: Wine Version: 1.1.42 Platform: x86 URL: http://www.pmail.com/ OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: turbolad995(a)hotmail.co.uk Upon testing Pegasus Mail under Wine 1.1.42 I find you cannot open the links in its help file. Clicking on the external links in the help file is supposed to open your web browser and take you to the web page, but nothing happens when you click on these links in the help file. This might be a bug in other programs' help files? -- 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.

1 8

[Bug 15915] New: cinepak codec reportedly not installed, FourCC case mismatch
by wine-bugs＠winehq.org 07 Apr '11

07 Apr '11

http://bugs.winehq.org/show_bug.cgi?id=15915 Summary: cinepak codec reportedly not installed, FourCC case mismatch Product: Wine Version: 1.1.7 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvfw32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: hoehle(a)users.sourceforge.net CC: dmitry(a)codeweavers.com The Alien Nations / Die Völker complains that the cinepak codec is not installed. The reason is a lower/upper case mismatch in a FourCC code. Upper-case FourCC is being supplied, as the log reveals: Call msvfw32.ICOpen(43444956,44495643,00000002) ret=00493baf trace:msvideo:ICOpen (VIDC,CVID,0x00000002) Call winmm.OpenDriver(0032fda8 L"VIDC.CVID", ...) trace:driver:OpenDriver (L"VIDC.CVID", L"drivers32", ...); But dlls/iccvid/iccvid.c implements the check if (icinfo && icinfo->fccType != ICTYPE_VIDEO) where ICTYPE_VIDEO refers to 'vidc', not VIDC. The same check is in msvidc32/msvideo1.c and msrle32/msrle32.c Probably a case-insensitive check is required? For instance, msvfw32/msvideo_main.c:ICOpen() uses the case-insensitive helper function compare_fourcc(). OTOH, after the case-insensitive check perhaps wine should fill in the icopen.fccType and .fccHandler slots with the FourCC case it expects (ICTYPE_VIDEO) rather than the argument it received? It seems reasonable to commit to a known character case early on in the code and use that consistently. What is The Right Thing (TRT), i.e. what to store in fccType? In any case, a case fix lets "Die Völker" work past this issue (and crash later in ddraw, but that's another issue). -- 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.

1 14