I'm using Ubuntu 10.04 with five workspaces set up in GNOME. I assume it's using compiz (I didn't tell it not to), which I know can interact problematically with Wine. I use Notes 7.03 for Windows quite happily in Wine at work. (I know there's a Linux client, but the installer seems very hard to get hold of casually.) As long as I use only one workspace. If I open it in one workspace and change to another, it's likely to crash. Or if I start it in one and try to move it to another. The command-line is unhelpful - it gives many lines of: err:win:DefWindowProcW called for other process window 0x1004c - and the closest I can see to useful information at crash time is: 27/04/2010 13:15:10.88 [0034:0002-0036] DynConfig> Found $DPLocked field: $DPLockedUnstrippede???? on policy note. Writing to loc doc 27/04/2010 13:15:11.06 [0034:0002-0036] DynConfig> Found $DPLocked field: $DPLockedUnstrippede???? on policy note. Writing to loc doc err:win:DefWindowProcW called for other process window 0x1004c err:win:DefWindowProcW called for other process window 0x1004c err:win:DefWindowProcW called for other process window 0x1004c err:win:DefWindowProcW called for other process window 0x1004c ... etc., etc. forever. Wine is 1.1.42 out of the Karmic wine-1.2 package, just updated today. This does *not* affect other programs running in Wine, e.g. Firefox win32. Any ideas on how I can better track down what's crashing where? Has anyone else seen this? - d.
On 27 April 2010 13:24, David Gerard <dgerard at gmail.com> wrote:> I'm using Ubuntu 10.04 with five workspaces set up in GNOME. I assume > it's using compiz (I didn't tell it not to), which I know can interact > problematically with Wine. > I use Notes 7.03 for Windows quite happily in Wine at work. (I know > there's a Linux client, but the installer seems very hard to get hold > of casually.) As long as I use only one workspace. If I open it in one > workspace and change to another, it's likely to crash. Or if I start > it in one and try to move it to another. > Wine is 1.1.42 out of the Karmic wine-1.2 package, just updated today. > This does *not* affect other programs running in Wine, e.g. Firefox win32. > Any ideas on how I can better track down what's crashing where? Has > anyone else seen this?FWIW, this is still happening occasionally with the current 1.2rc3 - but a lot less often! OTOH, this is on a different machine which will therefore have a different video card ... still under Ubuntu 10.04. - d.