Here I am. Ove Kaaven wrote:
>>well that's a wine bug. >> >> > >Umm? What? Okay, Wine may have problems with some kernels, but if it was >just a Wine bug, then Wine would crash and burn and that's it. However, >if Wine actually manages to freeze the whole system, that's not just a >Wine bug, that's a critical kernel security issue (local exploit). > > that was the exact reason why I posted this issue as a kernel bug: ideally, the kernel shouldn't lock if apps in the userspace misbehave. >Alternatively, it could just be the X server that's hung, I suppose, but >I don't think you should be so quick to reassign it without knowing any >details. > >If the original submitter can verify that it's the entire system that's >totally unresponsive (by e.g. trying to ssh in remotely), or just the >console, then perhaps we can assign this properly. > > just tested a couple of times to access with ssh after system hang, after a kernel update to 2.6.15-2: the response was "no route to host". The last attempt I made, for the first time, the mouse pointer was still responding while the system was hung: also in that situation the client couldn't connect (no route to host). I really don't know how to give more details in this situation: please help me to give you the right information. I'm currently using Crossover Office Pro 5.0.0, but before posting I made some tests with a fresh install of wine 0.9.5, with identical results. Mau -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
