Re: Does auto-apt work to get wine dependencies in source code?
--Sorry about the HTML in the earlier message. Was thinking of running some tests but the list of dependencies on the website seems outdated, apt-get build-dep does not work. Is that with the ubuntu-wine ppa enabled? There are two answers to that question, surprisingly. (1) bitbox In the instructions it looks like the wine ppa repository can be installed the Debian way. But I did that and here's the result. E: You must put some 'source' URIs in your sources.list So, I had to add the wine-ppa by manually adding to the sources.list. (2) non bitbox This morning a new version of the i386 photo function was added, and now the depencencies install. Conclusion: This afternoon I was able to update all dependencies and compile without a problem using (with modifications above) the bitbox instructions. Compiled only. Did not install because I needed symlinks, but at least I know where I am and what I have to do. Susan
Re: Does auto-apt work to get wine dependencies in source code?
Was thinking of running some tests but the list of dependencies on the website seems outdated, apt-get build-dep does not work.Is that with the ubuntu-wine ppa enabled?There are two answers to that question, surprisingly. (1) bitboxIn the instructions it looks like the wine ppa repository can be installed the Debian way. But I did that and here's the result. E: You must put some 'source' URIs in your sources.listSo, I had to add the wine-ppa by manually adding to the sources.list.(2) non bitboxThis morning a new version of the i386 photo function was added, and now the depencencies install. Conclusion: This afternoon I was able to update all dependencies and compile without a problem using (with modifications above) the bitbox instructions. Compiled only. Did not install because I needed symlinks, but at least I know where I am and what I have to do. Susan
Does auto-apt work to get wine dependencies in source code?
Hello, Was thinking of running some tests but the list of dependencies on the website seems outdated, apt-get build-dep does not work.
FYI ubuntu PPA 64-bit did not update wine1.5-386
just letting you know. assume it will be available later.
FYI: Pangolin script needs libfreeytype6-dev:386 but it cannot be installed
The configure script seems to be looking for libfreetype6-dev:386 but this cannot be installed without removing the compilers and other files Should I alert Ubuntu? Isn't this their problem? Susan
difficulties compiling or installing git on precise pagolin
In the development version of ubuntu, wine can neither be compiled nor installed. ~$ sudo apt-get build-dep wine1.3 [sudo] password for susan: Reading package lists... Done Building dependency tree Reading state information... Done The following packages have unmet dependencies: ia32-libs : Depends: ia32-libs-multiarch libsane-dev : Depends: libjpeg-dev Depends: libtiff4-dev but it is not going to be installed E: Build-dependencies for wine1.3 could not be satisfied. $ sudo apt-get install wine1.3 The following packages have unmet dependencies: wine1.3 : Depends: ia32-libs (= 1.6) but it is not going to be installed ia32-libs is now a transitional package. There is no ia32-libs-multiarch. It has been replaced by ia32-libs-multiarch:386. It seems as if the problem can first be solved by installing ia32-libs-multiarch:386, but when I try to do this it involves removing other packages that seem important. ??
ubuntu ppa -- nice to have on development version too
There was discussion about putting a daily wine build on the ubuntu ppa. I'd like to put in a word for having it on the development version (currently oneiric) as well as the stable version (natty). Right now wine only seems to have a natty ppa.
FYI - build-dep can no longer be done for git
There have been a couple of replacement packages. $ sudo apt-get build-dep wine1.3 The following packages have unmet dependencies: ia32-libs : Depends: lib32v4l-0 but it is not going to be installed lib32v4l-dev : Depends: libv4l-0 (= 0.8.3-2) but 0.8.5-3ubuntu1 is to be installed Depends: lib32v4l-0 (= 0.8.3-2) but it is not going to be installed Depends: libv4l-dev (= 0.8.3-2) but 0.8.5-3ubuntu1 is to be installed E: Build-dependencies for wine1.3 could not be satisfied.
shouldn't the 1.3 dependencies include binfmt-support and lib32nss
Just wondering. apt-get build-dep wine1.3 does not load binfmt-support and lib32nss... Installation of natspeak requires them. The installation script tries to grab them but failed for me.
Re: Regression today?
Susan Cragin wrote: I think a regression was introduced today. I got the following trying to run NatSpeak 11.0 with today's git. wine-1.3.22-255-g4c0c0d3 Should I do a regression test and file a bug, or is it obvious from this? Or is it me -- something to do with my new Oneiric Ocelot? Or the new 3.0 kernel?The 3.0 kernel works for me now (3.0-rc4) as good as any of the previousstable releases. Before -rc4 I get a kernel oops after the radeon GPUlockup + soft reset I get with SC2. Now I'm left with the GPU lockup butprevious kernels show the same problem.Hmmm... I have the 3.0-1.2.
Regression today?
I think a regression was introduced today. I got the following trying to run NatSpeak 11.0 with today's git. wine-1.3.22-255-g4c0c0d3 Should I do a regression test and file a bug, or is it obvious from this? Or is it me -- something to do with my new Oneiric Ocelot? Or the new 3.0 kernel? susan@ubuntu:~/.wine/drive_c/Program Files/Nuance/NaturallySpeaking11/Program$ wine natspeak err:service:service_send_start_message service LDragonSvc failed to start fixme:iphlpapi:NotifyAddrChange (Handle 0xc2e91c, overlapped 0xc2e900): stub wine: configuration in '/home/susan/.wine' has been updated. fixme:ole:CoInitializeSecurity ((nil),-1,(nil),(nil),0,3,(nil),0,(nil)) - stub! fixme:wbemprox:wbem_locator_ConnectServer 0x134288, LROOT\\CIMV2, (null), (null), (null), 0x, (null), (nil), 0xfcea54) fixme:mountmgr:harddisk_ioctl returning zero-filled buffer for IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS fixme:mountmgr:harddisk_ioctl unsupported ioctl 74080 fixme:wbemprox:wbem_locator_ConnectServer 0x135fd0, LROOT\\CIMv2, (null), (null), (null), 0x, (null), (nil), 0x10cea5c) fixme:mountmgr:harddisk_ioctl returning zero-filled buffer for IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS fixme:mountmgr:harddisk_ioctl unsupported ioctl 74080 fixme:wbemprox:wbem_locator_ConnectServer 0x135fd0, LROOT\\CIMv2, (null), (null), (null), 0x, (null), (nil), 0xfcea5c) fixme:mountmgr:harddisk_ioctl returning zero-filled buffer for IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS fixme:mountmgr:harddisk_ioctl unsupported ioctl 74080 fixme:wbemprox:wbem_locator_ConnectServer 0x136020, LROOT\\CIMv2, (null), (null), (null), 0x, (null), (nil), 0x10cea5c) fixme:wbemprox:wbem_locator_ConnectServer 0x136020, LROOT\\WMI, (null), (null), (null), 0x, (null), (nil), 0xfcea54) fixme:reg:RegSetKeySecurity :(0x60,4,0xd9ba9c): stub fixme:mountmgr:harddisk_ioctl returning zero-filled buffer for IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS fixme:mountmgr:harddisk_ioctl unsupported ioctl 74080 fixme:wbemprox:wbem_locator_ConnectServer 0x136020, LROOT\\CIMv2, (null), (null), (null), 0x, (null), (nil), 0x10cea5c) susan@ubuntu:~/.wine/drive_c/Program Files/Nuance/NaturallySpeaking11/Program$
Re: Regression in ioctl
This popped up today, and prevented me from opening my program. susan@ubuntu:~/.wine/drive_c/Program Files/Nuance/NaturallySpeaking10/Program$ wine natspeak fixme:mountmgr:harddisk_ioctl returning zero-filled buffer for IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS fixme:mountmgr:harddisk_ioctl unsupported ioctl 74080 fixme:mountmgr:harddisk_ioctl returning zero-filled buffer for IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS fixme:mountmgr:harddisk_ioctl unsupported ioctl 74080 fixme:mountmgr:harddisk_ioctl returning zero-filled buffer for IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS fixme:mountmgr:harddisk_ioctl unsupported ioctl 74080 fixme:reg:RegSetKeySecurity :(0x54,4,0xb05a50): stub fixme:mountmgr:harddisk_ioctl returning zero-filled buffer for IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS fixme:mountmgr:harddisk_ioctl unsupported ioctl 74080 susan@ubuntu:~/.wine/drive_c/Program Files/Nuance/NaturallySpeaking10/Program$ I had just compiled today's git. wine-1.3.20-44-gddad22d Is there a regression test in my future? Hi,When did you compiled the last time? yesterday or some month ago?I compile every git. So last compile was the day before this one. However, I don't remember if I tried to run NatSpeak, so the error might be as much as two days old?
Regression in ioctl
This popped up today, and prevented me from opening my program. susan@ubuntu:~/.wine/drive_c/Program Files/Nuance/NaturallySpeaking10/Program$ wine natspeak fixme:mountmgr:harddisk_ioctl returning zero-filled buffer for IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS fixme:mountmgr:harddisk_ioctl unsupported ioctl 74080 fixme:mountmgr:harddisk_ioctl returning zero-filled buffer for IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS fixme:mountmgr:harddisk_ioctl unsupported ioctl 74080 fixme:mountmgr:harddisk_ioctl returning zero-filled buffer for IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS fixme:mountmgr:harddisk_ioctl unsupported ioctl 74080 fixme:reg:RegSetKeySecurity :(0x54,4,0xb05a50): stub fixme:mountmgr:harddisk_ioctl returning zero-filled buffer for IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS fixme:mountmgr:harddisk_ioctl unsupported ioctl 74080 susan@ubuntu:~/.wine/drive_c/Program Files/Nuance/NaturallySpeaking10/Program$ I had just compiled today's git. wine-1.3.20-44-gddad22d Is there a regression test in my future?
today's git failed to build for me
I just downloaded today's git and tried to build it. The following are the make errors in the terminal output. Below that, separated by a line, are the installation errors. make[1]: Entering directory `/home/susan/wine/dlls/winejack.drv' gcc -m32 -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wstrict-prototypes -Wtype-limits -Wwrite-strings -Wpointer-arith -Wlogical-op -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=0 -o audio.o audio.c audio.c: In function ‘JACK_DriverProc’: audio.c:2419:50: error: ‘RTLD_NOW’ undeclared (first use in this function) audio.c:2419:50: note: each undeclared identifier is reported only once for each function it appears in audio.c:2443:5: warning: implicit declaration of function ‘MessageBoxA’ audio.c:2443:78: error: ‘MB_OK’ undeclared (first use in this function) make[1]: *** [audio.o] Error 1 make[1]: Leaving directory `/home/susan/wine/dlls/winejack.drv' make: *** [dlls/winejack.drv] Error 2 -- make[1]: Entering directory `/home/susan/wine/dlls/winejack.drv' gcc -m32 -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wstrict-prototypes -Wtype-limits -Wwrite-strings -Wpointer-arith -Wlogical-op -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=0 -o audio.o audio.c audio.c: In function ‘JACK_DriverProc’: audio.c:2419:50: error: ‘RTLD_NOW’ undeclared (first use in this function) audio.c:2419:50: note: each undeclared identifier is reported only once for each function it appears in audio.c:2443:5: warning: implicit declaration of function ‘MessageBoxA’ audio.c:2443:78: error: ‘MB_OK’ undeclared (first use in this function) make[1]: *** [audio.o] Error 1 make[1]: Leaving directory `/home/susan/wine/dlls/winejack.drv' make: *** [install] Error 2
re: today's git does not compile
Try switching from -O2 to -O1 with configure CFLAGS=-g -O1 and rebuild. Does that help? Yes. That works. Regardless of whether that gets you past the problem, please file a bug in launchpad against gcc-4.5. Ideally they'd want you to run with -save-temps and give them a copy of pen.i. https://bugs.launchpad.net/ubuntu/+source/gcc-4.5/+bug/704633 Here's the bug. I http://www.network-theory.co.uk/docs/gccintro/gccintro_36.html Dan, I can't work the -save-temps option. All three give me no input files. /wine-git$ gcc -save-temps /wine-git$ gcc -save-temps=cwd (or =obj) gcc: no input files
FYI: GCC-4.6 rebuild tests
GCC-4.6 has more build failures than mine. Here's the info. They don't test wine, apparently. It's not on the list. Maybe I can add it, or get it added. -Forwarded Message- From: Matthias Klose d...@ubuntu.com Sent: Jan 19, 2011 10:28 AM To: ubuntu-devel ubuntu-devel-annou...@lists.ubuntu.com, ubuntu-devel ubuntu-de...@lists.ubuntu.com Subject: GCC-4.6 rebuild tests [ Note that GCC-4.6 will not be used for natty / 11.04, but we consider using this version for the O-series / 11.10 ] A test rebuild of natty/main using the current GCC version from the trunk was finished last week. While only one internal compiler error was found, some more build failures were seen due to new warnings and more strict frontends. A list of build failure can be seen at http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20110111-gcc-natty.html If a package appears in the `superseded' section, it doesn't mean that the build failure with GCC-4.6 is fixed. Some comments and hints for fixes can be found at https://wiki.ubuntu.com/GCC4.6 Please extend the wiki page if appropriate. To work on the build failures, please use either the gcc-snapshot package from natty or the gcc-4.6 package from the ubuntu-toolchain-r/test PPA. A large number of build failures is seen for packages building with -Werror. The compiler packages above were changed to add a -Wno-error=unused-but-set-variable when -Werror is found. Despite this local change the these packages need to build without this local change. Matthias PS: Fixing build failures with GCC-4.5 in natty should still have priority ;) -- ubuntu-devel-announce mailing list ubuntu-devel-annou...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
re: today's git does not compile
https://bugs.launchpad.net/ubuntu/+source/gcc-4.5/+bug/704633 Bug successfully updated and confirmed by a member of Ubuntu's testing team, so we're off to the races.
today's git does not compile
Could there be a new dependency that isn't summoned by build-dep? Or is it me? I have the latest version of Natty Narwhal gcc (Ubuntu/Linaro 4.5.2-1ubuntu6) 4.5.2 gcc -m32 -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wstrict-prototypes -Wtype-limits -Wwrite-strings -Wpointer-arith -Wlogical-op -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=0 -o pen.o pen.c pen.c: In function ‘X11DRV_SelectPen’: pen.c:31:12: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See file:///usr/share/doc/gcc-4.5/README.Bugs for instructions. make[1]: *** [pen.o] Error 1 make[1]: Leaving directory `/home/susan/wine/dlls/winex11.drv' make: *** [dlls/winex11.drv] Error 2 susan@ubuntu:~/wine$ cd
Re: today's git does not compile
It's not wine's fault, and you're not missing any dependencies; the new version of gcc is probably buggy, and the bug is triggered by something inside wine. If you've compiled Wine before and are re-using object files from an old gcc it's possible that there is a conflict between the object files from before and the object files with your new version of gcc. So, you could try a make clean and then compile again. Erich Hoover ehoo...@mines.edu I tried make distclean and also tried a new wine-git download... so far nothing. On with the flags test.
Re: 64-bit Notepad2 crashes
ELF 7f3aa090b000-7f3aa0c3d000 Export libwine.so.1 if you've compiled wine yourself, it's strange that libwine.so doesn't contain any dwarf information maybe you're loading another instance of libwine? A+ -- Eric Pouech I did a search of the file system. Under /usr/local/lib64 I have libwine.so (link) libwine.so.1 (link) libwine.so.1.0 wine [folder} Under /usr/local/lib64/wine I have libwinecrt0.a libwined3d.def I purged wine yesterday and hand-removed all wine files I could find, including my repository and prefix. And I downloaded yesterday's git. And now I'm getting a different error. wine: error while loading shared libraries: libwine.so.1: cannot open shared object file: No such file or directory This error is for all wine commands, including wine --version I have the same files under /usr/local/lib64 but under user/local/lib64/wine I have lots of so's and def's. ??
Re: 64-bit Notepad2 crashes
On Thu, Dec 30, 2010 at 07:22:31AM -0500, Susan Cragin wrote: ELF 7f3aa090b000-7f3aa0c3d000 Export libwine.so.1 if you've compiled wine yourself, it's strange that libwine.so doesn't contain any dwarf information maybe you're loading another instance of libwine? A+ -- Eric Pouech I did a search of the file system. Under /usr/local/lib64 I have libwine.so (link) libwine.so.1 (link) libwine.so.1.0 wine [folder} Under /usr/local/lib64/wine I have libwinecrt0.a libwined3d.def I purged wine yesterday and hand-removed all wine files I could find, including my repository and prefix. And I downloaded yesterday's git. And now I'm getting a different error. wine: error while loading shared libraries: libwine.so.1: cannot open shared object file: No such file or directory This error is for all wine commands, including wine --version I have the same files under /usr/local/lib64 but under user/local/lib64/wine I have lots of so's and def's. ?? Is /etc/ld.so.conf listing /usr/local/lib64 ? Did you try running ldconfig once? Ciao, Marcus No, it is not listing it. It lists only: include /etc/ld.so.conf.d/*.conf Then I checked ld.so.conf.d, which is a directory containing the following conf files: GL lib32asound2 libasound2 libc x86_64-linux-gnu So, I compared those files to those generated with my 32-bit partition. The last file is replaced by the following: i686-linux-gnu.conf and i-486-linux-gnu.conf Then I ran ldconfig on the 64-bit, and then tried wine notepad. I got the following error: wine: error while loading shared libraries: libwine.so.1: cannot open shared object file: No such file or directory ?Susan
Re: 64-bit Notepad2 crashes
-Original Message- From: James Mckenzie jjmckenzi...@earthlink.net Sent: Dec 30, 2010 10:38 AM To: Susan Cragin susancra...@earthlink.net, Marcus Meissner mar...@jet.franken.de Cc: Wine Developers wine-devel@winehq.org, Eric Pouech eric.pou...@orange.fr Subject: Re: 64-bit Notepad2 crashes Susan Cragin susancra...@earthlink.net wrote: Sent: Dec 30, 2010 8:30 AM To: Marcus Meissner mar...@jet.franken.de Cc: Wine Developers wine-devel@winehq.org, Eric Pouech eric.pou...@orange.fr Subject: Re: 64-bit Notepad2 crashes On Thu, Dec 30, 2010 at 07:22:31AM -0500, Susan Cragin wrote: ELF 7f3aa090b000-7f3aa0c3d000 Export libwine.so.1 if you've compiled wine yourself, it's strange that libwine.so doesn't contain any dwarf information maybe you're loading another instance of libwine? A+ -- Eric Pouech I did a search of the file system. Under /usr/local/lib64 I have libwine.so (link) libwine.so.1 (link) libwine.so.1.0 wine [folder} Then I ran ldconfig on the 64-bit, and then tried wine notepad. I got the following error: wine: error while loading shared libraries: libwine.so.1: cannot open shared object file: No such file or directory Does this 'path' exist in LD_LIBRARY_PATH or equivilent? Otherwise ld might not be able to 'find' it when starting the program. James McKenzie su...@ubuntu:~$ ldd /usr/local/bin/wine linux-gate.so.1 = (0xf77c6000) libwine.so.1 = not found libpthread.so.0 = /lib32/libpthread.so.0 (0xf778c000) libc.so.6 = /lib32/libc.so.6 (0xf762f000) /lib/ld-linux.so.2 (0xf77c7000) Eureka, I think.
Re: 64-bit Notepad2 crashes
On Thu, Dec 30, 2010 at 07:22:31AM -0500, Susan Cragin wrote: ELF7f3aa090b000-7f3aa0c3d000 Export libwine.so.1 if you've compiled wine yourself, it's strange that libwine.so doesn't contain any dwarf information maybe you're loading another instance of libwine? A+ -- Eric Pouech I did a search of the file system. Under /usr/local/lib64 I have libwine.so (link) libwine.so.1 (link) libwine.so.1.0 wine [folder} Then I ran ldconfig on the 64-bit, and then tried wine notepad. I got the following error: wine: error while loading shared libraries: libwine.so.1: cannot open shared object file: No such file or directory Does this 'path' exist in LD_LIBRARY_PATH or equivilent? Otherwise ld might not be able to 'find' it when starting the program. James McKenzie su...@ubuntu:~$ ldd /usr/local/bin/wine linux-gate.so.1 = (0xf77c6000) libwine.so.1 = not found libpthread.so.0 = /lib32/libpthread.so.0 (0xf778c000) libc.so.6 = /lib32/libc.so.6 (0xf762f000) /lib/ld-linux.so.2 (0xf77c7000) Eureka, I think. Just compiled today's git. Could compile but not install. Here's the message. Wine build complete. su...@ubuntu:~/wine$ wine checkinstall wine: error while loading shared libraries: libwine.so.1: cannot open shared object file: No such file or directory
Re: 64-bit Notepad2 crashes
IGNORE MY LAST POST. I'm away from home and don't have my glasses with me. Wine build complete. su...@ubuntu:~/wine$ wine checkinstall wine: error while loading shared libraries: libwine.so.1: cannot open shared object file: No such file or directory
Re: 64-bit Notepad2 crashes
Does this 'path' exist in LD_LIBRARY_PATH or equivilent? Otherwise ld might not be able to 'find' it when starting the program. James McKenzie James... You've just exhausted my technical knowledge. How do I do / find that? Susan: For the BASH shell: Type in set and look for the LD_LIBRARY_PATH line. for the CSH/KSH shell: Type in env Look for the LD_LIBRARY_PATH line. Hopefully, /usr/local/lib is there. BTW, to make Wine work on a Mac, I have to add this line James McKenzie Typed set Did word search on library. Nothing.
Re: 64-bit Notepad2 crashes
On 29 December 2010 04:47, Susan Cragin susancra...@earthlink.net wrote: Stack dump: 0x0022b470: 0x0022b480: 0x0022b490: 0x0022b4a0: 0x0022b4b0: [snip] Backtrace: =0 0x7f3a9dd5cafb PathIsUNCW+0x7b() in shlwapi (0x0022b860) The stack has been blitzed? Or is this local variables (even though PathIsUNCW doesn't have any)? It's hard to know what's going on without a proper stack trace. PathIsUNCW is such a small function, the problem is almost certainly further up the call chain. Well, anybody up for seeing a couple of thousand lines of WINEDEBUG-+all, or should I run relay only? There used to be a place to post log files so people could look at them... but I've forgotten where it is. I was not able to reproduce this here on openSUSE 11.3, using Notepad2-4.1.24-x86-64.zip from http://www.flos-freeware.ch/notepad2.html Is this the one you used? The sourcecode shows it calling PathIsUNCW just with a stackbuffer in src/Dialog.c, which should be safe. Ciao, Marcus That is the one I used. To be clear about what I did, that file on the download site is an installation exe. I opened the compressed file and just used the program's exe and ini files by copying them to my home directory. I have compiled three logs, all, seh relay, and have compressed them, and a copy of the program and ini file I used, and have downloaded all to the following. https://www.yousendit.com/download/RlRxT20zT2JYSHhjR0E9PQ I did not configure any special compiler optimizations. I am running Ubuntu's Natty 64-bit Studio with linux 2.6.37-11-generic.
Re: 64-bit Notepad2 crashes
ELF 7f3aa090b000-7f3aa0c3d000 Export libwine.so.1 if you've compiled wine yourself, it's strange that libwine.so doesn't contain any dwarf information maybe you're loading another instance of libwine? A+ -- Eric Pouech I did a search of the file system. Under /usr/local/lib64 I have libwine.so (link) libwine.so.1 (link) libwine.so.1.0 wine [folder} Under /usr/local/lib64/wine I have libwinecrt0.a libwined3d.def Do you want copies of so.1.0?
64-bit Notepad2 crashes
I just compiled today's git wine-1.3.10-82-g10b1a7e and tried to run Notepad2's 64-bit version. Below is the crash. Wine's Notepad appears to work fine. Can anyone tell if I should file a wine bug or a Notepad2 bug? I'm on Ubuntu Natty. Thanks. $ wine64 Notepad2 fixme:heap:HeapSetInformation 0x2b4000 0 0x22fce0 4 fixme:commdlg:GetFileName95 Flags 0x0200 not yet implemented wine: Unhandled page fault on read access to 0x0026 at address 0x7f3a9dd5cafb (thread 0009), starting debugger... Unhandled exception: page fault on read access to 0x0026 in 64-bit code (0x7f3a9dd5cafb). Register dump: rip:7f3a9dd5cafb rsp:0022b470 rbp:0022b860 eflags:00010202 ( R- -- I - - - ) rax: rbx:0026 rcx:0026 rdx:0026 rsi:0022bd40 rdi: r8:0022afa0 r9:0004 r10: r11:0246 r12:0001 r13:0001 r14: r15: Stack dump: 0x0022b470: 0x0022b480: 0x0022b490: 0x0022b4a0: 0x0022b4b0: 0x0022b4c0: 0x0022b4d0: 0x0022b4e0: 0x0022b4f0: 0x0022b500: 0x0022b510: 0026 0022bd40 0x0022b520: 7f3a9dd5e951 Backtrace: =0 0x7f3a9dd5cafb PathIsUNCW+0x7b() in shlwapi (0x0022b860) 0x7f3a9dd5cafb PathIsUNCW+0x7b in shlwapi: cmpw $5c,(%rbx) Modules: Module Address Debug info Name (83 modules) ELF 7b80-7bbb5000 Deferredkernel32elf \-PE 7b82-7bbb5000 \ kernel32 ELF 7be0-7c103000 Deferredwine-loader PE 14000- 140167000 Deferrednotepad2 ELF 7f3a978cd000-7f3a97ae Deferredmsimg32elf \-PE 7f3a978d-7f3a97ae \ msimg32 ELF 7f3a97ae-7f3a97ce9000 Deferredlibrt.so.1 ELF 7f3a97ce9000-7f3a97eed000 Deferred libgpg-error.so.0 ELF 7f3a97eed000-7f3a98108000 Deferredlibresolv.so.2 ELF 7f3a98108000-7f3a9830b000 Deferredlibkeyutils.so.1 ELF 7f3a9830b000-7f3a9854f000 Deferredlibdbus-1.so.3 ELF 7f3a9854f000-7f3a987c9000 Deferredlibgcrypt.so.11 ELF 7f3a987c9000-7f3a989da000 Deferredlibtasn1.so.3 ELF 7f3a989da000-7f3a98be2000 Deferred libkrb5support.so.0 ELF 7f3a98be2000-7f3a98de6000 Deferredlibcom_err.so.2 ELF 7f3a98de6000-7f3a9900d000 Deferredlibk5crypto.so.3 ELF 7f3a9900d000-7f3a992d1000 Deferredlibkrb5.so.3 ELF 7f3a992d1000-7f3a994e2000 Deferred libavahi-client.so.3 ELF 7f3a994e2000-7f3a996ee000 Deferred libavahi-common.so.3 ELF 7f3a996ee000-7f3a9998f000 Deferredlibgnutls.so.26 ELF 7f3a9998f000-7f3a99bc4000 Deferred libgssapi_krb5.so.2 ELF 7f3a99bc4000-7f3a99e14000 Deferredlibcups.so.2 ELF 7f3a99e76000-7f3a9a0b Deferreduxthemeelf \-PE 7f3a99e8-7f3a9a0b \ uxtheme ELF 7f3a9a0b-7f3a9a2b6000 Deferredlibxfixes.so.3 ELF 7f3a9a2b6000-7f3a9a4c Deferredlibxcursor.so.1 ELF 7f3a9a4c-7f3a9a6c3000 Deferred libxcomposite.so.1 ELF 7f3a9a6c3000-7f3a9a8cc000 Deferredlibxrandr.so.2 ELF 7f3a9a8cc000-7f3a9aad6000 Deferredlibxrender.so.1 ELF 7f3a9aad6000-7f3a9acdc000 Deferredlibxxf86vm.so.1 ELF 7f3a9acdc000-7f3a9aedf000 Deferredlibxinerama.so.1 ELF 7f3a9aedf000-7f3a9b0e5000 Deferredlibxdmcp.so.6 ELF 7f3a9b0e5000-7f3a9b2e8000 Deferredlibxau.so.6 ELF 7f3a9b2e8000-7f3a9b505000 Deferredlibxcb.so.1 ELF 7f3a9b505000-7f3a9b70a000 Deferredlibuuid.so.1 ELF 7f3a9b70a000-7f3a9b925000 Deferredlibice.so.6 ELF 7f3a9b925000-7f3a9bc5c000 Deferredlibx11.so.6 ELF 7f3a9bc5c000-7f3a9be6e000 Deferredlibxext.so.6 ELF 7f3a9be6e000-7f3a9c076000 Deferredlibsm.so.6 ELF
Re: 64-bit Notepad2 crashes
-Original Message- From: Austin Lund austin.l...@gmail.com Sent: Dec 28, 2010 6:14 PM To: Susan Cragin susancra...@earthlink.net Cc: Wine Developers wine-devel@winehq.org Subject: Re: 64-bit Notepad2 crashes On 29 December 2010 04:47, Susan Cragin susancra...@earthlink.net wrote: Stack dump: 0x0022b470: 0x0022b480: 0x0022b490: 0x0022b4a0: 0x0022b4b0: [snip] Backtrace: =0 0x7f3a9dd5cafb PathIsUNCW+0x7b() in shlwapi (0x0022b860) The stack has been blitzed? Or is this local variables (even though PathIsUNCW doesn't have any)? It's hard to know what's going on without a proper stack trace. PathIsUNCW is such a small function, the problem is almost certainly further up the call chain. Well, anybody up for seeing a couple of thousand lines of WINEDEBUG-+all, or should I run relay only? There used to be a place to post log files so people could look at them... but I've forgotten where it is.
64-bit works but Notepad takes a long time to come up, using today's git
I maybe should have filed this as a bug. I know Wine had a regression in 64-bit, and that such regression received a patch. I updated git today and tried it out. Notepad loads, but it loads very slowly. I think it took about 2 minutes. Maybe more. wine-1.3.10-48-g1288078
Re: 64-bit works but Notepad takes a long time to come up, using today's git
On Mon, Dec 27, 2010 at 12:41:37PM -0500, Susan Cragin wrote: I maybe should have filed this as a bug. I know Wine had a regression in 64-bit, and that such regression received a patch. I updated git today and tried it out. Notepad loads, but it loads very slowly. I think it took about 2 minutes. Maybe more. wine-1.3.10-48-g1288078 Was the the first try or the second? wineboot after a new version might take a bit. It takes nearly no time here. Could you bisect to the slow down? Perhaps some printer stuff? Ciao, Marcus I think I've solved what is probably my problem. Notepad when started with the command wine64 runs quickly. Notepad started with wine ran very slowly on one 64-bit partition that I've fiddled with a lot, and not at all on a cleaner 64-bit partition. Sorry for the confusion.
Possible problem with Natty 64-bit compile
I have downloaded the git, compiled and installed wine as 64-bit on the current 64-bit version of Natty. This all works fine, no errors I can see, but then it doesn't run. My executables can be found, including: /usr/local/bin/wine64 and wine64-preloader But I can't run anything. A wine command tells me wine isn't installed, which I guess it isn't, and wine64 gives me a segmentation fault. Do I need a symlink? ubuntu$ wine notepad The program 'wine' can be found in the following packages: * wine-bin-unstable * wine1.2 * wine1.0 Try: sudo apt-get install selected package ubuntu:~$ wine64 notepad Segmentation fault ubuntu:~$
64-bit compilation on Ubuntu-Natty -- build-dep script misses two dependencies
I'm compiling from git onto 64-bit Natty, which is in Alpha. Wine's apt-get build-dep script seems to be missing the following. configure: OpenCL 32-bit development files not found, OpenCL won't be supported. configure: gstreamer-0.10 base plugins 32-bit development files not found, gstreamer support disabled I was able to find gstreamer but did not find any development files for OpenCL in the Ubuntu repository. I did install this: python-pyopencl but still got the warning. I know it's too early to mention this, since Natty's still in Alpha.
Regression? in first-run of Dragon NaturallySpeaking
I haven't been installing Dragon NaturallySpeaking every day for over a week, but I did try it today, and noticed that a bug has apparently crept in. Here's what happens: Installation runs fine. Then I try running the program for the first time. The microphone level test is fine, and the test for microphone accuracy. But then the window that brings up the training dialogue freezes. I imagine it's probably been noticed, but wanted to make sure before I investigated and filed a bug or did a regression test. Susan
Did today's git compile properly?
It's probably me... But I got the following: .1 make[1]: Leaving directory `/home/susan/wine/loader' make[1]: Entering directory `/home/susan/wine/programs' rm -f /usr/local/bin/`dirname programs/msiexec/__installprog__` /usr/bin/install -c wineapploader /usr/local/bin/`dirname programs/msiexec/__installprog__` /usr/bin/install: cannot create regular file `/usr/local/bin/programs/msiexec': No such file or directory make[1]: *** [programs/msiexec/__installprog__] Error 1 make[1]: Leaving directory `/home/susan/wine/programs' make: *** [programs/__install__] Error 2 su...@ubuntu:~/wine$
Git does not build properly after daily pull -- font errors
What's up with the git repository? I do the following: git pull sudo make uninstall ./configure --enable-win64 make distclean ./configure --enable-win64 make depend make and I get the following: warning: System 16: missing glyph for char f8c8 make[1]: *** No rule to make target `marlett.ttf', needed by `all'. Stop. make[1]: Leaving directory `/home/susan/wine/fonts' make: *** [fonts] Error 2 So I delete the git repository and download a new one.
Re: Git does not build properly after daily pull -- font errors
Susan Cragin wrote: ./configure --enable-win64 make distclean ./configure --enable-win64 make depend make Huh? Are you actually trying to build the 64-bit version of Wine? Why would you want to do that? Especially when 64-bit Wine isn't mature yet. Did you try it without --enable-win64? and I get the following: warning: System 16: missing glyph for char f8c8 make[1]: *** No rule to make target `marlett.ttf', needed by `all'. Stop. make[1]: Leaving directory `/home/susan/wine/fonts' make: *** [fonts] Error 2 Check out commit 8350aafd5495c77ad4ba005dc4ae3f61a1ad1147: Author: Alexandre Julliard julli...@winehq.org Date: Thu Feb 4 20:29:23 2010 +0100 fonts: Remove the rules for font symlinks and go back to standard VPATH usage. I'll bet that has something to do with it... So I delete the git repository and download a new one. OK? Then what happened? Did it work, or didn't it? The new git repository worked. I've been doing --enable-win64 because it has worked for me. I've been doing it for a couple of weeks and haven't had a problem. Susan
Re: Today's git has unimplemented function msxml4 leading to stack dump when installing dragon naturallyspeaking
On 2/4/2010 00:08, Susan Cragin wrote: wine-1.1.37-412-g9a92f9c With today's git got a debug, dump, etc., while installing dragon naturallyspeaking. have log wine: Call from 0x7b8364e2 to unimplemented function msxml4.dll.DllRegisterServer, aborting wine: Unimplemented function msxml4.dll.DllRegisterServer called at address 0x7b8364e2 (thread 0027), starting debugger... Susan, please try with current, patch is in. Let me know if you still have a problem with it. Bug has gone BTW -- DNS did install yesterday even with the bug.
Today's git has unimplemented function msxml4 leading to stack dump when installing dragon naturallyspeaking
wine-1.1.37-412-g9a92f9c With today's git got a debug, dump, etc., while installing dragon naturallyspeaking. have log wine: Call from 0x7b8364e2 to unimplemented function msxml4.dll.DllRegisterServer, aborting wine: Unimplemented function msxml4.dll.DllRegisterServer called at address 0x7b8364e2 (thread 0027), starting debugger... - relevant portion below - fixme:reg:GetNativeSystemInfo (0x8b1754) using GetSystemInfo() fixme:msi:msi_unimplemented_action_stub SetODBCFolders - 234 ignored LDirectory table values fixme:msi:msi_unimplemented_action_stub MigrateFeatureStates - 1 ignored LUpgrade table values fixme:msi:msi_unimplemented_action_stub RemoveExistingProducts - 1 ignored LUpgrade table values fixme:msi:msi_unimplemented_action_stub MsiUnpublishAssemblies - 8 ignored LMsiAssembly table values fixme:msi:msi_unimplemented_action_stub SelfUnregModules - 1 ignored LSelfReg table values wine: Call from 0x7b8364e2 to unimplemented function msxml4.dll.DllRegisterServer, aborting wine: Unimplemented function msxml4.dll.DllRegisterServer called at address 0x7b8364e2 (thread 0027), starting debugger... Unhandled exception: unimplemented function msxml4.dll.DllRegisterServer called in 32-bit code (0x7b8364e2). Register dump: CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:003b EIP:7b8364e2 ESP:0033fd24 EBP:0033fd88 EFLAGS:0207( - -- I - -P-C) EAX:7b826105 EBX:7b881ff4 ECX:33b50814 EDX:0033fd44 ESI:8100 EDI:00110429 Stack dump: 0x0033fd24: 0033fda8 0008 003c 8100 0x0033fd34: 0001 7b8364e2 0002 0x0033fd44: 33b50814 33b50831 68311ff4 33b4 0x0033fd54: 0033fd74 0033fd88 7b84e9dd 33b4 0x0033fd64: 0033fd74 0033fd7c 7ffd8c00 0x0033fd74: 00120011 6830ff9d 7b83649a 68311ff4 Backtrace: =0 0x7b8364e2 RaiseException+0x52(code=2147483904, flags=1, nbargs=2, args=0x33fda8) [/home/susan/wine/dlls/kernel32/except.c:84] in kernel32 (0x0033fd88) 1 0x33b507b8 __wine_spec_unimplemented_stub+0x38(module=msxml4.dll, function=DllRegisterServer) [/home/susan/wine/dlls/winecrt0/stub.c:34] in msxml4 (0x0033fdb8) 2 0x33b50588 __wine_stub_DllUnregisterServer() in msxml4 (0x0033fe58) 3 0x6830fe0c __wine_spec_exe_entry+0x7c(peb=0x7ffdf000) [/home/susan/wine/dlls/winecrt0/exe_entry.c:37] in regsvr32 (0x0033fea8) 4 0x7b8586d4 start_process+0x54(peb=register ESI not in topmost frame) [/home/susan/wine/dlls/kernel32/process.c:1026] in kernel32 (0x0033fee8) 5 0x7bc6ed54 call_thread_func+0xc() in ntdll (0x0033fef8) 6 0x7bc6ef20 call_thread_entry_point+0x70(entry=0x7b858680, arg=0x7ffdf000) [/home/susan/wine/dlls/ntdll/signal_i386.c:2426] in ntdll (0x0033ffc8) 7 0x7bc4aefa in ntdll (+0x3aefa) (0x0033ffe8) 0x7b8364e2 RaiseException+0x52 [/home/susan/wine/dlls/kernel32/except.c:84] in kernel32: subl $4,%esp 84 RtlRaiseException( record ); Modules: Module Address Debug info Name (70 modules) ELF 33b3f000-33b53000 Dwarf msxml4elf \-PE 33b4-33b53000 \ msxml4 ELF 6800-6801d000 Deferredld-linux.so.2 ELF 6801d000-68158000 Deferredlibwine.so.1 ELF 68158000-68171000 Deferredlibpthread.so.0 ELF 68171000-682c5000 Deferredlibc.so.6 ELF 682c5000-682c9000 Deferredlibdl.so.2 ELF 682c9000-682d1000 Deferredlibnss_compat.so.2 ELF 682d1000-682e8000 Deferredlibnsl.so.1 ELF 682e8000-682f2000 Deferredlibnss_nis.so.2 ELF 682f2000-682fe000 Deferredlibnss_files.so.2 ELF 682fe000-68313000 Dwarf regsvr32elf \-PE 6830-68313000 \ regsvr32 ELF 68313000-6836b000 Deferredadvapi32elf \-PE 6832-6836b000 \ advapi32 ELF 6836b000-683db000 Deferredrpcrt4elf \-PE 6838-683db000 \ rpcrt4 ELF 683db000-684e8000 Deferreduser32elf \-PE 683f-684e8000 \ user32 ELF 684e8000-68572000 Deferredgdi32elf \-PE 684f-68572000 \ gdi32 ELF 68572000-6861 Deferredkrnl386.exe16.so PE 6858-6861 Deferredkrnl386.exe16 ELF 6861-68625000 Deferredsystem.drv16.so PE 6862-68625000 Deferredsystem.drv16 ELF 68625000-68639000 Deferredcomm.drv16.so PE 6863-68639000 Deferredcomm.drv16 ELF 68639000-68664000 Deferredgdi.exe16.so PE 6864-68664000 Deferredgdi.exe16 ELF 68664000-686da000 Deferredlibfreetype.so.6 ELF 686da000-686ef000 Deferredlibz.so.1 ELF 686ef000-6871f000 Deferredlibfontconfig.so.1 ELF 6871f000-68746000 Deferredlibexpat.so.1 ELF
installation problem with yesterday's git
I'm having an installation problem with yesterday's git. err:msi:ITERATE_Actions Execution halted, action LInstallSpeechAPI returned 1627 err:msi:ITERATE_Actions Execution halted, action LExecuteAction returned 1627 Bug? Regression test? anyone want to see my whole terminal output?
Re: installation problem with yesterday's git - NEVERMIND
Somehow, the 4th time was a charm. Must be me? -Original Message- I'm having an installation problem with yesterday's git. err:msi:ITERATE_Actions Execution halted, action LInstallSpeechAPI returned 1627 err:msi:ITERATE_Actions Execution halted, action LExecuteAction returned 1627 Bug? Regression test? anyone want to see my whole terminal output?
Regression on Tuesday Dec 8
I was installing Dragon NaturallySpeaking on Tuesday with git and noticed that it was very slow to load. In addition, the automatic registration doesn't work as well as it used to. The link to the Scansoft site, to generate the code, does not work. Regression test? Sigh.
msi regression in today's git
Installed Dragon NaturallySpeaking using clean prefix and today's git. Instal went without errors but when I tried to open the program it said that the install hadn't completed correctly. Specifically, iexplore.exe was missing. I looked at the terminal output for the run but there wasn't anything interesting. Susan
Re: msi regression in today's git -- NEVER MIND
I had a bad git. Re-did everything and now it works. Sorry about that. Susan -Original Message- Installed Dragon NaturallySpeaking using clean prefix and today's git. Instal went without errors but when I tried to open the program it said that the install hadn't completed correctly. Specifically, iexplore.exe was missing. I looked at the terminal output for the run but there wasn't anything interesting. Susan
new Lucid gcc compiles wine o
Lucid has fixed the bug I mentioned earlier, and now Wine can be compiled in pre-alpha Lucid Lynx, providing all updates are as-of today, ll/11. In case anyone is interested, the working gcc is: gcc (Ubuntu 4.4.2-1ubuntu4) 4.4.2
Question on using winedbg when program does not crash, just becomes unresponsive
There is some sort of memory leak in Dragon NaturallySpeaking that makes the program become unresponsive (but not crash) after some minutes of using the Dictation Box. I have tried winedbg, SetOnFirstBreak but the program never actually crashes. Without SOFB, of course, winedbg goes for the first unhandled exception, which is harmless. I can't start winedbg right before the program crashes, because I don't know when it will do so. It just sort of wears down. There is nothing I do to make it become unresponsive. Any ideas?
had trouble compiling today
It may be me. I've upgraded to Lucid Lynx. My compile failed. gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wstrict-prototypes -Wwrite-strings -Wtype-limits -Wpointer-arith -g -O2 -o int21.o int21.c int21.c: In function ‘INT21_GetDriveAllocInfo’: int21.c:3556: internal compiler error: in int_cst_value, at tree.c:8305 Please submit a full bug report, with preprocessed source if appropriate. See file:///usr/share/doc/gcc-4.4/README.Bugs for instructions. make[2]: *** [int21.o] Error 1 make[2]: Leaving directory `/home/susan/wine/dlls/winedos' make[1]: *** [winedos] Error 2 make[1]: Leaving directory `/home/susan/wine/dlls' make: *** [dlls] Error 2 su...@ubuntu:~/wine$
Re: had trouble compiling today
Looks like a gcc compiler bug, so you will need to report it there and/or to the Ubuntu bug tracker. Out of interest: a/ did this work when you were running karmic? Yes. Worked always with Karmic. Worked yesterday with Lucid. But downloaded new gcc today, and new git. So it's one or the other. b/ what does gcc --version produce? gcc (Ubuntu 4.4.2-1ubuntu3) 4.4.2 c/ is this an incremental build from a previous build on karmic? Yes. (In fact, it's pre-alpha lucid.) It may well be that there is a new gcc that depends on a new something else that hasn't been released yet. d/ what happens if you clean out all build files (running git clean -fxd in ~/wine will do this if ~/wine is a clone of the wine git repository) and do a build -- does that resolve the issue? Oh, that's a nice command. I'll have to remember that one. Nothing happens. NOTE: You should still report this to gcc/Ubuntu. Noted. Reported. Bug filed. - Reece As I was getting ready to send this I noted another gcc floating by aptitude, so I gave that one a spin. No luck. The problem persists, but I bet the developers know about it.
Have a feeling that the alsa cheese has been moved
After using alsa very happily for several days or weeks, it no longer works for me. Changes I have noticed between the daily builds of 10/1 and 10/13 indicate that Ubuntu is working on alsa, and making changes. In the past, with my program, here's what happened. When sound didn't work, winecfg usually showed wave-in as default. When it did, it showed as dsnoop:0. Well, for a few days daily builds had been hell and sound didn't work at all. Then suddenly with today's daily build sound worked great -- once, with the wave-in showing default. ??? Then the second time I logged in, it showed dsnoop and the message said the sound system wasn't being recognized.
Question -- Did Friday's git cause anyone sound problems on re-boot?
I built and installed Friday's git, installed DNS and ran it without a problem, then re-booted and my sound had vanished. It does not appear to be a problem with my sound modules loading, or a conflict with pulseaudio (which I kill anyway). Alsamixer settings have been adjusted to the proper level. If anyone had a similar experience with Friday's git, and it's not just me, I'll investigate further. However, I suspect it's not a wine problem. Susan
Usual oss choices missing in winecfg, in today's git
Just built today's git, and am running DNS with alsa. (Thanks, Maarten.) Called up winecfg as usual and found there were no options under OSS Driver. No wave-out, no wave-in, no mixer devices. Nada. Peculiar, never saw this before. So I thought I'd call in.
progress of sound update
Yesterday's Ubuntu updates produced a rash of pulseaudio changes, and suddenly alsa works with wine, without stumbling. Today's secret to making it work: In System/Preferences/Startup applications, uncheck pulseaudio sudo apt-get install esound sudo nano /etc/pulse/client.conf autospawn = no Then every time your computer starts, run killall pulseaudio in terminal first. (Because the Startup Applications menu doesn't really work.) I trained and ran pulseaudio without a problem. I also tried oss yesterday, and that seemed to be working again, too. I usually follow the above directions but do not install esound or kill pulseaudio and then run the wine app with padsp. If anyone has any different experiences with today's karmic updates, I would be interested to hear about them. Susan
Re: progress of sound update -- REVISED
Change -- The program I test with is Dragon NaturallySpeaking. Yesterday's Ubuntu updates produced a rash of pulseaudio changes, and suddenly alsa works with wine, without stumbling. Today's secret to making it work: In System/Preferences/Startup applications, uncheck pulseaudio sudo apt-get install esound sudo nano /etc/pulse/client.conf autospawn = no Then every time your computer starts, run killall pulseaudio in terminal first. (Because the Startup Applications menu doesn't really work.) I trained and ran Dragon NaturallySpeaking without a problem. I also tried oss yesterday, and that seemed to be working again, too. I usually follow the above directions but do not install esound or kill pulseaudio and then run the wine app with padsp. If anyone has any different experiences with today's karmic updates, I would be interested to hear about them. Susan
Re: progress of sound update -- REVISED
Yesterday's Ubuntu updates produced a rash of pulseaudio changes, and suddenly alsa works with wine, without stumbling. Today's secret to making it work: In System/Preferences/Startup applications, uncheck pulseaudio sudo apt-get install esound Why do you need to install esound? I don't know. I've taken it for granted that some kind of mixer is needed. Perhaps because I don't use the default sound card, the on-board card. Maybe I don't need esound at all. Or maybe if I could permanently make my Creative X-fi card the default. Right now, to do that, I have to revert back to the alsa-utils from Jaunty and use asoundconf set-default-card. (The newest alsa-utils does not include this handy tool.) sudo nano /etc/pulse/client.conf autospawn = no Then every time your computer starts, run killall pulseaudio in terminal first. (Because the Startup Applications menu doesn't really work.) Painful bug in Ubuntu. Yet another reason why I stay away from it at all costs :) What do you use? I trained and ran Dragon NaturallySpeaking without a problem. Excellent news! Yeah. I read somewhere that Ubuntu has made pulseaudio removable partly because of this very program, which of course is a great assistance to people with mild RSI, who can use a keyboard for some things, but tire easily when entering large amounts of text.
Re: progress of sound update -- REVISED
Why do you need to install esound? ALSA has shipped with dmix by default since shortly after 1.0 was released, though I think Ubuntu's pulse config can screw with it even after pulseaudio is removed. I'd forgotten about dmix, it's been so long. Good old dmix and dsnoop (which is what I need for incoming sound). I THINK MAYBE dmix works and dsnoop does not, because it's listed when I open Audacity. I'll have to give it a try. However, without installing esound, I don't see dmix and dsnoop but I do see default. And default freezes. Perhaps that's them, and they just don't work?
Font can be changed in Dictation Box after today's git
Yippee!! A big step forward for usability. I'll mark the bug fixed tonight.
Re: Latency as of yesterday
Current Ubuntu sound bugs relating to wine OSS 409395. ALSA 407970 -I got this response on the Ubuntu list-- This is probably due to a libasound2-plugins and pulseaudio/rtkit skew; the latest libasound2-plugins needs at least pulseaudio 1:0.9.16~test3 and rtkit 0.3. Karmic has an older version of pulseaudio (1:0.9.15) at the moment. -- After further checking I determined that the current kernel changes are supposed to make the regular kernel capable of running at real-time (right now, for outgoing sound only) by activating a switch on the regular kernel. This functionality, of course, needs pulseaudio. Despite the optimism expressed above, pulseaudio 1:0.9016~test4 and the latest rtkit did not solve my problem. Wine still has no functioning sound. Stay tuned.
Latency as of yesterday
I got a new kernel and a new git yesterday. One of them is causing massive latency in my sound system. I looked at the changes to git that were made yesterday, and suspect that the latency came with the kernel. 2.6.31-5-generic is the new kernel. Just for fun I reinstalled my entire system this morning, and the latency is the same, so it is not due to any tweaks I have made. I have been running using winecfg's oss sound and padsp for a week or so. It had been working fairly well. Anyway, before I file a bug on Ubuntu against the kernel, I thought I would ask if yesterday's git might be at fault. I don't have time to do regression testing before Friday, but I will do it if needed. Susan (Separate issue -- I have not been able to run dragon NaturallySpeaking with alsa for several months. Timeout issues during training.)
Re: Latency as of yesterday
Susan Cragin wrote: I got a new kernel and a new git yesterday. One of them is causing massive latency in my sound system. I looked at the changes to git that were made yesterday, and suspect that the latency came with the kernel. 2.6.31-5-generic is the new kernel. Just for fun I reinstalled my entire system this morning, and the latency is the same, so it is not due to any tweaks I have made. I have been running using winecfg's oss sound and padsp for a week or so. It had been working fairly well. Anyway, before I file a bug on Ubuntu against the kernel, I thought I would ask if yesterday's git might be at fault. I don't have time to do regression testing before Friday, but I will do it if needed. Susan Ubuntu has bugs open for sound issues with the newer kernels. (Separate issue -- I have not been able to run dragon NaturallySpeaking with alsa for several months. Timeout issues during training.) Is there a bug logged for this? Yes and yes. I looked at the bunch of Ubuntu bugs relating to sound with the newest kernel. There was nothing right on point, so I filed on of my own. 409395. The alsa bug is: 407970 Bottom line -- no working sound in wine right now, that I can figure out. At all. In addition, purging pulseaudio has just gotten much more difficult, as of the last couple of days. I tried yesterday. Directions that worked 2 weeks ago now cause desktop to be removed. (I had to re-install system.)
Re: Latency as of yesterday
I got a new kernel and a new git yesterday. One of them is causing massive latency in my sound system. I looked at the changes to git that were made yesterday, and suspect that the latency came with the kernel. 2.6.31-5-generic is the new kernel. Just for fun I reinstalled my entire system this morning, and the latency is the same, so it is not due to any tweaks I have made. I have been running using winecfg's oss sound and padsp for a week or so. It had been working fairly well. Anyway, before I file a bug on Ubuntu against the kernel, I thought I would ask if yesterday's git might be at fault. I don't have time to do regression testing before Friday, but I will do it if needed. Susan Ubuntu has bugs open for sound issues with the newer kernels. (Separate issue -- I have not been able to run dragon NaturallySpeaking with alsa for several months. Timeout issues during training.) Is there a bug logged for this? Yes and yes. I looked at the bunch of Ubuntu bugs relating to sound with the newest kernel. There was nothing right on point, so I filed on of my own. 409395. The alsa bug is: 407970 Bottom line -- no working sound in wine right now, that I can figure out. At all. In addition, purging pulseaudio has just gotten much more difficult, as of the last couple of days. I tried yesterday. Directions that worked 2 weeks ago now cause desktop to be removed. (I had to re-install system.) The problem has been identified. Stay tuned. This is probably due to a libasound2-plugins and pulseaudio/rtkit skew; the latest libasound2-plugins needs at least pulseaudio 1:0.9.16~test3 and rtkit 0.3. Karmic has an older version of pulseaudio (1:0.9.15) at the moment.
gdiplus errors - how to use a workaround
A few months ago I tried compiling wine without all the dependencies that are downloaded with apt-get build-dep wine. I just used a minimum, as wine asked for them. To my surprise, in Dragon NaturallySpeaking the DragonBar came up very crudely sketched, but all the buttons worked. That hasn't happened since. I was wondering if anyone knew which wine dependencies were responsible for this. As a wild guess, I would imagine that it involves compiling without support for the fancy functions of gdiplus. FYI -- using winetricks gdiplus does not work at all. it makes the program crash.
Font problem in Notepad -- regression today
Notepad is behaving very strangely today. It crashes every time I try to change the font. However, when I tried to trace the problem using winedbg, the font changed fine, after the following fixme showed up. Then when I closed the winedbg terminal window, notepad closed too. su...@ubuntu:~$ winedbg Wine-dbginfo process pid threads parent executable (all id:s are in hex) 0008 1 'notepad.exe' 000e 3000a 'services.exe' 0011 4000e 'winedevice.exe' 0018 10008 'explorer.exe' Wine-dbgattach 0x8 0x680007f0 GLIBC_2+0x7f0 in ld-linux.so.2: int $0x80 Wine-dbgset $BreakOnFirstChance=0 Wine-dbgcont fixme:winedbg:be_i386_is_func_call Unsupported yet call insn (0xcd) at 0x680007f0
Re: AppDB test results in Spanish
Who feels like translating some test results? http://appdb.winehq.org/objectManager.php?sClass=versioniId=8714iTestingId=38908 I mean someone actually replace that entry with a translated version. I could do it via Google Translate, but I'd rather someone who *knows* Spanish replace it with a REAL translation :) I read Spanish. Here's my take. I got as far as the load menu and one quick race. In race mode the videos don't work, and other modes also fail. Many things. All this was configured with Windows Vista settings. That can prove anything. No more to say. (Or, that goes without saying.)
re: Removing active maintainers
A basic level of courtesy shouldn't be too hard. Dogfights where two maintainers are asking to have each other thrown out are a good sign that both of said developers need to chill. We need more women. Susan
As of Thursday's git, DNS runs for a bit longer.
I have been timing Dragon NaturallySpeaking to see how fast it crashes. I start when I click on the program, and use it pretty steadily until it crashes. As of yesterday's git, it runs for about 15 minutes and 30 seconds. That's an improvement of two minutes over previous versions. :) Susan
Re: Removing active maintainers
Version 9 should be entirely deleted. That refers to the early 9.0 Preferred release, which is not available any more. 9.0 Preferred has been replaced by 9.5 Preferred, which is garbage like Standard. We should not have people buying DNS 9 Preferred and thinking it is installable when it is not. Versions should not be deleted, especially not for programs sold on actual disks. A user may dig up an old copy somewhere and wonder whether it would work. If the version is deleted, he/she will not know and/or may recreate the page with his results. Gert OK, but Version 9 should be re-numbered to 9.0 Preferred, with a note that version was superseded by 9.5, and new copies purchased will most likely be 9.5.
Re: Removing active maintainers
With regard to Dragon NaturallySpeaking, I have the following comments. Version 5 is still for sale, especially overseas, and is VERY cheap. It's ancient, and of poor quality, but someone still might want to use it. The only test is recent. I'd keep this as is. Version 7 ALL the comments are obsolete and very old. This version was very popular and tested extensively way back when. (Dan Kegel is the admin.) The comments are now only confusing. Version 9.5 Standard is OK. It's rating is garbage because it didn't install. And it still doesn't.Version 9 should be entirely deleted. That refers to the early 9.0 Preferred release, which is not available any more. 9.0 Preferred has been replaced by 9.5 Preferred, which is garbage like Standard. We should not have people buying DNS 9 Preferred and thinking it is installable when it is not. Version 10 and 10 Preferred are OK, even though I should update Standard a bit. (I am the admin.)HTH. Susan
Today's git may have a problem -- install takes forever then crashes
Today's git starts the installation of DNS very-very slowly. Then takes
forever. I thought finally it was going to install but then it crashes at/near
the end.
Tail of log below.
fixme:ole:CoCreateInstance no instance created for interface
{d94a9b75-516c-41ec-8163-f1ac8ab03b29} of class
{fff2d28f-e4ee-44d9-8104-8e71556757f6}, hres is 0xc005
wine: Unhandled page fault on read access to 0x at address 0x412f7d
(thread 007d), starting debugger...
su...@ubuntu:~/DNS$ Unhandled exception: page fault on read access to
0x in 32-bit code (0x00412f7d).
Register dump:
CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:003b
EIP:00412f7d ESP:0033fb00 EBP:0033fe6c EFLAGS:00210212( R- -- I -A- - )
EAX: EBX: ECX: EDX:
ESI:00475908 EDI:0046f754
Stack dump:
0x0033fb00: 001300fc 0004 0044a687
0x0033fb10: 7b8c5ff4 0012fa88 0033fb38 7ffdf000
0x0033fb20: 7e1cfff4 0001 7e1bc63b 7e1cfff4
0x0033fb30: 0001 7e19 0033fb78 7e1b1ff7
0x0033fb40: 0003 7e1d7928 7e1c9207 7e1c7822
0x0033fb50: 7e19 0001
Backtrace:
=0 0x00412f7d in agent (+0x12f7d) (0x0033fe6c)
1 0x0044a767 in agent (+0x4a767) (0x0033fef8)
fixme:dbghelp_dwarf:dwarf2_parse_variable Unsupported form for const value
szNlsKeyName (a)
2 0x7b8778ef start_process+0xdf(arg=(nil))
[/home/susan/wine/dlls/kernel32/process.c:941] in kernel32 (0x0033ffe8)
0x00412f7d: movl0x0(%eax),%ecx
Modules:
Module Address Debug info Name (69 modules)
PE40- 491000 Export agent
ELF 7b80-7b962000 Dwarf kernel32elf
\-PE 7b82-7b962000 \ kernel32
ELF 7bc0-7bcb9000 Deferredntdllelf
\-PE 7bc1-7bcb9000 \ ntdll
ELF 7bf0-7bf04000 Deferredwine-loader
ELF 7e15e000-7e182000 Deferredmprelf
\-PE 7e16-7e182000 \ mpr
ELF 7e182000-7e1d8000 Deferredwininetelf
\-PE 7e19-7e1d8000 \ wininet
ELF 7e226000-7e25a000 Deferreduxthemeelf
\-PE 7e23-7e25a000 \ uxtheme
ELF 7e25a000-7e265000 Deferredlibxcursor.so.1
ELF 7e265000-7e26b000 Deferredlibxfixes.so.3
ELF 7e26b000-7e26f000 Deferredlibxcomposite.so.1
ELF 7e26f000-7e278000 Deferredlibxrandr.so.2
ELF 7e278000-7e282000 Deferredlibxrender.so.1
ELF 7e282000-7e288000 Deferredlibxxf86vm.so.1
ELF 7e288000-7e28b000 Deferredlibxinerama.so.1
ELF 7e28b000-7e2ad000 Deferredimm32elf
\-PE 7e29-7e2ad000 \ imm32
ELF 7e2ad000-7e2b2000 Deferredlibxdmcp.so.6
ELF 7e2b2000-7e2d Deferredlibxcb.so.1
ELF 7e2d-7e2d4000 Deferredlibxau.so.6
ELF 7e2d4000-7e2d9000 Deferredlibuuid.so.1
ELF 7e2d9000-7e409000 Deferredlibx11.so.6
ELF 7e409000-7e419000 Deferredlibxext.so.6
ELF 7e419000-7e434000 Deferredlibice.so.6
ELF 7e434000-7e43d000 Deferredlibsm.so.6
ELF 7e44d000-7e4ef000 Deferredwinex11elf
\-PE 7e46-7e4ef000 \ winex11
ELF 7e51c000-7e543000 Deferredlibexpat.so.1
ELF 7e543000-7e57 Deferredlibfontconfig.so.1
ELF 7e58-7e596000 Deferredlibz.so.1
ELF 7e596000-7e615000 Deferredlibfreetype.so.6
ELF 7e615000-7e629000 Deferredlz32elf
\-PE 7e62-7e629000 \ lz32
ELF 7e629000-7e644000 Deferredversionelf
\-PE 7e63-7e644000 \ version
ELF 7e644000-7e73b000 Deferredoleaut32elf
\-PE 7e66-7e73b000 \ oleaut32
ELF 7e73b000-7e7ad000 Deferredrpcrt4elf
\-PE 7e75-7e7ad000 \ rpcrt4
ELF 7e7ad000-7e8bd000 Deferredole32elf
\-PE 7e7d-7e8bd000 \ ole32
ELF 7e8bd000-7e98b000 Deferredcomctl32elf
\-PE 7e8d-7e98b000 \ comctl32
ELF 7e98b000-7e9ee000 Deferredshlwapielf
\-PE 7e9a-7e9ee000 \ shlwapi
ELF 7e9ee000-7eb83000 Deferredshell32elf
\-PE 7ea0-7eb83000 \ shell32
ELF 7eb83000-7ec2e000 Deferredgdi32elf
\-PE 7eb9-7ec2e000 \ gdi32
ELF 7ec2e000-7ed8a000 Deferreduser32elf
\-PE 7ec5-7ed8a000 \ user32
ELF 7ed8a000-7ee14000 Deferredcrypt32elf
\-PE 7ed9-7ee14000 \ crypt32
ELF 7ee14000-7ee6e000 Deferredadvapi32elf
\-PE 7ee2-7ee6e000 \ advapi32
Re: Implications for Wine from the Ubuntu Developer Summit -- Pulseaudio
2009/6/2 Scott Ritchie sc...@open-vote.org: First, I talked with a Pulseaudio expert about what we can do to make things work better. He said that if we want good compatibility we will need our ALSA stack to use the Pulseaudio safe subset: http://0pointer.de/blog/projects/guide-to-sound-apis.html. I've filed a metabug tracking this here: http://bugs.winehq.org/show_bug.cgi?id=18740. Use of this unsafe subset can cause most problems with stuttering or even complete dropoff. As far as I know, this is not possible for Wine (without massive latency issues caused by overbuffering in Wine itself) due to the fact that Wine has to make DirectSound apps happy. It's also not very consoling from this Pulseaudio expert that they don't seem to see a problem with the ALSA layer on their end - it's the apps that need to be fixed. Wasn't the point of Pulse that you could use libasound/OSS apps without modification? :) I'm not completely familiar with how sound works in Wine, but in the past I remember that one complaint about PulseAudio over ALSA was latency. Latency issues these days are mostly due to bad kernel configurations PulseAudio will *always* have more latency than ALSA. This has nothing to do with kernel configurations, just that using a CONFIG_NO_HZ/CONFIG_HZ_1000 (or whatever it is) kernel from the -rt tree makes the latency issue less severe. New kernel won't fix Wine + Pulse problem. Forgive me in advance for interjecting dross into a technical discussion. Would part of the problem be solved if users could be given the option of installing pulseaudio? That way, some users would be made instantly happy. There is a subset of users (albeit a tiny subset) that just needs one sound application running, but wants that application running with crystal-clear sound and near-zero latency. These are certain professional audio users, and those who run Dragon NaturallySpeaking through wine. Those people may be ill-served by having pulseaudio at all. Right now, in wine, removing pulseaudio completely doesn't seem to return alsa's functionality. Wine/alsa freezes, and I have to use OSS emulation, but OSS just does not produce as high-quality a sound. PS -- The rt kernel really is wonderful for speech recognition or any other use. The repository version has problems that are being worked on. In the meantime, just compile your own.
Re: Sound problems with latest kernel -- formerly a pulseaudio thread but not any more
I filed ubuntu bug 369762. Ubuntu didn't think much of my bug. They sent me the following recipe to cure it, and marked the bug invalid. 1) Edit /etc/pulse/client.conf, and change autospawn = yes to autospawn = no 2) `touch $HOME/.pulse_a11y_nostart' 3) `asoundconf list' 4) choose the desired card from the previous command's output, and use `asoundconf set-default-card CARD', replacing CARD as appropriate 5) `killall pulseaudio' https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/348353 mentions a recent kernel patch that routes all audio through pulse. I wonder if this patch is the culprit?
Re: Sound problems with latest kernel -- formerly a pulseaudio thread but not any more
I have tested the following and I believe found they were not the problem: --snip-- (3) problem with pulseaudio How did you determine this? I thought you said your version of Ubuntu was crippled if pulseaudio was removed, so did you use pasuspender? If so, did you verify there was no pulseaudio process running while you were testing Wine? After I started my testing, I did run into problems when I tried to re-install pulseaudio and then remove it, but the PA problem was unrelated. Ubuntu said there was a PA bug, and issued a fix. After I applied the fix, no more problems working with pulseaudio removed. So the whole thing was sort of a red herring. I have re-installed my entire system since that problem went away, and immediately purged pulseaudio, and that's where I'm working from now. Still same problem. OK, thanks for that clarification. So you've tracked the problem down to kernel version 2.6.29? What version of ALSA drivers are in your working and broken kernels? I've actually tracked it to before that. Wine's audio last worked with one of Ubuntu's generic kernels, probably 2.6.28-10. Ubuntu's current repository kernel is 2.6.28-11. That's the one I that caused the problem. The experimental bug-fix kernel is 2.6.28-12. That does not solve my problem. (Here's where I got the kernel: http://kernel.ubuntu.com/~dtchen/test-kernels/ ) When my kernel worked, my drivers were 0.1.19 -- one of Tashaki Iwai's daily stable builds from a couple of weeks ago. They are 0.1.19 now, today's daily stable build, compiled against 2.6.29-1-rt8-custom, which is what I am running at the moment. My 29-rt kernel is showing the same problems as the two kernels mentioned above. FWIW, the person who compiled the RT kernel said that he did so without applying the Ubuntu patches. So that tells me that the change took place outside the Ubuntu patches. Well, this may be a pulseaudio problem after all. It may not be a wine problem. For the first time this morning, I tried running audacity -- the linux version. (My system has pulseaudio purged.) Audacity behaves the same way under Linux it does under wine, freezing when I stop and re-start the record function. I filed ubuntu bug 369762.
Sound problems with latest kernel -- formerly a pulseaudio thread but not any more
I'm changing the name of the thread. Pulseaudio has nothing to do with my current problem. I thought it did back when I started the thread, but my testing turned out to be incomplete. I still don't know what the problem is, but I believe it has to do with the way wine relates to the current Ubuntu configuration. Using the most current kernel, the most current updates (and using tomorrow's kernels and updates) dmix and dsnoop I believe are not recognized properly by wine because I'm not getting any sound through them. And I did file a bug, but I filed it back when I still thought it was a wine regression, so it's been a long and painful process of discovery. I have tested the following and I believe found they were not the problem: (1) wine regression: (2) problem with my experimental sound drivers; (3) problem with pulseaudio; (4) bizarre problem unique to me -- and for this I reinstalled the system an tested with the base before moving on. When I did the last install, with the current Ubuntu Studio, I got the same result using the downloaded Generic kernel. (Studio can use both Generic and Real-time kernels. Linux-rt didn't work for other reasons. It crashed on bootup.) I was informed that both then-current kernels had problems. So I got the linux-generic with current Ubuntu patches and a successful re-compile of the linux-rt without Ubuntu patches. And I still have exactly the same problem. Here are my current kernels: linux-rt: 2.6.29.1-rt8-custom (It doesn't include Ubuntu's patches.) linux-generic 2.6.28-12 (this is from the Ubuntu site and has Ubuntu's patches) When I run audacity through wine, I get the following input choices: MIME: Wine wave in mapper - Input MIME: dsnoop:Generic MIME: dsnoop:Generic Windows DirectSound: Primary Sound Capture Driver Windows DirectSound: dsnoop:Generic Windows DirectSound: dsnoop:Generic When I use the second option (MME: dsnoop:Generic) it works on the first pass, but when I try to stop and start it again -- no go. The second recording area pops up but it seems to shimmer. The recording meter does not move. And then it freezes. (That is approximately what happens to me training DNS.) When I use the 5th option (Windows DirectSound: dsnoop:generic) it works on the first pass, but when I stop/start it I get the following error message: Error when opening sound device. Please check the input device settings and the project sample rate.
Re: Sound problems with latest kernel -- formerly a pulseaudio thread but not any more
2009/4/29 Susan Cragin susancra...@earthlink.net: I have tested the following and I believe found they were not the problem: --snip-- (3) problem with pulseaudio How did you determine this? I thought you said your version of Ubuntu was crippled if pulseaudio was removed, so did you use pasuspender? If so, did you verify there was no pulseaudio process running while you were testing Wine? After I started my testing, I did run into problems when I tried to re-install pulseaudio and then remove it, but the PA problem was unrelated. Ubuntu said there was a PA bug, and issued a fix. After I applied the fix, no more problems working with pulseaudio removed. So the whole thing was sort of a red herring. I have re-installed my entire system since that problem went away, and immediately purged pulseaudio, and that's where I'm working from now. Still same problem. Susan
Re: Sound problems with latest kernel -- formerly a pulseaudio thread but not any more
I have tested the following and I believe found they were not the problem: --snip-- (3) problem with pulseaudio How did you determine this? I thought you said your version of Ubuntu was crippled if pulseaudio was removed, so did you use pasuspender? If so, did you verify there was no pulseaudio process running while you were testing Wine? After I started my testing, I did run into problems when I tried to re-install pulseaudio and then remove it, but the PA problem was unrelated. Ubuntu said there was a PA bug, and issued a fix. After I applied the fix, no more problems working with pulseaudio removed. So the whole thing was sort of a red herring. I have re-installed my entire system since that problem went away, and immediately purged pulseaudio, and that's where I'm working from now. Still same problem. OK, thanks for that clarification. So you've tracked the problem down to kernel version 2.6.29? What version of ALSA drivers are in your working and broken kernels? I've actually tracked it to before that. Wine's audio last worked with one of Ubuntu's generic kernels, probably 2.6.28-10. Ubuntu's current repository kernel is 2.6.28-11. That's the one I that caused the problem. The experimental bug-fix kernel is 2.6.28-12. That does not solve my problem. (Here's where I got the kernel: http://kernel.ubuntu.com/~dtchen/test-kernels/ ) When my kernel worked, my drivers were 0.1.19 -- one of Tashaki Iwai's daily stable builds from a couple of weeks ago. They are 0.1.19 now, today's daily stable build, compiled against 2.6.29-1-rt8-custom, which is what I am running at the moment. My 29-rt kernel is showing the same problems as the two kernels mentioned above. FWIW, the person who compiled the RT kernel said that he did so without applying the Ubuntu patches. So that tells me that the change took place outside the Ubuntu patches.
Fw: Re: Sound problems with latest kernel -- formerly a pulseaudio thread but not any more
Whoops. This should have gone to the list. Susan Cragin wrote: I have tested the following and I believe found they were not the problem: --snip-- (3) problem with pulseaudio How did you determine this? I thought you said your version of Ubuntu was crippled if pulseaudio was removed, so did you use pasuspender? If so, did you verify there was no pulseaudio process running while you were testing Wine? After I started my testing, I did run into problems when I tried to re-install pulseaudio and then remove it, but the PA problem was unrelated. Ubuntu said there was a PA bug, and issued a fix. After I applied the fix, no more problems working with pulseaudio removed. So the whole thing was sort of a red herring. I have re-installed my entire system since that problem went away, and immediately purged pulseaudio, and that's where I'm working from now. Still same problem. OK, thanks for that clarification. So you've tracked the problem down to kernel version 2.6.29? What version of ALSA drivers are in your working and broken kernels? I've actually tracked it to before that. Wine's audio last worked with one of Ubuntu's generic kernels, probably 2.6.28-10. Ubuntu's current repository kernel is 2.6.28-11. That's the one I that caused the problem. The experimental bug-fix kernel is 2.6.28-12. That does not solve my problem. (Here's where I got the kernel: http://kernel.ubuntu.com/~dtchen/test-kernels/ ) When my kernel worked, my drivers were 0.1.19 -- one of Tashaki Iwai's daily stable builds from a couple of weeks ago. They are 0.1.19 now, today's daily stable build, compiled against 2.6.29-1-rt8-custom, which is what I am running at the moment. My 29-rt kernel is showing the same problems as the two kernels mentioned above. FWIW, the person who compiled the RT kernel said that he did so without applying the Ubuntu patches. So that tells me that the change took place outside the Ubuntu patches. I've had a few users report crashing in steam games as a result of pulseaudio: https://bugs.launchpad.net/bugs/367379 -- do you think this is all related? Thanks, Scott Ritchie Maybe. From the bug, it's hard to tell. But here's what I think. I think that the kernel made changes recently that changed how sound relates to the kernel, and tied pulseaudio closer to the kernel (hence those error messages I got under 2.6.28-11, which kernel was acknowledged to be buggy the day it came out). Some of the bugs they either backed out or corrected with 2.6.28-12. It would be interesting to see if they can get steam running with that kernel. If you are working with the steam-bug people ask them to add the below kernel, purge pulseaudio, and test with alsa only. http://kernel.ubuntu.com/~dtchen/test-kernels/ Of course, they need headers, image restricted modules. Susan
Re: Ubuntu no longer works correctly without pulseaudio
wineoss is not a viable solution to the pulseaudio problem, but this is a real nasty issue where the solution is as long as it works for you, it's fine. What exactly is the issue with purging pulseaudio? Though this should be taken up with ubuntu's bugs tracker. pulseaudio should be considered optional, since ALSA/dmix works wherever pulseaudio with ALSA backend works, even if it is opt-out. Ben, sorry... You probably haven't been following this thread closely. I determined a couple of days ago that pulseaudio was not actually my problem even though I thought it was. I just kept the name of the thread. One of wine's developers asked me if linux's (or Ubuntu's) alsa-wrappers could have changed, and if wine's alsa-wrappers could therefore need updating. The fact that something works under winecfg OSS (but not under winecfg ALSA) is a valuable piece of diagnostic information. My value to this group is usually as a canary in the mine. Because I have the latest kernel, and the latest updates, I am able to spot problems before they hit the mainstream. And remember, this is a developers' group, not a users group. Experimentation is grist for the mill. Susan
Re: Ubuntu no longer works correctly without pulseaudio
Bug 1813 is a really old bug for something else (fixed in 2003). Did you forget a digit? That would be http://bugs.winehq.org/show_bug.cgi?id=18133. - Reece Hi. Yes, that's the bug. Here's everything I know, and probably more than you want to know, but I don't know what to leave out. My system is on the bleeding edge of everything, which can be a problem when it comes time to diagnose. I have been using Ubuntu Jaunty Studio since its first beta, and it's now fairly mature. I compile every wine git and test it, using Dragon NaturallySpeaking. Usually everything works as well or better than it has. In addition to that, I compile my own alsa-driver because I use a Creative SoundBlaster X-fi soundcard. They are a one-time install and I used the stable daily build. They had been working well for weeks, and I had not updated them in at least a day or two. About 10 days ago, when I did my daily wine build and installed DNS, the training froze. My first thought was a wine regression, but I was busy and didn't test for a few days. Then I did a couple of regression tests that seemed to succeed, but really the just marked the first change I tagged as the problem. I tested back further than the problem appeared. Still no luck. Solution? That it's not wine's problem, it is something else that has been introduced. Then I tried using a new alsa-driver, and a new alsa-libs with it. Nothing. Then I tested various configurations of pulseaudio, purged and not-purged. No changes. Then I reinstalled the whole Ubuntu-Studio system. In the meantime, Ubuntu-Studio had switched to using the Real-Time kernel as a default. The kernel froze before wine had a chance to. Back to the drawing board. I downloaded the generic kernel. That seemed to work for USB audio only. I tried compiling alsa-drivers, and installing them, and then USB stopped receiving sound. Then someone on my ubuntu-studio users list compiled a generic (non-ubuntu) realtime kernel. I installed it in the crudest way possible, by double-clicking on the DEB. Success, but for the USB soundcard only. The alsadriver settings that freeze during training are as follows (and they are the ones that used to work): wave-out devices: dmix:Generic (there were three of these) wave-in devices: dsnoop:Generic (ditto) My working mixer device was HD-Audio-Generic. (I had three cards, the other mixers were HDA Intel and iMic USB audio system) Now, to get the program to work at all without freezing, I re-install the kernel. Then only the USB works properly. The settings I see are as follows. wave-out devices: ALC660-VD Analog USB Audio wave-in devices: (same) So, what do you make of all this? Are dmix and dsnoop being bypassed? Susan
Re: Ubuntu no longer works correctly without pulseaudio
http://bugs.winehq.org/show_bug.cgi?id=18133. The alsadriver settings that freeze during training are as follows (and they are the ones that used to work): wave-out devices: dmix:Generic (there were three of these) wave-in devices: dsnoop:Generic (ditto) My working mixer device was HD-Audio-Generic. (I had three cards, the other mixers were HDA Intel and iMic USB audio system) Now, to get the program to work at all without freezing, I re-install the kernel. Then only the USB works properly. The settings I see are as follows. wave-out devices: ALC660-VD Analog USB Audio wave-in devices: (same) Good news. By changing in winecfg alsa to oss, I was able to get USB and my on-board cards (including Creative X-fi) to work, and to work VERY well. No freezing during training. Smooth recognition. And very fast. (My new souped-up real-time kernel may have something to do with that.) I cannot control the volume by the program (I have to use alsamixer). OSS Driver wave out devices / wave in devices / mixer devices all show these three: Realtek ALC660-VD USB Mixer Creative CA0110-IBG
Ubuntu no longer works correctly without pulseaudio
I just thought I would alert the list. I had a problem with sound oddities a few days ago, and filed bug 1813. The possible culprits were wine's daily build, my experimental alsa-driver, and standard Ubuntu updates. The Ubuntu updates won. Ubuntu no longer works correctly with pulseaudio purged. I have to use wine with pasuspender. Susan
Re: Possible regression today's git wine-1.1.19-153-g55ad3fd
Ohhh... got a nice crash after a re-boot. Never mind that. This looks more promising. At least, to me it does. The actctx error I get all the time, but I've never seen the other, and it happend right as the system froze up. fixme:actctx:parse_depend_manifests Could not find dependent assembly LMicrosoft.VC80.MFCLOC (8.0.50608.0) err:wave:wodPlayer_WriteMaxFrags Error in writing wavehdr. Reason: Broken pipe err:wave:wodPlayer_WriteMaxFrags Error in writing wavehdr. Reason: Broken pipe err:wave:wodPlayer_WriteMaxFrags Error in writing wavehdr. Reason: Broken pipe err:wave:wodPlayer_WriteMaxFrags Error in writing wavehdr. Reason: Success Interesting. You are running Ubuntu studio 8.10 without pulseaudio, right? Have you updated the system between version runs (that may have reintroduced pulseaudio, for example)? Are you running any other sound applications (or the sound that is played after boot on Ubuntu)? Could you perform a git bisect to identify the guilty change? Doing some investigation, I have found (http://alsa.opensrc.org/index.php/HowTo_Asynchronous_Playback): That is basically all there is to the callback. Note however, that this example does not include error checking, which is a good idea of course. Occasionally, you may have to restore from a buffer under-run, in case the computer was caught up in some other process and didn't get to calling your callback. Whenever this happens, the first operation you perform on the device, in this case snd_pcm_avail_update, will return -EPIPE (a 'Broken Pipe' error). You can restore from this by calling the snd_pcm_prepare function again. This may be what you are experiencing here. I'd need to look into this further, but to be honest, I'm a little out of depth with the Windows and Wine sound interfaces. - Reece Reece: I purged pulseaudio and checked that it had not been re-installed. I run Ubuntu 9.04 with all updates. I also use a test version of alsa-driver since my sound card is difficult to recognize but so far have had only great results -- no impact on wine at all. The problem I am experiencing manifests itself in the program freezing... could be the sound, could also be the buttons doing something odd. One button's on-off toggle switches suddenly with no input on my part. Regression test is below. Susan b958dfdc4769515c0ef56c401430dd3e3980aabf is first bad commit commit b958dfdc4769515c0ef56c401430dd3e3980aabf Author: Huw Davies h...@codeweavers.com Date: Thu Apr 16 11:51:45 2009 +0100 ole32: Change helper function to return the matching entry. :04 04 2964979dee4f353e1d565f7c20d8fdcc534f006d 8744cfee2e33db4799f58f102825103f565e18b9 M dlls I filed bug #18133, which has more detail and a screenshot. Susan
Possible regression today's git wine-1.1.19-153-g55ad3fd
Dragon NaturallySpeaking freezes up today during training, without crashing. I will do a regression test if needed, but suspect that the freeze may be already known and/or affect many programs. The terminal output was singularly unhelpful. After deleting all the lines that I see every time often enough to have memorized them, I come up with the following, but none of it happened at the point of crash. Susan err:ole:local_server_thread ConnectNamedPipe failed with error 231 fixme:wininet:set_cookie Unknown additional option Lexpires = Thu, 01-Jan-2099 00:00:00 GMT fixme:winstation:GetUserObjectInformationW not supported index 4 err:ntdll:NtQueryInformationToken Unhandled Token Information class 12! fixme:mstask:MSTASK_ITaskScheduler_Enum 0x15bd40, 0x32f088: stub fixme:mstask:MSTASK_ITask_GetExitCode (0x155c18, 0x32f124): stub fixme:mstask:MSTASK_ITaskScheduler_Enum 0x15bd40, 0x32f088: stub fixme:mstask:MSTASK_ITask_GetExitCode (0x155c18, 0x32f124): stub fixme:mstask:MSTASK_ITaskScheduler_Enum 0x15bd40, 0x32f088: stub fixme:mstask:MSTASK_ITask_GetExitCode (0x155c18, 0x32f124): stub fixme:gdiplus:GdipSetLinePresetBlend not implemented fixme:keyboard:UnregisterHotKey (0x1008c,1): stub fixme:keyboard:RegisterHotKey (0x1008c,1,0x,106): stub
Re: Possible regression today's git wine-1.1.19-153-g55ad3fd
Dragon NaturallySpeaking freezes up today during training, without crashing. I will do a regression test if needed, but suspect that the freeze may be already known and/or affect many programs. Susan Ohhh... got a nice crash after a re-boot. fixme:gdiplus:GdipCreateHBITMAPFromBitmap stub fixme:actctx:parse_depend_manifests Could not find dependent assembly LMicrosoft.VC80.MFCLOC (8.0.50608.0) err:ole:CoRevokeClassObject called from wrong apartment, should be called from 8002c err:ole:CoRevokeClassObject called from wrong apartment, should be called from 8002c err:ole:CoRevokeClassObject called from wrong apartment, should be called from 8002c err:ole:CoRevokeClassObject called from wrong apartment, should be called from 8002c err:ole:CoRevokeClassObject called from wrong apartment, should be called from 8002c err:ole:CoRevokeClassObject called from wrong apartment, should be called from 8002c err:ole:CoRevokeClassObject called from wrong apartment, should be called from 8002c err:ole:CoRevokeClassObject called from wrong apartment, should be called from 8002c err:ole:CoRevokeClassObject called from wrong apartment, should be called from 8002c err:ntdll:RtlpWaitForCriticalSection section 0x7bc9c624 loader.c: loader_section wait timed out in thread 0040, blocked by 0042, retrying (60 sec) su...@ubuntu:~/.wine/drive_c/Program Files/Nuance/NaturallySpeaking10/Program$
Re: Possible regression today's git wine-1.1.19-153-g55ad3fd
Ohhh... got a nice crash after a re-boot. Never mind that. This looks more promising. At least, to me it does. The actctx error I get all the time, but I've never seen the other, and it happend right as the system froze up. fixme:actctx:parse_depend_manifests Could not find dependent assembly LMicrosoft.VC80.MFCLOC (8.0.50608.0) err:wave:wodPlayer_WriteMaxFrags Error in writing wavehdr. Reason: Broken pipe err:wave:wodPlayer_WriteMaxFrags Error in writing wavehdr. Reason: Broken pipe err:wave:wodPlayer_WriteMaxFrags Error in writing wavehdr. Reason: Broken pipe err:wave:wodPlayer_WriteMaxFrags Error in writing wavehdr. Reason: Success
Re: Possible regression today's git wine-1.1.19-153-g55ad3fd
2009/4/20 Reece Dunn mscl...@googlemail.com: 2009/4/20 Susan Cragin susancra...@earthlink.net: Ohhh... got a nice crash after a re-boot. Never mind that. This looks more promising. At least, to me it does. The actctx error I get all the time, but I've never seen the other, and it happend right as the system froze up. fixme:actctx:parse_depend_manifests Could not find dependent assembly LMicrosoft.VC80.MFCLOC (8.0.50608.0) err:wave:wodPlayer_WriteMaxFrags Error in writing wavehdr. Reason: Broken pipe err:wave:wodPlayer_WriteMaxFrags Error in writing wavehdr. Reason: Broken pipe err:wave:wodPlayer_WriteMaxFrags Error in writing wavehdr. Reason: Broken pipe err:wave:wodPlayer_WriteMaxFrags Error in writing wavehdr. Reason: Success Interesting. You are running Ubuntu studio 8.10 without pulseaudio, right? Have you updated the system between version runs (that may have reintroduced pulseaudio, for example)? Are you running any other sound applications (or the sound that is played after boot on Ubuntu)? Could you perform a git bisect to identify the guilty change? Doing some investigation, I have found (http://alsa.opensrc.org/index.php/HowTo_Asynchronous_Playback): That is basically all there is to the callback. Note however, that this example does not include error checking, which is a good idea of course. Occasionally, you may have to restore from a buffer under-run, in case the computer was caught up in some other process and didn't get to calling your callback. Whenever this happens, the first operation you perform on the device, in this case snd_pcm_avail_update, will return -EPIPE (a 'Broken Pipe' error). You can restore from this by calling the snd_pcm_prepare function again. This may be what you are experiencing here. I'd need to look into this further, but to be honest, I'm a little out of depth with the Windows and Wine sound interfaces. - Reece Reece: I purged pulseaudio and checked that it had not been re-installed. I run Ubuntu 9.04 with all updates. I also use a test version of alsa-driver since my sound card is difficult to recognize but so far have had only great results -- no impact on wine at all. The problem I am experiencing manifests itself in the program freezing... could be the sound, could also be the buttons doing something odd. One button's on-off toggle switches suddenly with no input on my part. Regression test is below. Susan b958dfdc4769515c0ef56c401430dd3e3980aabf is first bad commit commit b958dfdc4769515c0ef56c401430dd3e3980aabf Author: Huw Davies h...@codeweavers.com Date: Thu Apr 16 11:51:45 2009 +0100 ole32: Change helper function to return the matching entry. :04 04 2964979dee4f353e1d565f7c20d8fdcc534f006d 8744cfee2e33db4799f58f102825103f565e18b9 M dlls
Re: Article on wine development strategy
I would like to put in my two cents for making Dragon NaturallySpeaking 10 work at about 50%. DNS 10 is a terrible program in a lot of ways. It's interface is over-engineered, clumsy, unintuitive, and packed with features that the average user never even looks at. People who don't know DNS say, I'd love to dictate into word, format by voice command, etc. People who know DNS well, say just give me accuracy and speed, and forget everything else. Those people usually tend to be the natural DNS constituency: either disabled or want to churn out a tremendous amount of text without typing. I think my point here is that happiness depends not only on % but on the type of program. Not all programs are created equal. Not all features are a good idea. Susan Cragin
Re: FYI -- Dragon Naturally Speaking running a bit better today.
On Do, 2009-04-09 at 16:05 -0400, Susan Cragin wrote: Dragon Naturally Speaking ... the amount of time one can use it before it crashes crept up about 2 minutes, ... Today I dictated for about 14 minutes until it crashed. That's progress. Susan, thanks a lot for your sedulous testing of DNS in Wine! -- By by ... Detlef Thank you all for making my program run better. 16 minutes with today's git, 14-Apr. Susan
FYI -- Dragon Naturally Speaking running a bit better today.
Dragon Naturally Speaking crashes after prolonged use, but the amount of time one can use it before it crashes crept up about 2 minutes, using today's git. Today I dictated for about 14 minutes until it crashed. That's progress. Susan
Re: Firefox 3 runs faster on Linux+Wine than on Linux -- comparative to running on Windows
Hi, For those not monitoring slashdot [1], there is an article [2] that is comparing the Google V8 benchmark on Windows and Linux versions of Firefox 3. The result of this is that the Windows and Wine runs are pretty close (241 vs 227) when compared to the Linux run (181) and Opera (155). I wonder what the results are like on Firefox 3.1 with tracemonkey enabled on Windows, Wine and Linux. [1] http://tech.slashdot.org/article.pl?sid=09/02/13/0058251 [2] http://www.tuxradar.com/content/browser-benchmarks-2-even-wine-beats-linux-firefox - Reece One thing that interested me... one person wrote that Linux/Firefox compiled with msvc was faster than gcc, because msvc is better at optimization. Has anyone tried compiling wine with msvc? Susan
Today's git installation error...
When I installed DNS10 today, the included Visual C++ 8.0 runtime does not
load, with the following message.
fixme:advapi:LookupAccountNameW (null) Lsusan (nil) 0x33f80c (nil) 0x33f810
0x33f804 - stub
fixme:advapi:LookupAccountNameW (null) Lsusan 0x131958 0x33f80c 0x132430
0x33f810 0x33f804 - stub
ALSA lib pcm_dmix.c:1008:(snd_pcm_dmix_open) unable to open slave
fixme:reg:GetNativeSystemInfo (0x7e1487b4) using GetSystemInfo()
wine: Unhandled page fault on write access to 0x7de61520 at address 0x7de61520
(thread 0020), starting debugger...
p\{EB7D44B1-C2F5-4B7B-9128-CE4C3D427024}\Visual C++ Runtime for Dragon
NaturallySpeaking.msi: server.c:594: server_get_unix_fd: Assertion
`wine_server_ptr_handle(fd_handle) == handle' failed.
err:seh:raise_exception Exception frame is not in stack limits = unable to
dispatch exception.
Then I try again, and it does load, and the program installs and runs.
??
I imagine other people have reported this. No need to respond.
DNS10 goes 12 minutes rather than 10 before crashing.
As you may know, Dragon NaturallySpeaking 10 crashes on use with predictable regularity. Used to be every 10 minutes. However, yesterday (and today) that creeped up to 12 minutes. It could be due to anything, but I thought one of you might say EUREKA!! it's the foobar.c part of oleacc!! or something like that. If not, have a good day. Susan
Re: DNS10 goes 12 minutes rather than 10 before crashing.
As you may know, Dragon NaturallySpeaking 10 crashes on use with predictable regularity. Used to be every 10 minutes. However, yesterday (and today) that creeped up to 12 minutes. It could be due to anything, but I thought one of you might say EUREKA!! it's the foobar.c part of oleacc!! or something like that. If not, have a good day. Susan Hi Susan, Is there a demo for DNS 10 and do you need to do anything special for it to crash? I presume you need to train it and then start speaking. - Reece Hi, Reece. There is no demo. DNS10 Standard costs $100. I have been somewhat successful in getting complimentary copies for developers. I'm meeting with one of the senior developers the second Tuesday in Feb. If you want a copy, send me something about you or a link to something about you, and a street address for mailing. What I do: Every day, I compile git and re-install DNS on a new .wine. Then I train it and run it. I use it in my work, which is writing. DNS10 used to be sort of flaky but it's getting better. Right now sometimes it crashes immediately on first run but then it runs GREAT -- fast and accurate -- for 10 minutes (now 12). Then it crashes. Always. Inevitably. It's always the time factor. Always just about the same amount of seconds between the time the recognition engine initializes and when it crashes. I can be dictating like a maniac -- hundreds of words per minute, or I can dictate nothing at all. I can transfer text every 10 seconds or leave it all in DictationBox. I can change the settings to save trained text or not. Nothing makes any difference other than time. BTW -- I always dictate into DictationBox, for transfer into Notepad. That is the way (under ALL configurations including Windows) that the program runs the best. Susan
Re: Support for Dragon NS in Wine
<sdru...@gmail.com><susancra...@earthlink.net><d...@kegel.com><jeffzaro...@gmail.com>Thanks to all of you. This is very helpful information. Susan, I appreciate your willingness to run more tests. I'm particularly interested in being able to run NS on CrossOver Mac by Codeweavers. I am planning on switching from a PC to a Mac, and for several reasons, I don't want to have to install the Windows operating system and use Boot Camp or Fusion. I already own NS 8 Professional and am hoping it can function on the Mac and be used on Office applications designed for the Mac (and on Mac applications, too). I don't need most of the features that go beyond the Preferred version, so if I stick to those features available on Preferred, would I get good functionality? Of course, if I could also use the feature that records and saves a transcript of specific dictations (not available on Preferred), it would be especially nice. Any possibility of your testing that out? I was hoping I could upgrade to the new version 10 and use it on the Mac, but it seems that would not be a good idea at this time. I'll be grateful for whatever further assistance you can provide. Steve D. On Tue, Jan 20, 2009 at 5:44 PM, Susan Cragin susancra...@earthlink.net wrote: On Tue, Jan 20, 2009 at 3:23 PM, Jeff Zaroyko jeffzaro...@gmail.com wrote: While I don't own any NS product, two open bugs to come to mind for NS 8, one affecting the installer but with a workaround, bug 15708 and the other a user has reported a regression bug 16248 but was not interested in running a regression test. http://bugs.winehq.org/show_bug.cgi?id=15708 http://bugs.winehq.org/show_bug.cgi?id=16248 I think those were both for NS 7, not 8... A full list of NS bugs is at http://bugs.winehq.org/buglist.cgi?quicksearch=Dragon+Naturally+Speaking Looks like 9 is happier than 10...? I have 7, 8, 9, 9.5 and 10 here. I'll test a couple tonight, maybe 7 and 8, on today's git. Here's what I remember. 7 worked great right out of the box at one time, with all-native code. 8 is virtually the same product as 7. Ditto worked great. (Nobody bought 8 much because it was the same engine as 7.) 9.0 worked pretty good out of the box with a couple of glitches. 9.5 does not install, and works not at all, except for one lucky man who developed a workaround that doesn't always work. (9.5 replaced 9.0 as "version 9," and 9.0 is no longer sold, at least in the US.) 10.0 installs well and runs pretty well for 10 minutes, then nasty crashes happen. Wine support has been given primarily for the two cheapest "consumer" versions, Standard and Preferred. Very few people have asked about Professional, and I don't know of anyone who has tried to make Professional 8 run with wine. Susan Well, I tested 7 and 8 last night with a current git. For 7, bug 15708 is still active. I was unable to do the workaround. 8 installs and trains without a problem but then does not run. I filed a bug report. bug 17057. I will do a little more work on this and keep you updated. Susan
Today's git does not compile
At least, it doesn't for me... O2 -o wowthunk.o wowthunk.c ../../tools/winebuild/winebuild -D_REENTRANT -fPIC --as-cmd as -o relay16asm.o --relay16 ../../tools/wmc/wmc -i -U -H /dev/null -o nls/winerr_deu.mc.rc nls/winerr_deu.mc ../../tools/wmc/wmc -i -U -H /dev/null -o nls/winerr_enu.mc.rc nls/winerr_enu.mc ../../tools/wmc/wmc -i -U -H /dev/null -o nls/winerr_fra.mc.rc nls/winerr_fra.mc ../../tools/wmc/wmc -i -U -H /dev/null -o nls/winerr_kor.mc.rc nls/winerr_kor.mc ../../tools/wmc/wmc -i -U -H /dev/null -o nls/winerr_nor.mc.rc nls/winerr_nor.mc ../../tools/wrc/wrc --nostdinc -I. -I. -I../../include -I../../include -D__WINESRC__ -D_KERNEL32_ -fokernel.res kernel.rc Source: �̤� a2 cc a4 eb Unicode: 5341 6708 Back: �Q�� a4 51 a4 eb nls/cht.nls:84:16: Error: String �̤� does not convert identically to Unicode and back in codepage 950. Try using a Unicode string instead make[2]: *** [kernel.res] Error 1 make[2]: Leaving directory `/home/susan/wine/dlls/kernel32' make[1]: *** [kernel32] Error 2 make[1]: Leaving directory `/home/susan/wine/dlls' make: *** [dlls] Error 2 su...@ubuntu:~/wine$
Re: Support for Dragon NS in Wine
On Tue, Jan 20, 2009 at 3:23 PM, Jeff Zaroyko jeffzaro...@gmail.com wrote: While I don't own any NS product, two open bugs to come to mind for NS 8, one affecting the installer but with a workaround, bug 15708 and the other a user has reported a regression bug 16248 but was not interested in running a regression test. http://bugs.winehq.org/show_bug.cgi?id=15708 http://bugs.winehq.org/show_bug.cgi?id=16248 I think those were both for NS 7, not 8... A full list of NS bugs is at http://bugs.winehq.org/buglist.cgi?quicksearch=Dragon+Naturally+Speaking Looks like 9 is happier than 10...? I have 7, 8, 9, 9.5 and 10 here. I'll test a couple tonight, maybe 7 and 8, on today's git. Here's what I remember. 7 worked great right out of the box at one time, with all-native code. 8 is virtually the same product as 7. Ditto worked great. (Nobody bought 8 much because it was the same engine as 7.) 9.0 worked pretty good out of the box with a couple of glitches. 9.5 does not install, and works not at all, except for one lucky man who developed a workaround that doesn't always work. (9.5 replaced 9.0 as version 9, and 9.0 is no longer sold, at least in the US.) 10.0 installs well and runs pretty well for 10 minutes, then nasty crashes happen. Wine support has been given primarily for the two cheapest consumer versions, Standard and Preferred. Very few people have asked about Professional, and I don't know of anyone who has tried to make Professional 8 run with wine. Susan
Trouble compiling today's git.
Is anyone else having trouble compiling today's git? Or is it just my flu-addled brain? make[1]: Entering directory `/home/susan/wine/server' ../tools/makedep -C. -S.. -T.. async.c atom.c change.c class.c clipboard.c completion.c console.c context_alpha.c context_i386.c context_powerpc.c context_sparc.c context_x86_64.c debugger.c device.c directory.c event.c fd.c file.c handle.c hook.c mach.c mailslot.c main.c mapping.c mutex.c named_pipe.c object.c process.c procfs.c ptrace.c queue.c region.c registry.c request.c semaphore.c serial.c signal.c snapshot.c sock.c symlink.c thread.c timer.c token.c trace.c unicode.c user.c window.c winstation.c make[1]: Leaving directory `/home/susan/wine/server' make[1]: Entering directory `/home/susan/wine/server' ../tools/makedep -C. -S.. -T.. async.c atom.c change.c class.c clipboard.c completion.c console.c context_alpha.c context_i386.c context_powerpc.c context_sparc.c context_x86_64.c debugger.c device.c directory.c event.c fd.c file.c handle.c hook.c mach.c mailslot.c main.c mapping.c mutex.c named_pipe.c object.c process.c procfs.c ptrace.c queue.c region.c registry.c request.c semaphore.c serial.c signal.c snapshot.c sock.c symlink.c thread.c timer.c token.c trace.c unicode.c user.c window.c winstation.c make[1]: Leaving directory `/home/susan/wine/server' make[1]: Entering directory `/home/susan/wine/tools' make[2]: Entering directory `/home/susan/wine/tools/widl' ../../tools/makedep -C. -S../.. -T../.. client.c expr.c hash.c header.c proxy.c server.c typegen.c typelib.c utils.c widl.c write_msft.c parser.y parser.l make[2]: Leaving directory `/home/susan/wine/tools/widl' make[2]: Entering directory `/home/susan/wine/tools/widl' ../../tools/makedep -C. -S../.. -T../.. client.c expr.c hash.c header.c proxy.c server.c typegen.c typelib.c utils.c widl.c write_msft.c parser.y parser.l make[2]: Leaving directory `/home/susan/wine/tools/widl' make[2]: Entering directory `/home/susan/wine/tools/winebuild' ../../tools/makedep -C. -S../.. -T../.. import.c main.c parser.c relay.c res16.c res32.c spec16.c spec32.c utils.c make[2]: Leaving directory `/home/susan/wine/tools/winebuild' make[2]: Entering directory `/home/susan/wine/tools/winebuild' ../../tools/makedep -C. -S../.. -T../.. import.c main.c parser.c relay.c res16.c res32.c spec16.c spec32.c utils.c make[2]: Leaving directory `/home/susan/wine/tools/winebuild' make[2]: Entering directory `/home/susan/wine/tools/winedump' ../../tools/makedep -C. -S../.. -T../.. debug.c dos.c dump.c emf.c le.c lib.c lnk.c main.c minidump.c misc.c msc.c msmangle.c ne.c output.c pdb.c pe.c search.c symbol.c make[2]: Leaving directory `/home/susan/wine/tools/winedump' make[2]: Entering directory `/home/susan/wine/tools/winedump' ../../tools/makedep -C. -S../.. -T../.. debug.c dos.c dump.c emf.c le.c lib.c lnk.c main.c minidump.c misc.c msc.c msmangle.c ne.c output.c pdb.c pe.c search.c symbol.c make[2]: Leaving directory `/home/susan/wine/tools/winedump' make[2]: Entering directory `/home/susan/wine/tools/winegcc' ../../tools/makedep -C. -S../.. -T../.. utils.c winegcc.c make[2]: Leaving directory `/home/susan/wine/tools/winegcc' make[2]: Entering directory `/home/susan/wine/tools/winegcc' ../../tools/makedep -C. -S../.. -T../.. utils.c winegcc.c make[2]: Leaving directory `/home/susan/wine/tools/winegcc' make[2]: Entering directory `/home/susan/wine/tools/wmc' ../../tools/makedep -C. -S../.. -T../.. lang.c mcl.c utils.c wmc.c write.c mcy.y make[2]: Leaving directory `/home/susan/wine/tools/wmc' make[2]: Entering directory `/home/susan/wine/tools/wmc' ../../tools/makedep -C. -S../.. -T../.. lang.c mcl.c utils.c wmc.c write.c mcy.y make[2]: Leaving directory `/home/susan/wine/tools/wmc' make[2]: Entering directory `/home/susan/wine/tools/wrc' ../../tools/makedep -C. -S../.. -T../.. dumpres.c genres.c newstruc.c readres.c translation.c utils.c wrc.c writeres.cparser.y parser.l make[2]: Leaving directory `/home/susan/wine/tools/wrc' make[2]: Entering directory `/home/susan/wine/tools/wrc' ../../tools/makedep -C. -S../.. -T../.. dumpres.c genres.c newstruc.c readres.c translation.c utils.c wrc.c writeres.cparser.y parser.l make[2]: Leaving directory `/home/susan/wine/tools/wrc' ../tools/makedep -C. -S.. -T.. -I/usr/include/freetype2 fnt2bdf.c fnt2fon.c make_ctests.c makedep.c relpath.c sfnt2fnt.c make[1]: Leaving directory `/home/susan/wine/tools' ./tools/makedep -C. -S. -T. make[1]: Entering directory `/home/susan/wine/tools' make[1]: `makedep' is up to date. make[1]: Leaving directory `/home/susan/wine/tools' make[1]: Entering directory `/home/susan/wine/libs' make[2]: Entering directory `/home/susan/wine/libs/port'
Re: today's git does not compile with yesterday's new gcc -- regression test results
I did the regression test. But how legitimate are the results if the problem is the new gcc that I downloaded recently, and not wine? This problem was an Ubuntu linux bug, and has been fixed in headers for kernel 2.6.28-2.2. See Ubuntu bug 303711. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/303711
Re: Did anyone have any trouble compiling wine today? Or was it just me ....
I don't know off hand then. I'd say run a regression test. As a guess, you might try removing: #ifdef HAVE_LINUX_SERIAL_H #include linux/serial.h #endif but that would just be a kludgy workaround. -- -Austin Will try both tomorrow. Thanks. Austin: Did not see above section, but did see this, so removed it. #ifdef HAVE_LINUX_INPUT_H #include linux/input.h #endif Did not work. Got same error. :(
Re: Did anyone have any trouble compiling wine today? Or was it just me ....
On Mon, Dec 1, 2008 at 9:06 AM, Susan Cragin [EMAIL PROTECTED] wrote: I don't know off hand then. I'd say run a regression test. As a guess, you might try removing: #ifdef HAVE_LINUX_SERIAL_H #include linux/serial.h #endif but that would just be a kludgy workaround. -- -Austin Will try both tomorrow. Thanks. Austin: Did not see above section, but did see this, so removed it. #ifdef HAVE_LINUX_INPUT_H #include linux/input.h #endif Did not work. Got same error. :( Regression test? As Detleft said, it may be kernel related. -- -Austin Found something similar to what Detlef found, so filed a Ubuntu bug against the kernel. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/303711 Also tried new kernel, 2.6.28-1-ub, but got same result. Susan
Help need list of wine git versions
Need the number of the current git because am doing regression on it, because it doesn't compile on my machine using my gcc. gcc (Ubuntu 4.3.2-2ubuntu5) 4.3.3 20081129 (prerelease) (And BTW can the regression test page link to this page?) Thank you very much. Susan
today's git does not compile with yesterday's new gcc -- regression test results
I did the regression test. But how legitimate are the results if the problem is the new gcc that I downloaded recently, and not wine? gcc (Ubuntu 4.3.2-2ubuntu5) 4.3.3 20081129 (prerelease) [EMAIL PROTECTED]:~/wine$ git bisect bad Bisecting: 0 revisions left to test after this [0b7478a79fb0594daba5cee3c024c352ad39] widl: Make sure format strings for structure and union types are only output once. Susan
