January 2005 - Wine-Bugs - list.winehq.org

[Bug 54] PrgWin95: Wrong background for checkboxes, radiobuttons, etc.
by Wine Bugs Jan. 25, 2005

Jan. 25, 2005

http://bugs.winehq.org/show_bug.cgi?id=54 ------- Additional Comments From ikrakow_1999(a)yahoo.com 2005-25-01 12:27 ------- Looks like it works in Wine 20050111. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 52] PrgWin95: Problems with access to the root window
by Wine Bugs Jan. 25, 2005

Jan. 25, 2005

http://bugs.winehq.org/show_bug.cgi?id=52 ------- Additional Comments From ikrakow_1999(a)yahoo.com 2005-25-01 12:23 ------- Still a bug. In Wine 20050511, produces the following messages: fixme:dc:LockWindowUpdate (0x10020), partial stub! fixme:dc:GetDCEx not yet supported - see source fixme:dc:LockWindowUpdate (nil), partial stub! before scrambling the screen. Still does not restore the screen to its original state, as it does when running on Windows XP Home. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 2498] Y-Axis mouse movement issues
by Wine Bugs Jan. 25, 2005

Jan. 25, 2005

http://bugs.winehq.org/show_bug.cgi?id=2498 ------- Additional Comments From reif(a)earthlink.net 2005-25-01 11:15 ------- I just posted a patch to wine-patches that should fix this problem. Please try it. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 2498] Y-Axis mouse movement issues
by Wine Bugs Jan. 25, 2005

Jan. 25, 2005

http://bugs.winehq.org/show_bug.cgi?id=2498 ------- Additional Comments From saulius.krasuckas(a)elst.vtu.lt 2005-25-01 07:04 ------- during regression-test I use CDT timezone, so the date formatted in such way: "Mon Sep 06 15:23:27 2004 CDT" to format it I: 1, go to the wine-cvs mailing list. 2, select the patch of interest (I would prefer the earliest patch of "Sep 06 2004" as there may arise time differences because of difference of the timezones used by Alexandre's submission tool and your cvs-client). 3, copy down the date of the patch ("Mon Sep 06 2004 - 15:23:26 CDT"). 4, rearrange it by moving "2004 " just before the "CDT " begins. 5, eliminate "- " junk. 6, change time-part by 1 second. to make sure the patch will get into your CVS tree I increase the time. for the patch to not get into the tree I decrease the time. in my example I have increased it. to see the differences in non-abstract way: "Mon Sep 06 2004 - 15:23:26 CDT" (from the web-page) "Mon Sep 06 15:23:27 2004 CDT" (to the cvs-client) not really so hard, huh? sorry, if this is redundant. I have learned no other way around for a while. and I would suggest the ending patch to be of "Wed Sep 08 2004 - 19:30:30 CDT", as it is the last patch this day commited on "Sept 8, 2004". Hence: "Wed Sep 08 2004 - 19:30:30 CDT" (from the web-page) "Wed Sep 08 19:30:31 2004 CDT" (to the cvs-client) and it seems you are stuck with two different regressing patches, living each near other. when the first offending patch is found, I suggest to test the Wine by traveling from the found patch to the one of "Fri Sep 10 2004 - 17:30:06 CDT", lets say. HTH, corrections are welcome. [1] http://www.winehq.org/hypermail/wine-cvs/2004/09/index.html -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 2677] New: Ciel install fails at instal shield initialisation
by Wine Bugs Jan. 25, 2005

Jan. 25, 2005

http://bugs.winehq.org/show_bug.cgi?id=2677 Summary: Ciel install fails at instal shield initialisation Product: Wine Version: 20041201 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-ole AssignedTo: wine-bugs(a)winehq.org ReportedBy: diablo43000(a)yahoo.com Overview Description: Installing Ciell on Fedora core 3 fails at install shiel initialization Steps to Reproduce: 1) copy ~/.wine/drive_c/windows/system/STDOLE2.TLB to ~/.wine/drive_c/windows/system/STDOLE32.TLB so that the install shield starts 2) #winefile 3) move to cdrom (previously added in ~/.wine/dosdevices) 4) select install application Actual Results: recived an error in a new window: "An application support file cud not be installed. (0x80004003)" only button present "OK" when pressed install shiel dissapears Expected Results: install shield continues to run and installs application Build Date & Platform: Build 2004-12-01 on PC Linux fedora core 3 Kernel version 2.6.10-1.741 Additional Builds and Platforms: none Additional Information: Console output: fixme:mmtime:timeBeginPeriod Stub; we set our timer resolution at minimum fixme:ole:RegisterTypeLib Registering non-oleautomation interface! fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:RegisterTypeLib Registering non-oleautomation interface! fixme:ole:RegisterTypeLib Registering non-oleautomation interface! fixme:ole:RegisterTypeLib Registering non-oleautomation interface! fixme:ole:RegisterTypeLib Registering non-oleautomation interface! fixme:ole:RegisterTypeLib Registering non-oleautomation interface! fixme:ole:RegisterTypeLib Registering non-oleautomation interface! fixme:ole:RegisterTypeLib Registering non-oleautomation interface! fixme:ole:RegisterTypeLib Registering non-oleautomation interface! err:ole:MARSHAL_Register_Proxy Already have mid? fixme:ole:CoUnmarshalInterface Failed to create instance of unmarshaller {0000030b-0000-0000-c000-000000000046}. fixme:ole:_unmarshal_interface Marshalling interface {aa7e2068-cb55-11d2-8094-00104b1f9838} failed with 800401f0 fixme:ole:deserialize_param failed to stuballoc in TKIND_RECORD. fixme:ole:TMStubImpl_Invoke Failed to deserialize param pTransferEvents, hres 800401f0 fixme:ole:CoUnmarshalInterface Failed to create instance of unmarshaller {0000030b-0000-0000-c000-000000000046}. fixme:ole:_unmarshal_interface Marshalling interface {aa7e2068-cb55-11d2-8094-00104b1f9838} failed with 800401f0 fixme:ole:deserialize_param failed to stuballoc in TKIND_RECORD. fixme:ole:TMStubImpl_Invoke Failed to deserialize param pTransferEvents, hres 800401f0 fixme:ole:PipeBuf_Release Free all stuff fixme:ole:PipeBuf_Release Free all stuff fixme:ole:PipeBuf_Release Free all stuff fixme:ole:PipeBuf_Release Free all stuff fixme:ole:PipeBuf_Release Free all stuff fixme:ole:PipeBuf_Release Free all stuff fixme:ole:PipeBuf_Release Free all stuff fixme:ole:PipeBuf_Release Free all stuff fixme:ole:PipeBuf_Release Free all stuff fixme:ole:PipeBuf_Release Free all stuff fixme:ole:read_pipe Read only 0 of 4 bytes from 0xac. fixme:ole:_StubReaderThread Failed with hres 80004005 fixme:mmtime:timeBeginPeriod Stub; we set our timer resolution at minimum thank you -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 2676] Wine-20050111 raises "Uninitialized mutex in pthread_mutex_trylock_basic"
by Wine Bugs Jan. 25, 2005

Jan. 25, 2005

http://bugs.winehq.org/show_bug.cgi?id=2676 ------- Additional Comments From mirya(a)ukrpost.net 2005-25-01 02:53 ------- Maybe I forgot to specify env. notes :): FreeBSD 5_RELENG kernel with 5_3_RELENG base, i686, 128Mb RAM, 1 400MHz CPU, wine is set up upon WinXP SP2 box. Than more sad news: tried the same on another machine - again FreeBSD 5_RELENG kernel with 5_3_RELENG base, but P4, 256Mb RAM, 1 1.7GHz CPU, standalone wine. Setting up MSIE6 with sidenet script fails 'cause of the problem reported somewhere in MSIE downloader (russian version ie6setup_RU.exe, 493816 bytes, md5() == 1aced53d28ac95474dd3dc47ce20582a). Again, using wine binary package (ftp://ftp2.freebsd.org/pub/FreeBSD/ports/i386/packages-5-stable/All/wine-20…, 8146197 bytes, md5() == c0473a8d9dea3b7ed72d731073c677d3), got the log: $ wine ie6setup_RU.exe fixme:file:get_default_drive_device auto detection of DOS devices not supported on this platform fixme:ntdll:NtQueryVolumeInformationFile device info not properly supported on this platform err:heap:HEAP_CreateSystemHeap system heap base address 0x80000000 not available Please use the registry key HKEY_CURRENT_CONFIG\Software\Fonts\LogPixels to set the screen resolution and remove the "Resolution" entry in the config file fixme:advapi:DecryptFileA "C:\\windows\\temp\\IXP001.TMP\\" 00000000 fixme:ntdll:NtQueryVolumeInformationFile device info not properly supported on this platform err:heap:HEAP_CreateSystemHeap system heap base address 0x80000000 not available Please use the registry key HKEY_CURRENT_CONFIG\Software\Fonts\LogPixels to set the screen resolution and remove the "Resolution" entry in the config file fixme:cursor:CURSORICON_SimulateLoadingFromResourceW Animated icons not correctly implemented! 0x360000 fixme:cursor:CURSORICON_SimulateLoadingFromResourceW icon entry found! 0x360000 fixme:cursor:CURSORICON_SimulateLoadingFromResourceW icon size ok. offset=0x360074 fixme:setupapi:SETUPX_CreateStandardLDDs LDID_SRCPATH: what exactly do we have to do here ? fixme:font:load_VDMX No suitable ratio found fixme:file:get_default_drive_device auto detection of DOS devices not supported on this platform fixme:font:load_VDMX No suitable ratio found fixme:setupapi:GenInstall16 unsupported flag: GENINSTALL_DO_REGSRCPATH fixme:setupapi:vcpUICallbackProc16 (0xcbe0, 0705, 0000, 00000000, 001aa67c) - semi-stub fixme:setupapi:vcpUICallbackProc16 (0xcbe0, 070f, 0000, 00000000, 001aa67c) - semi-stub fixme:setupapi:vcpUICallbackProc16 (0xcbe0, 0710, 0000, 00000000, 001aa67c) - semi-stub fixme:setupapi:vcpUICallbackProc16 (0xcbe0, 070b, 0000, 00000000, 001aa67c) - semi-stub fixme:setupapi:vcpUICallbackProc16 (0xcbe0, 070c, 0000, 00000000, 001aa67c) - semi-stub fixme:setupapi:GenInstall16 unsupported flag: GENINSTALL_DO_CFGAUTO fixme:setupapi:GenInstall16 unsupported flag: GENINSTALL_DO_REGSRCPATH fixme:setupapi:GenInstall16 unsupported flag: GENINSTALL_DO_CFGAUTO fixme:setupapi:GenInstall16 unsupported flag: GENINSTALL_DO_REGSRCPATH fixme:setupapi:GenInstall16 unsupported flag: GENINSTALL_DO_CFGAUTO fixme:font:load_VDMX No suitable ratio found fixme:font:load_VDMX No suitable ratio found fixme:setupapi:GenInstall16 unsupported flag: GENINSTALL_DO_REGSRCPATH fixme:setupapi:GenInstall16 unsupported flag: GENINSTALL_DO_CFGAUTO Fatal error 'Uninitialized mutex in pthread_mutex_trylock_basic' at line 474 in file /usr/src/lib/libpthread/thread/thr_mutex.c (errno = 22) wine: Unhandled exception (thread 0015), starting debugger... fixme:ntdll:NtQueryVolumeInformationFile device info not properly supported on this platform err:heap:HEAP_CreateSystemHeap system heap base address 0x80000000 not available WineDbg starting on pid 0xa Couldn't initiate DbgHelp fixme:seh:UnhandledExceptionFilter Unhandled error on debug event: 0 Unhandled exception: assertion failed in 32-bit code (0xb7f9c1d7). file_set_error: Bad address file_set_error: Bad address In 32 bit mode. Register dump: CS:001f SS:002f DS:002f ES:002f FS:126f GS:0097 EIP:b7f9c1d7 ESP:00e7f950 EBP:00e7f96c EFLAGS:00000202( - 00 - - I1) EAX:00000000 EBX:b80135ec ECX:00000005 EDX:000003e3 ESI:00e7f98c EDI:00e7f984 Stack dump: 0x00e7f950: b7f9127e 000003e4 00000006 00000000 0x00e7f960: 00000000 00000212 b80135ec 00e7f9bc 0x00e7f970: b8003627 00000006 00e7f98c 00000000 0x00e7f980: b80035f2 00343232 b7ffe21e ffffffdf 0x00e7f990: ffffffff ffffffff ffffffff b7f0a992 0x00e7f9a0: b7f34c00 b98be840 010963b0 00e7f9b4 024d: sel=126f base=00116000 limit=00001fff 32-bit rw- Backtrace: file_set_error: Bad address =>1 0xb7f9c1d7 (0x00e7f96c) 2 0xb8003627 (0x00e7f9bc) file_set_error: Bad address 0xb7f9c1d7: jb 0xb7f9c1bc Wine-dbg> -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 2498] Y-Axis mouse movement issues
by Wine Bugs Jan. 25, 2005

Jan. 25, 2005

http://bugs.winehq.org/show_bug.cgi?id=2498 ------- Additional Comments From aethyr7(a)hotmail.com 2005-25-01 01:12 ------- Created an attachment (id=749) --> (http://bugs.winehq.org/attachment.cgi?id=749&action=view) requested WINEDEBUG output Here's the output from WINEDEBUG=+dinput,+event I just started up the program, moved my mouse around for a bit, then killed wine. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 2498] Y-Axis mouse movement issues
by Wine Bugs Jan. 25, 2005

Jan. 25, 2005

http://bugs.winehq.org/show_bug.cgi?id=2498 ------- Additional Comments From aethyr7(a)hotmail.com 2005-25-01 00:31 ------- I'm trying to do regression testing, but it's pretty slow going, as it seems like there were a lot of commits done all at once. Basically, here's the situation: cvs -z3 -q update -PAd -D "Sept 7, 2004" Mouse is fine. cvs -z3 -q update -PAd -D "Sept 8, 2004" No mouse movement at all. cvs -z3 -q update -PAd -D "Sept 9, 2004" Messed up movement along Y-axis (what I saw when I made this bug report). I just don't know how to figure out what specific cvs commits broke it. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 2017] Photoshop 7.0 no longer works
by Wine Bugs Jan. 24, 2005

Jan. 24, 2005

http://bugs.winehq.org/show_bug.cgi?id=2017 ------- Additional Comments From v8p53fo02(a)sneakemail.com 2005-24-01 18:45 ------- Andrea, Thanks for that. That's narrowed down the problem a little (I think I may know what's wrong) Can I ask you to repeat the procedure with wine running in synchronous mode (see your Wine config file and set "Synchronous" = "Y" in the [X11DRV] section), and once again, post the results here. It would also help to know what version of wine you're using. Many thanks -Rob. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 2616] Text invisible in menus and dialogues
by Wine Bugs Jan. 24, 2005

Jan. 24, 2005

http://bugs.winehq.org/show_bug.cgi?id=2616 ------- Additional Comments From kilgus(a)fuenfsieben.de 2005-24-01 12:57 ------- News: I set up my system from scratch using SuSE 9.2, current (again already updated) version of wine being 20050111 now. Display is a little bit stringy but text in menus and dialogues is visible again. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0