http://bugs.winehq.org/show_bug.cgi?id=18237
Summary: Lotus Notes Client 6.5.5 email adress resolving slowed down Product: Wine Version: 1.1.20 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: toralf.foerster@gmx.de
Probably a regression between 1.1.19 and 1.1.20 which slowed down Lotus Notes 6.5.5 for a task like resolving an email address. If I type in "firstname lastname" followed by a comma into the "To." field of a new mail, it takes usually 1 second with wine-1.1.19 to get the full Lotus Notes Email address. With wine-1.1.20 it takes up to 20 or 30 seconds. Furthermore it seems that it needs much longer to open the mailbox database or to create the window of a new email (even w/ using the local replic).
http://bugs.winehq.org/show_bug.cgi?id=18237
--- Comment #1 from Austin English austinenglish@gmail.com 2009-04-27 10:39:55 --- Regression test? http://wiki.winehq.org/RegressionTesting
http://bugs.winehq.org/show_bug.cgi?id=18237
--- Comment #2 from Toralf Förster toralf.foerster@gmx.de 2009-04-28 02:51:39 --- (In reply to comment #1)
Regression test? http://wiki.winehq.org/RegressionTesting
such task would take a lot of time and cannot be automated. I'd like to avoid such effort if there's another way - and BTW my current experiences w/ spending such big effort into bisection of an issue (bug #17324) are bad :-(
http://bugs.winehq.org/show_bug.cgi?id=18237
--- Comment #3 from Austin English austinenglish@gmail.com 2009-04-28 09:52:02 --- (In reply to comment #2)
(In reply to comment #1)
Regression test? http://wiki.winehq.org/RegressionTesting
such task would take a lot of time and cannot be automated. I'd like to avoid such effort if there's another way - and BTW my current experiences w/ spending such big effort into bisection of an issue (bug #17324) are bad :-(
We don't know the cause of the issue without the regression test. It's easiest to fix when the code is fresh in the developer's mind.
It CAN be automated, if you can script the problem: http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html http://lwn.net/Articles/317154/
http://bugs.winehq.org/show_bug.cgi?id=18237
--- Comment #4 from Toralf Förster toralf.foerster@gmx.de 2009-04-28 10:35:11 --- To reduce the overall effort (I'm familar with scripting and bisecting, I do it often enough for the linux kernel, however there's sth to enter in into the LN client), it would be nice to be pointed out to the suspicous subsystem if possible.
http://bugs.winehq.org/show_bug.cgi?id=18237
--- Comment #5 from Austin English austinenglish@gmail.com 2009-04-28 11:49:18 --- (In reply to comment #4)
To reduce the overall effort (I'm familar with scripting and bisecting, I do it often enough for the linux kernel, however there's sth to enter in into the LN client), it would be nice to be pointed out to the suspicous subsystem if possible.
You can use Autohotkey to script up something: http://www.autohotkey.com/
very simple scripting language, works great with Wine.
http://bugs.winehq.org/show_bug.cgi?id=18237
Toralf Förster toralf.foerster@gmx.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #6 from Toralf Förster toralf.foerster@gmx.de 2009-04-29 03:44:04 --- I'll give it a try next time. This bug however I'd like to close b/c after changing my location and updateing the linux kernel the issue went away.
http://bugs.winehq.org/show_bug.cgi?id=18237
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #7 from Dmitry Timoshkov dmitry@codeweavers.com 2009-04-29 03:56:11 --- Closing.
-
wine-bugs＠winehq.org