[Bug 53830] New: can't fin the power key when opening an Approach database
https://bugs.winehq.org/show_bug.cgi?id=53830 Bug ID: 53830 Summary: can't fin the power key when opening an Approach database Product: Wine-staging Version: 7.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ToddAndMargo(a)zoho.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 73362 --> https://bugs.winehq.org/attachment.cgi?id=73362 Approach start up error message Fedora 36 wine-7.18-2.fc36.i686 (Wine Staging) Lotus Approach N99.8.0208.0800 This affects my business in a YUGE way! When attempting to open a database in Approach, the following error occurs: "Couldn't find the PowerKey for the database 2-22-parts." This is a regression from 7.12 (regression testing is over my head). Please send me what tests/data you wish me to collect. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53830 Todd Chester <ToddAndMargo(a)zoho.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|can't fin the power key |can't find the power key |when opening an Approach |when opening an Approach |database |database -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53830 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|critical |normal CC| |o.dierick(a)piezo-forte.be --- Comment #1 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, Issues in a single application are severity 'normal'. Read more about severity levels descriptions there: https://wiki.winehq.org/Bugs#severity Please, attach a normal (=without WINEDEBUG) terminal output. Instructions to get a log can be found there: https://wiki.winehq.org/FAQ#get_log Does the issue happen with upstream wine? Regards. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53830 Todd Chester <ToddAndMargo(a)zoho.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #2 from Todd Chester <ToddAndMargo(a)zoho.com> --- Well now. A reboot solved the issue. Closing as not a bug -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53830 Todd Chester <ToddAndMargo(a)zoho.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |--- Severity|normal |major Status|RESOLVED |UNCONFIRMED --- Comment #3 from Todd Chester <ToddAndMargo(a)zoho.com> --- And the next reboot and it is back. Reopening -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53830 --- Comment #4 from Todd Chester <ToddAndMargo(a)zoho.com> --- It transpires that if i open the database in a qemu-kvm Window2 10 session and then close it, Wine's version will open. Wait overnight and the symptom comes back -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53830 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|major |normal --- Comment #5 from Austin English <austinenglish(a)gmail.com> --- Again, not major. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53830 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53830 --- Comment #6 from Todd Chester <ToddAndMargo(a)zoho.com> --- (In reply to Austin English from comment #5)
Again, not major.
I was basing the "Major" by its impact on my business for which the bug is having a "Major" impact on. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53830 --- Comment #7 from Austin English <austinenglish(a)gmail.com> --- (In reply to Todd Chester from comment #6)
(In reply to Austin English from comment #5)
Again, not major.
I was basing the "Major" by its impact on my business for which the bug is having a "Major" impact on.
As you've been told before, that's not what the severity is based on, it's based on how many applications/platforms the bug affects. If you really want to see it fixed, you can help by running the regression test. As an aside, I'd suggest sticking to a known working version of wine if your business depends on it and only rolling out mew versions after testing on a controlled environment.. or look into Crossover for paid support -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53830 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #8 from Austin English <austinenglish(a)gmail.com> --- In any event, please attach the terminal output as requested in comment #1 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53830 --- Comment #9 from Todd Chester <ToddAndMargo(a)zoho.com> --- (In reply to Austin English from comment #7)
As you've been told before, that's not what the severity is based on, it's based on how many applications/platforms the bug affects.
That explains it. I was looking at it from the impact it had on me and not on the rest of your users. And I do not remember ever having that explained to me. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53830 --- Comment #10 from Todd Chester <ToddAndMargo(a)zoho.com> --- (In reply to Austin English from comment #8)
In any event, please attach the terminal output as requested in comment #1
It is not bricking today. It is remissness of an "uninitialized variable". I will provide a "terminal output" next time it bricks. Version 6 works fine. Version 7 has been a nightmare for me. Is there a way I can download and create a Fedora repo of 6 of my own as Fedora advances is revision and I lose access to 6? This is currently working, but I may lose it in the future: # dnf --setopt=excludepkgs="" downgrade wine --releasever=35 Oh and a regression test is way, way over my head. I have stated that several times before. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53830 --- Comment #11 from Todd Chester <ToddAndMargo(a)zoho.com> --- Created attachment 73373 --> https://bugs.winehq.org/attachment.cgi?id=73373 wine approach.exe > home/temp/Approach.Power.Key.Error.txt 2>&1 Okay, the "power Key" error started again and I caught it on a trace export WINEDEBUG=+winspoolwine $ set | grep -i wine WINEDEBUG=+winspoolwine wine approach.exe > home/temp/Approach.Power.Key.Error.txt 2>&1 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53830 --- Comment #12 from Todd Chester <ToddAndMargo(a)zoho.com> --- I found if I just wait about four minutes, I can get my databases to open. But if I keep trying over and over, I can not. Maybe that tell you something. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53830 --- Comment #13 from Todd Chester <ToddAndMargo(a)zoho.com> --- How do you turn off the needs info status? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53830 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |UNCONFIRMED Ever confirmed|1 |0 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53830 --- Comment #14 from Todd Chester <ToddAndMargo(a)zoho.com> --- Issue reproduces in wine-7.18-2.fc36.i686 (wine.repo) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53830 --- Comment #15 from Todd Chester <ToddAndMargo(a)zoho.com> --- Fedora 37 wine-7.22-2.fc37.x86_64 Power key error on longer appears. But Approach can not print anything to any printer. And it never even shows up is the CUPS queue. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53830 Todd Chester <ToddAndMargo(a)zoho.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #16 from Todd Chester <ToddAndMargo(a)zoho.com> --- Go ahead and close in wine-common-8.0-1.fc37.noarch No longer able to duplicate -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53830 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #17 from Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> --- Closing Fixed wine-staging bug. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla