http://bugs.winehq.org/show_bug.cgi?id=21736
Summary: Quicken 2004 Premier Ctrl+F is not recognized on application launch. Product: Wine Version: 1.0.1 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: rhdinah@yahoo.com
When launching Quicken the keyboard shortcut Ctrl+F (Find) does nothing ... reliably nothing. However, if you traverse the Quicken menus Edit | Find & Replace | Find ... then the Find request and operation proceeds normally. Interestingly enough after this is done then the Ctrl+F keyboard shortcut is recognized.
http://bugs.winehq.org/show_bug.cgi?id=21736
--- Comment #1 from Andrew Nguyen arethusa26@gmail.com 2010-02-16 00:35:16 --- Please retest the application in the latest development version of Wine (1.1.38).
http://bugs.winehq.org/show_bug.cgi?id=21736
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |minor
http://bugs.winehq.org/show_bug.cgi?id=21736
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |ABANDONED
--- Comment #2 from Austin English austinenglish@gmail.com 2011-11-17 00:06:21 CST --- 1.5 years, no response, no download => abandoned.
http://bugs.winehq.org/show_bug.cgi?id=21736
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #3 from Austin English austinenglish@gmail.com 2011-11-17 00:10:32 CST --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=21736
Robert H. Dinah rhdinah@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |UNCONFIRMED Resolution|ABANDONED |
--- Comment #4 from Robert H. Dinah rhdinah@yahoo.com 2011-11-26 23:31:36 CST --- Not so fast now Mr. Austin English ...
Mr. Andrew Nguyen asked that it be retested with the newest version in development ... which I did not do because of the amount of work it would involve on my part ... plus his request was clearly a stop gap measure putting the onus back on me. It DID NOT REQUIRE NOR DID IT ASK FOR a response. I've repeatedly tested this bug with all the newer PRODUCTION versions ... and it still does not work.
So please don't insult me with assuming that I'm not interested in this being fixed and setting the status to RESOLVED, ABANDONED and then CLOSED. I have not abandoned my bug entry ... and you cannot just blanketly assume that this bug is fixed. It is not.
I love you guys and all, but you should have a more professional way at looking at bugs. They clearly are bugs. Whether they get fixed or not is another question.
http://bugs.winehq.org/show_bug.cgi?id=21736
--- Comment #5 from Vitaliy Margolen vitaliy-bugzilla@kievinfo.com 2011-11-27 10:00:42 CST --- Please retest this application with latest development Wine version (wine-1.3.33). Old "stable" Wine versions are not being worked work on past their release.
http://bugs.winehq.org/show_bug.cgi?id=21736
--- Comment #6 from Robert H. Dinah rhdinah@yahoo.com 2011-11-27 10:17:22 CST --- (In reply to comment #5)
Please retest this application with latest development Wine version (wine-1.3.33). Old "stable" Wine versions are not being worked work on past their release.
It still doesn't work. Obviously you haven't read my message.
http://bugs.winehq.org/show_bug.cgi?id=21736
Robert H. Dinah rhdinah@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|1.0.1 |1.2.2
http://bugs.winehq.org/show_bug.cgi?id=21736
--- Comment #7 from Vitaliy Margolen vitaliy-bugzilla@kievinfo.com 2011-11-27 12:39:09 CST --- (In reply to comment #6)
It still doesn't work. Obviously you haven't read my message.
Please specify what latest Wine version have you used to test your application. Other then rant your comment 4 contained no useful information whatsoever.
http://bugs.winehq.org/show_bug.cgi?id=21736
Dmitry Timoshkov dmitry@baikal.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|1.2.2 |1.0.1
http://bugs.winehq.org/show_bug.cgi?id=21736
--- Comment #8 from Robert H. Dinah rhdinah@yahoo.com 2011-11-28 09:48:59 CST --- (In reply to comment #7)
(In reply to comment #6)
It still doesn't work. Obviously you haven't read my message.
Please specify what latest Wine version have you used to test your application. Other then rant your comment 4 contained no useful information whatsoever
I had indicated 1.2.2 and Dmitry Timoshkov chose to change it back to 1.0.1.
Other then rant your comment 4 contained no useful information whatsoever.
Consider the case closed.
http://bugs.winehq.org/show_bug.cgi?id=21736
--- Comment #9 from Dmitry Timoshkov dmitry@baikal.ru 2011-11-28 09:59:36 CST --- Adding a comment to the bug is enough, don't change an originally reported Wine version. Please read once again comment #5, and follow the request there.
http://bugs.winehq.org/show_bug.cgi?id=21736
--- Comment #10 from Robert H. Dinah rhdinah@yahoo.com 2011-11-28 18:15:28 CST --- (In reply to comment #9)
Adding a comment to the bug is enough, don't change an originally reported Wine version. Please read once again comment #5, and follow the request there.
It is difficult for me to understand the underpinnings and mentality of WINE's quality assurance procedures ... 'nuf said on that ...
Since I use Ubuntu 10.04 LTS in my business, I cannot afford the risk of placing sub-alpha development code on my machine. I'm certain you understand that.
After the new year I will build another machine with the latest Ubuntu and your latest development code and retest this. I am certain however ... and willing to wager immense amounts of money ... that nothing has changed with regard to this bug.
Thank you for being polite in your response ... but with respect to the other person's response:
In my software development career had a person in my shop responded in that way to a customer they would have been shown the door ... pronto ...
http://bugs.winehq.org/show_bug.cgi?id=21736
--- Comment #11 from Alexandre Julliard julliard@winehq.org 2011-11-29 03:43:33 CST --- (In reply to comment #10)
In my software development career had a person in my shop responded in that way to a customer they would have been shown the door ... pronto ...
If you are not happy with the service, feel free to ask for a refund.
http://bugs.winehq.org/show_bug.cgi?id=21736
--- Comment #12 from Robert H. Dinah rhdinah@yahoo.com 2011-11-29 10:48:26 CST --- (In reply to comment #11)
(In reply to comment #10)
In my software development career had a person in my shop responded in that way to a customer they would have been shown the door ... pronto ...
If you are not happy with the service, feel free to ask for a refund.
Yet another wise-ass comment ... a sign of maturity I presume ...
http://bugs.winehq.org/show_bug.cgi?id=21736
Vitaliy Margolen vitaliy-bugzilla@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |ABANDONED
--- Comment #13 from Vitaliy Margolen vitaliy-bugzilla@kievinfo.com 2011-11-29 19:24:49 CST --- (In reply to comment #12) You should probably check who you telling this to.
Closing abandoned. Please in the future refrain from using bugzilla unless you really change your point of view of open source projects. Which run by volunteers on their own time at their own expense.
http://bugs.winehq.org/show_bug.cgi?id=21736
Vitaliy Margolen vitaliy-bugzilla@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #14 from Vitaliy Margolen vitaliy-bugzilla@kievinfo.com 2011-11-29 19:25:52 CST --- Closing. No need to reopen. It will be ignored anyway. Consider this your refund.
http://bugs.winehq.org/show_bug.cgi?id=21736
--- Comment #15 from Robert H. Dinah rhdinah@yahoo.com 2011-11-29 23:42:09 CST --- (In reply to comment #14)
Closing. No need to reopen. It will be ignored anyway. Consider this your refund.
Thank you ...
Remember this is WINE's bug, not mine ... it was submitted in good faith ... on my time and at my expense ... ignoring bugs does not fix them ... true? It was not submitted because I needed a fix ... it was submitted to improve the code ... your code ...
You should probably check who you telling this to.
Golly ...
change your point of view of open source projects ...
I've always have a good and proper point of view on open source projects ... and its volunteers ... I just don't appreciate being spoken 'down to' by them.
Anyway ... sadly ... you've lost a friend, admirer and supporter ... I know that won't bring tears to your eyes, but it does mine. до свидания ...
http://bugs.winehq.org/show_bug.cgi?id=21736
--- Comment #16 from Juan Lang juan.lang@gmail.com 2011-11-30 10:25:41 CST --- (In reply to comment #15)
Remember this is WINE's bug, not mine ... it was submitted in good faith ... on my time and at my expense ... ignoring bugs does not fix them ... true? It was not submitted because I needed a fix ... it was submitted to improve the code ... your code ...
We aren't ignoring it. We asked you to retest it, you didn't, then you badmouthed us when we said you weren't responsive. You followed up with an ad hominem attack. If you're trolling, it's succeeding. If we've lost a friend, well, you haven't shown any friendliness here.
http://bugs.winehq.org/show_bug.cgi?id=21736
--- Comment #17 from Robert H. Dinah rhdinah@yahoo.com 2011-11-30 11:32:19 CST --- (In reply to comment #16)
(In reply to comment #15)
Remember this is WINE's bug, not mine ... it was submitted in good faith ... on my time and at my expense ... ignoring bugs does not fix them ... true? It was not submitted because I needed a fix ... it was submitted to improve the code ... your code ...
We aren't ignoring it. We asked you to retest it, you didn't, then you badmouthed us when we said you weren't responsive. You followed up with an ad hominem attack. If you're trolling, it's succeeding. If we've lost a friend, well, you haven't shown any friendliness here.
We aren't ignoring it.
And I quote: "Closing. No need to reopen. It will be ignored anyway. Consider this your refund."
We asked you to retest it, you didn't
Yes and no ... true I didn't test it with a development version, because I didn't wish to corrupt my machine with sub-alpha code ... as I mentioned I use my machine in my work. However I DID TEST IT on each and every new production release of WINE ... and it never worked ... and the request did not say to report back the results. In my eyes testing with a development release for something as simple as a keyboard accelerator ... when clearly it wasn't being addressed all along ... made it appear to put the onus back on me ... which created frustration. In development shops I've worked it was never the responsibility of the bug submitter to test or debug his bug. Of course when I was assigned a bug that was particularly difficult to reproduce I would engage the submitter to reproduce the bug so that I could do so in like manner at my desk as a developer. And that is the reason for my statement: "It is difficult for me to understand the underpinnings and mentality of WINE's quality assurance procedures".
When my manager asked me to test something I would. If he asked me to report back by some time I would. Otherwise I'd not bother him in his busy day unless he specifically asked me what happened on the test.
then you badmouthed us when we said you weren't responsive.
No I "badmouthed" you when for apparently no reason the words "non-responsive" and "abandoned" came out the middle of nowhere in my email ... without a previous kind message to me of any potential status that I may have observed. Should the team have asked me to test code with specific debugging code addressing this bug I would have created a test machine to do so gladly. Had they asked and delivered development code to me with debugging symbols in it I would have attempted to debug it for you. Since I am a Windows and Unix developer myself this would have been easy, however, like you all I am a very busy person. [sigh ... why am I writing this?]
"If you're trolling"
Name calling is not nice.
"Other then rant your comment 4 contained no useful information whatsoever."
Agreed, but the tone of this is not nice.
"Adding a comment to the bug is enough, don't change an originally reported
Wine version. Please read once again comment #5, and follow the request there."
IMHO what I consider a properly made polite statement.
"If you are not happy with the service, feel free to ask for a refund."
An overused, shameful and insulting statement ... especially considering who made it.
"you haven't shown any friendliness here"
Looking back on the thread I concur ... most of them were made in frustration ... should this have insulted your team ... I apologize ... however as documented above ... and again looking back on the thread ... neither does the WINE team.
One more thing, please:
"You should probably check who you telling this to."
If Jesus or God had spoken to me I would have known it AND they would have told me they were Jesus or God. Other people because of their status don't impress me and I certainly don't raise them up and onto a pedestal. Nevertheless I still would invite, expect and return intelligent, polite conversation and due respect.
http://bugs.winehq.org/show_bug.cgi?id=21736
Juan Lang juan.lang@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Resolution|ABANDONED | Ever Confirmed|0 |1
--- Comment #18 from Juan Lang juan.lang@gmail.com 2011-11-30 13:29:02 CST --- Ok, so it didn't work on version 1.2.3? I'll reopen, though we'd really appreciate a retest on a more recent development version: the difference between development and release is often pretty small. (Volunteers => we do the best we can with QA, but that's not very good.)
It's possible to install more than one simultaneously, and using different WINEPREFIXes. I'll describe it briefly: download the source to the latest development version, e.g. to ~/src/wine, and build it (cd ~/src/wine && ./configure && make).
Install Quicken in its own wineprefix:
WINEPREFIX=~/.wine-quickentest ~/src/wine/wine path/to/quicken/setup.exe
Run Quicken from its new install location:
cd ~/.wine-quickentest/drive_c/path/to/quicken ~/src/wine/wine ./quicken.exe
http://bugs.winehq.org/show_bug.cgi?id=21736
--- Comment #19 from Robert H. Dinah rhdinah@yahoo.com 2011-11-30 21:03:06 CST --- (In reply to comment #18)
Ok, so it didn't work on version 1.2.3? I'll reopen, though we'd really appreciate a retest on a more recent development version: the difference between development and release is often pretty small. (Volunteers => we do the best we can with QA, but that's not very good.)
It's possible to install more than one simultaneously, and using different WINEPREFIXes. I'll describe it briefly: download the source to the latest development version, e.g. to ~/src/wine, and build it (cd ~/src/wine && ./configure && make).
Install Quicken in its own wineprefix:
WINEPREFIX=~/.wine-quickentest ~/src/wine/wine path/to/quicken/setup.exe
Run Quicken from its new install location:
cd ~/.wine-quickentest/drive_c/path/to/quicken ~/src/wine/wine ./quicken.exe
I will test this on an old test machine with Ubuntu Maverick this weekend ... with the current development version of WINE that I can find online. See? I'm not the horrible beast from the abyss that I've been purported to be ...
Thank you Juan for your informative and intelligent instructions. This is *exactly* what I was looking for and not receiving. I'll be back with the results hopefully early next week.
http://bugs.winehq.org/show_bug.cgi?id=21736
Vitaliy Margolen vitaliy-bugzilla@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |ABANDONED
--- Comment #20 from Vitaliy Margolen vitaliy-bugzilla@kievinfo.com 2011-11-30 21:28:45 CST --- As I said closed, DO NOT reopen.
http://bugs.winehq.org/show_bug.cgi?id=21736
Vitaliy Margolen vitaliy-bugzilla@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #21 from Vitaliy Margolen vitaliy-bugzilla@kievinfo.com 2011-11-30 21:29:00 CST --- Closed is closed.
http://bugs.winehq.org/show_bug.cgi?id=21736
--- Comment #22 from Vitaliy Margolen vitaliy-bugzilla@kievinfo.com 2011-11-30 21:33:43 CST --- Oh and all the "nice" remarks doesn't really make you smarter or more polite. It shows exactly who you are - and ignorant jerk. Who don't even care to check who founded the Wine project, who still running it after 15 years, and who have respect of every Wine developer. And who deserves respect of AVERY Wine user.
Of course what do you know? Trolls not supposed to know anything or their trolling won't work.
http://bugs.winehq.org/show_bug.cgi?id=21736
Juan Lang juan.lang@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Resolution|ABANDONED |
--- Comment #23 from Juan Lang juan.lang@gmail.com 2011-11-30 22:32:47 CST --- Vitaliy, this bug clearly isn't abandoned. The flaming is unfortunate, but it's really not an appropriate status for the bug, so please leave this one be.
http://bugs.winehq.org/show_bug.cgi?id=21736
Vitaliy Margolen vitaliy-bugzilla@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |ABANDONED
--- Comment #24 from Vitaliy Margolen vitaliy-bugzilla@kievinfo.com 2011-11-30 22:49:41 CST --- When he is able to produce the test results with recent Wine version - sure. But until then, he added no useful content.
Back to Abandoned.
http://bugs.winehq.org/show_bug.cgi?id=21736
--- Comment #25 from Robert H. Dinah rhdinah@yahoo.com 2011-11-30 23:30:21 CST --- (In reply to comment #24)
When he is able to produce the test results with recent Wine version - sure. But until then, he added no useful content.
Back to Abandoned.
Such hatred and name slinging ... why should I bother then ... as you say, in your statement, abandoned is abandoned. Vitaliy you come off as an arrogant, overbearing, abrasive and unpleasant person. Debug it yourself.
Oh, and what is the big deal with the WINE project anyway? Honestly who gives a damn. I'm much more comfortable with VirtualBox anyway ... and you know what? It has very, very few errors and runs EVERYTHING ...
Sorry Juan, I'll not be submitting any test results next week. I really don't like what I'm hearing ... and I'm leaving this thread.
http://bugs.winehq.org/show_bug.cgi?id=21736
Robert H. Dinah rhdinah@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|ABANDONED |
--- Comment #26 from Robert H. Dinah rhdinah@yahoo.com 2011-12-02 12:08:34 CST --- I fired up my test machine with Ubuntu Lucid Lynx (10.04 LTS), installed the binaries for 1.3.33 and Quicken 2004 with a simple checking account with two entries and the problem remains.
http://bugs.winehq.org/show_bug.cgi?id=21736
--- Comment #27 from Austin English austinenglish@gmail.com 2013-12-05 21:50:48 CST --- This is your friendly reminder that there has been no bug activity for 2 years. Is this still an issue in current (1.7.7 or newer) wine? If so, please attach the terminal output in 1.7.7 (see http://wiki.winehq.org/FAQ#get_log).
https://bugs.winehq.org/show_bug.cgi?id=21736
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |ABANDONED
--- Comment #28 from Austin English austinenglish@gmail.com --- (In reply to Austin English from comment #27)
This is your friendly reminder that there has been no bug activity for 2 years. Is this still an issue in current (1.7.7 or newer) wine? If so, please attach the terminal output in 1.7.7 (see http://wiki.winehq.org/FAQ#get_log).
Abandoned.
https://bugs.winehq.org/show_bug.cgi?id=21736
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #29 from Austin English austinenglish@gmail.com --- Closing.
-
wine-bugs＠winehq.org