http://bugs.winehq.org/show_bug.cgi?id=18324
Summary: Lotus 123 crashes on copy to clipboard Product: Wine Version: 1.1.20 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: ToddAndMargo@verizon.net
Created an attachment (id=20865) --> (http://bugs.winehq.org/attachment.cgi?id=20865) test file to treat copy to clipboard crash
Hi All,
In Lotus 123 (v9), if you highlight across two cell horizontally, then go the "Edit", "Copy" 123 will crash. This makes 123 unusable under Wine (why the "major" severity).
Also, Linux acts really weird until your kill the 123 process
Steps to reproduce: 1) open the 123 attachment I am about to post 2) highlight across two cell horizontally 3) press <ctrl><c> or go to "Edit", "Copy"
http://bugs.winehq.org/show_bug.cgi?id=18324
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|major |normal
--- Comment #1 from Dmitry Timoshkov dmitry@codeweavers.com 2009-05-01 23:48:16 --- http://bugs.winehq.org/page.cgi?id=fields.html#bug_severity
Please attach full console output including the backtrace.
http://bugs.winehq.org/show_bug.cgi?id=18324
--- Comment #2 from Todd Chester ToddAndMargo@verizon.net 2009-05-01 23:51:54 --- Created an attachment (id=20866) --> (http://bugs.winehq.org/attachment.cgi?id=20866) copy to clipboard crash log
/usr/local/bin/wine "/home/wine/drive_c/lotus/123/123w.exe" "/home/temp/CopyAndPasteCrash.123" > /home/temp/123CopyCrash.log 2>&1
http://bugs.winehq.org/show_bug.cgi?id=18324
--- Comment #3 from Todd Chester ToddAndMargo@verizon.net 2009-05-01 23:53:39 --- (In reply to comment #1)
http://bugs.winehq.org/page.cgi?id=fields.html#bug_severity
Please attach full console output including the backtrace.
Hi Dmitry,
What do you mean by "console output including the backtrace"? Was the log I just posted what you wanted?
-T
http://bugs.winehq.org/show_bug.cgi?id=18324
--- Comment #4 from Dmitry Timoshkov dmitry@codeweavers.com 2009-05-02 05:24:14 --- (In reply to comment #3)
What do you mean by "console output including the backtrace"?
What you've attached is almost fine.
Was the log I just posted what you wanted?
It lacks the debugger backtrace.
http://bugs.winehq.org/show_bug.cgi?id=18324
--- Comment #5 from Todd Chester ToddAndMargo@verizon.net 2009-05-02 13:24:32 --- (In reply to comment #4)
It lacks the debugger backtrace.
From what you see on what I did post, what command line arguments do you need?
http://bugs.winehq.org/show_bug.cgi?id=18324
--- Comment #6 from Vitaliy Margolen vitaliy@kievinfo.com 2009-05-02 19:34:29 --- (In reply to comment #5) There are lots of lines that follow "starting debugger..". See this for more info: http://wiki.winehq.org/FAQ#get_log Attach the complete file.
http://bugs.winehq.org/show_bug.cgi?id=18324
--- Comment #7 from Todd Chester ToddAndMargo@verizon.net 2009-05-03 15:06:46 --- Created an attachment (id=20893) --> (http://bugs.winehq.org/attachment.cgi?id=20893) 123 copy crash #2
(In reply to comment #5) There are lots of lines that follow "starting debugger..". See this for more info: http://wiki.winehq.org/FAQ#get_log Attach the complete file.
Okay. I get it now. What I did was to kill 123 (kill -9 ...) while the debugger was still running. This I did as Linux got really weird while the debugger was running and I did not realize what was happening. So here we go a second time.
I let it run for 15 minutes. I had to kill the process, as I could not use any other running program on my computer. (But could start new ones, which is how I killed the process.)
This is pretty easy to reproduce, as I have included the offending file. Would on of the experts please try reproducing my problem?
Many thanks, -T
http://bugs.winehq.org/show_bug.cgi?id=18324
--- Comment #8 from Todd Chester ToddAndMargo@verizon.net 2009-05-03 15:48:06 --- "one of the experts" not "on of the experts". Stinkin' typos
I had to kill the process, as I could not use any other running program on my computer. (But could start new ones, which is how I killed the process.)
Hi Guys,
Should I open a bug report on the debugger, or is this report sufficient?
-T
http://bugs.winehq.org/show_bug.cgi?id=18324
--- Comment #9 from Todd Chester ToddAndMargo@verizon.net 2009-05-08 21:29:13 --- Hi Guys,
No one ever answered me as to whether or not I should file a bugs against the bug reporter as well.
Also: I have duplicate the same error in Word Pro with live (highly private) data in tables, but have been unable to recreate a sample for you guys. If you fix the 123 error, I am sure you will also get its cousin in Word Pro.
Many thanks, -T
http://bugs.winehq.org/show_bug.cgi?id=18324
Todd Chester ToddAndMargo@verizon.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ToddAndMargo@verizon.net
--- Comment #10 from Todd Chester ToddAndMargo@verizon.net 2009-05-11 14:42:46 --- No symptom change under 1.1.21 :-(
http://bugs.winehq.org/show_bug.cgi?id=18324
--- Comment #11 from Todd Chester ToddAndMargo@verizon.net 2009-06-05 17:07:25 --- No change under 1.1.23 :'(
http://bugs.winehq.org/show_bug.cgi?id=18324
--- Comment #12 from Todd Chester ToddAndMargo@verizon.net 2009-08-09 20:28:26 --- I am unable to reproduce this under Wine 1.1.27. This bug was a total pain in the, eh, well, neck. Thank you guys so, so much!
Please close this ticket as "FIXED". YIPEE!
-T (the "Original Poster")
http://bugs.winehq.org/show_bug.cgi?id=18324
Ken Sharp kennybobs@o2.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #13 from Ken Sharp kennybobs@o2.co.uk 2009-08-09 20:34:16 --- Fixed.
Note: You can change bugs you have logged yourself.
http://bugs.winehq.org/show_bug.cgi?id=18324
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #14 from Alexandre Julliard julliard@winehq.org 2009-08-21 12:47:04 --- Closing bugs fixed in 1.1.28.