Winff startup warning about access violation and possible data corruption
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Winff |
Unknown
|
Unknown
|
|||
winff (Ubuntu) |
Fix Released
|
Undecided
|
Andrew Starr-Bochicchio |
Bug Description
Binary package hint: winff
Executing Lucid's WinFF in a terminal leads to the following output:
[WARNING] Out of OEM specific VK codes, changing to unassigned
[WARNING] Out of unassigned VK codes, assigning $FF
[FORMS.PP] ExceptionOccurred
Sender=
Exception=Access violation
Stack trace:
$00364F6E
$08290BCD
$081BCA9B
$081BBCEA
$0817AC98
$0817A885
$0817B87A
$0817AD75
$0817A885
$0817B87A
$0817AD75
$08077CC1
$0807CFAC
$0807E069
$0817A885
$0817B87A
$080853CE
TApplication.
Stack trace:
$00364F6E
$08290BCD
$081BCA9B
$081BBCEA
$0817AC98
$0817A885
$0817B87A
$0817AD75
$0817A885
$0817B87A
$0817AD75
$08077CC1
$0807CFAC
$0807E069
$0817A885
$0817B87A
$080853CE
-------
Additionally, a popup opens. See attached screenshot.
Pressing OK closes the popup, but the program does not show up afterwards.
Deleting the .winff folder had no effect.
WinFF in Karmic worked flawlessly.
ProblemType: Bug
Architecture: i386
Date: Sun Feb 14 18:58:09 2010
DistroRelease: Ubuntu 10.04
NonfreeKernelMo
Package: winff 1.2.0-1ubuntu1
ProcEnviron:
LANGUAGE=
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: winff
Uname: Linux 2.6.32-13-generic i686
Changed in winff (Ubuntu): | |
status: | New → Confirmed |
assignee: | nobody → Paul Gevers (paul-climbing) |
Changed in winff (Ubuntu): | |
assignee: | nobody → SevenMachines (sevenmachines) |
tags: | added: patch |
Changed in winff (Ubuntu): | |
assignee: | SevenMachines (sevenmachines) → nobody |
Changed in winff (Ubuntu): | |
status: | Confirmed → In Progress |
assignee: | nobody → Andrew Starr-Bochicchio (andrewsomething) |
Thanks for reporting this issue.
I am not sure, but it might be related to the fact that gtk+2.0 got an update two days ago (i.e. after this winff was build). At least that is what upstream has seen before with this kind of error. Maybe rebuilding winff is all that is needed. Could somebody verify this?