registry team mailing list archive

[Bug Watch Updater <235613@xxxxxxxxxxxxxxxxxx>]

Launchpad has imported 9 comments from the remote bug at
http://bugs.winehq.org/show_bug.cgi?id=13296.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2008-05-18T08:32:28+00:00 Jan-winehq wrote:

Created an attachment (id=13150)
Logging output

I upgraded to  Ubuntu Hardy, and wine 1.0-rc1.
Hotsync manager 1.0 for Palm Pilot worked fine before.
http://appdb.winehq.org/objectManager.php?sClass=version&iId=10362

Now it crashes half-way synchronising over the serial port, sometimes after a few seconds, sometimes much later in the process.
These crashes reproduce well, and yield a segmentation fault without further information
$ wine hotsync.exe
Segmentation fault
$

I do not know if this means that a part of Wine crashes, or just the application.
I added logging, where it seems that the problem lies within the call below:
0009:CallTo16(func=111f:072a,ds=1087,118f,7404,0000,0006) ss:sp=1087:ffd0

I am not sure if the problem lies with wine, or that other problems with
Ubuntu Hardy may relate to this.

It is disappointing that an application that used to work fine, and I
came to depend on, is now broken.

Reply at: https://bugs.launchpad.net/openvz-
kernel/+bug/235613/comments/0

------------------------------------------------------------------------
On 2008-05-18T12:56:58+00:00 austin_is wrote:

Please run a regression test:

http://wiki.winehq.org/RegressionTesting

Reply at: https://bugs.launchpad.net/openvz-
kernel/+bug/235613/comments/1

------------------------------------------------------------------------
On 2008-05-22T16:35:51+00:00 Jan-winehq wrote:

I did rebuilds all the way back to "git checkout wine-0.9.50".
The problem reproduces all the way back to those versions.
This means that ANY of those builds of wine shows this problem under Ubuntu Hardy (kernel version 2.6.24-16-generic). This wine application did not show this bug under Gutsy (kernel version linux-2.6.22.14).

I guess some function now returns a value that it didn't before. 
I'm not sure what to do now, as the problem now seems to lie somewhere in the middle between wine and Ubuntu linux core development.

Note: The behavior at start-up changed to the behavior of those earlier
versions: the iconified version did not show up at the desktop.

Reply at: https://bugs.launchpad.net/openvz-
kernel/+bug/235613/comments/2

------------------------------------------------------------------------
On 2008-05-22T16:54:07+00:00 austin_is wrote:

(In reply to comment #2)
> I did rebuilds all the way back to "git checkout wine-0.9.50".
> The problem reproduces all the way back to those versions.
> This means that ANY of those builds of wine shows this problem under Ubuntu
> Hardy (kernel version 2.6.24-16-generic). This wine application did not show
> this bug under Gutsy (kernel version linux-2.6.22.14).
> 
> I guess some function now returns a value that it didn't before. 
> I'm not sure what to do now, as the problem now seems to lie somewhere in the
> middle between wine and Ubuntu linux core development.
> 
> Note: The behavior at start-up changed to the behavior of those earlier
> versions: the iconified version did not show up at the desktop.
> 

Have you filed a bug with ubuntu? You might try switching kernels under
gutsy or hardy to see if that's where the problem is...

Reply at: https://bugs.launchpad.net/openvz-
kernel/+bug/235613/comments/3

------------------------------------------------------------------------
On 2008-05-28T16:51:55+00:00 Jan-winehq wrote:

Created an attachment (id=13443)
Logging from Wine

Filed bug at Ubuntu under:
https://bugs.launchpad.net/ubuntu/+source/wine/+bug/235613

I just got the kernel upgrade from vmlinuz-2.6.24-16 to vmlinuz-2.6.24-17 (patch for Ubuntu Hardy).
Now, the problem is less frequent.
It seems that I can introduce the failure by either
1) switching electrical equipment nearby. 
2) switching on the logging (as for attached file) 
Therefore, I think that the crash occurs after a communications / timing  failure. 
Apparently, Hardy generates them, even with no ambient influences, where Feisty didn't.

Probably unrelated: at end of a succesful synchronisation, I now get :
fixme:comm:io_control Unsupported
fixme:ntdll:RtlNtStatusToDosErrorNoTeb no mapping for 000000c0

Reply at: https://bugs.launchpad.net/openvz-
kernel/+bug/235613/comments/4

------------------------------------------------------------------------
On 2008-10-17T03:31:28+00:00 Jan-winehq wrote:

Still crashes wine-1.1.6 with and kernel 2.6.24-21-generic #1 SMP Mon
Aug 25 17:32:09 UTC 2008 i686 GNU/Linux

err:seh:setup_exception_record nested exception on signal stack in
thread 0009 eip 7bc6688a esp 7ffdb900 stack 0x232000-0x330000

Reply at: https://bugs.launchpad.net/openvz-
kernel/+bug/235613/comments/10

------------------------------------------------------------------------
On 2009-03-08T08:18:30+00:00 Jan-winehq wrote:

Disappeared after upgrading to Ubuntu Intrepid, kernel version
2.6.27-11-generic #1 SMP Thu Jan 29 19:24:39 UTC 2009 i686 GNU/Linux
May have been kernel (rt2500 netwrok driver ?) bug.

Reply at: https://bugs.launchpad.net/openvz-
kernel/+bug/235613/comments/12

------------------------------------------------------------------------
On 2009-03-08T11:57:47+00:00 Vitaliy-bugzilla wrote:

Not Wine bug - invalid.

Reply at: https://bugs.launchpad.net/openvz-
kernel/+bug/235613/comments/13

------------------------------------------------------------------------
On 2009-03-08T11:58:02+00:00 Vitaliy-bugzilla wrote:

Closing

Reply at: https://bugs.launchpad.net/openvz-
kernel/+bug/235613/comments/14


** Changed in: wine
   Importance: Unknown => Medium

-- 
[Hardy][wine][regression] Segmentation Fault in Palm Hotsync over serial 
https://bugs.launchpad.net/bugs/235613
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for OpenVZ kernel.