http://bugs.winehq.com/show_bug.cgi?id=1124
------- Additional Comments From z_god@wanadoo.nl 2003-28-06 07:46 ------- Bug comments restored from Gmane.org:
I'm running Wine 20021007 on a Suse-8.0 machine, and want to startup Bryce-4.0 (which installed properly inclusive Quicktime and Acroreader) but which fails with:
fixme:ddraw:Main_DirectDraw_SetCooperativeLevel (0x426bc1d8)->(00000000,00000008) fixme:win:OpenDesktopA ("screen-saver",1,0,40): stub fixme:msvcrt:_XcptFilter (-2147483392,0x406d1f7c)semi-stub wine: Unhandled exception, starting debugger... err:seh:start_debugger Couldn't start debugger ("debugger/winedbg 134679808 512") (2)
What's there going wrong? Is it maybe only the missed screen saver? But when, how getting one for a pure wine installation, so wine without some Windows-whatever-release-wherefrom-stuff?
With greeting from Munich ..
------- Additional Comments From buffer0 <at> t-online.de 2002-11-03 16:41 ------- This sort of "bug/error" and exception was caused by the incomplete installation of Bryce-4.0 (German release). The 'setup' by the CDROM distribution hadn't a proper run through (spurious!). Well, when having installed the [MetaStream],[QuickTime 3] and [Acrobat] folders explicitely in addition after the setup, one obtained a complete installation.
However, on my Suse-8.0 box/installation, all things had run through only to the point where some ALSA problems then occured:
Nov 4 00:00:05 teflon modprobe: modprobe: Can't locate module sound-slot-1 Nov 4 00:00:05 teflon modprobe: modprobe: Can't locate module sound-service-1-3 Nov 4 00:00:05 teflon modprobe: modprobe: Can't locate module sound-slot-2 Nov 4 00:00:05 teflon modprobe: modprobe: Can't locate module sound-service-2-3 Nov 4 00:00:06 teflon modprobe: modprobe: Can't locate module sound-slot-1 Nov 4 00:00:06 teflon modprobe: modprobe: Can't locate module sound-service-1-3 Nov 4 00:00:06 teflon modprobe: modprobe: Can't locate module sound-slot-2 Nov 4 00:00:06 teflon modprobe: modprobe: Can't locate module sound-service-2-3 Nov 4 00:00:06 teflon modprobe: modprobe: Can't locate module sound-slot-1 Nov 4 00:00:06 teflon modprobe: modprobe: Can't locate module sound-service-1-3 Nov 4 00:00:06 teflon modprobe: modprobe: Can't locate module sound-slot-2 Nov 4 00:00:06 teflon modprobe: modprobe: Can't locate module sound-service-2-3 Nov 4 00:00:06 teflon kernel: ALSA ../../../alsa-kernel/core/seq/oss/seq_oss_init.c:212: no device found
AND that's a different bug and story, I'll assume. So I'lll resolve/close Bug#1124.
What's the main thing with this bug? Well, wine is VERY sensitive on principle installation dependancies, and can't tell them to us ...
------- Additional Comments From johane <at> lysator.liu.se 2002-11-06 02:22 ------- The resolution shouldn't be fixed.
------- Additional Comments From johane <at> lysator.liu.se 2002-11-06 02:29 ------- Did the installer say that all necessary components were installed, when they were not? In that case this should be considered an open bug.
------- Additional Comments From johane <at> lysator.liu.se 2002-11-06 02:30 ------- A clicking-error...
------- Additional Comments From buffer0 <at> t-online.de 2002-11-06 10:53 ------- I'm testing wine and Bryce, with the following results:
[0]: The installer hadn't complained. The sole worse things had been with installing Quicktime where the window-management made trouble: The installer GUI put its screen on the screen with topmost priority, resulting that all other related subwindows aren't visible for the user.
What helped? Some alt-F4 or so under KDE, or some other hot-key under Enlightenment which allowed to change the window orders ...
[1]: Some hard thing must be wrong the window management! Bryce-4.0 runs only proper within the Desktop mode! When trying to run in fullscreen mode the main-top window can't be accessed. Seems a worse arrangment problem with X11 window management schemes.
[2]: wine crashes spuriously; '*click*' error/crash. But wine+Bryce crashes definitely intermediately when selecting under Bryce-help menu the about menu-entry.
[3]: An important thing for the wine-config file: "crtdll"= "native, builtin" is a must. Else Bryce-4.0 doesn't come up with its main screen.
[4]: wine+Bryce didn't had crashed yet on rendering. Meaning: All the window, menu and whatever I/O stuff seem to influencee much too hard the non-crashing quality of wine - with Bryce-4.0 - or?
So what? The *click+crash* problems are worse. But how fixing (it fast)? How jumping into the wine and w$dos machinery??
-
Wine Bugs