[Bug 48200] New: Approach "Shell" function stopped working
https://bugs.winehq.org/show_bug.cgi?id=48200 Bug ID: 48200 Summary: Approach "Shell" function stopped working Product: Wine-staging Version: 4.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major 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: --- $ rpm -qa wine-common wine-common-4.20-1.fc31.noarch Fedora 31, x64 Help! Lotus Approach's "Shell" function in Word Pro stopped working after upgrading to 4.20. Result = Shell ( "z:\home\linuxutil\CopyToClipboard.pl" + " " + FullAddress) CopyToClipboard.pl never see the call. This happens on all me shell call. Its killing 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=48200 --- Comment #1 from Todd Chester <ToddAndMargo(a)zoho.com> --- Downgrading Wine corrected the issue: # dnf downgrade wine-* # rpm -qa wine-core wine-core-4.17-2.fc31.i686 wine-core-4.17-2.fc31.x86_64 -- 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=48200 --- Comment #2 from Todd Chester <ToddAndMargo(a)zoho.com> ---
Lotus Approach's "Shell" function in Word Pro
The shell command does not work in Approach. I haven't tried it on Word Pro. Word Pro can't paste into a cell in a table. It just pastes it at the nearest out of table area. Aslo solved by downgrading to 4.17 -- 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=48200 --- Comment #3 from Todd Chester <ToddAndMargo(a)zoho.com> --- (In reply to Todd Chester from comment #2)
Word Pro can't paste into a cell in a table. It just pastes it at the nearest out of table area. Also solved by downgrading to 4.17
Scratch that. It was a corrupted line in the table -- 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=48200 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|major |normal Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #4 from Zebediah Figura <z.figura12(a)gmail.com> --- (In reply to Todd Chester from comment #3)
(In reply to Todd Chester from comment #2)
Word Pro can't paste into a cell in a table. It just pastes it at the nearest out of table area. Also solved by downgrading to 4.17
Scratch that. It was a corrupted line in the table
Okay, resolving INVALID then. -- 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=48200 Todd Chester <ToddAndMargo(a)zoho.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |--- Severity|normal |major Status|RESOLVED |UNCONFIRMED --- Comment #5 from Todd Chester <ToddAndMargo(a)zoho.com> --- (In reply to Zebediah Figura from comment #4)
(In reply to Todd Chester from comment #3)
(In reply to Todd Chester from comment #2)
Word Pro can't paste into a cell in a table. It just pastes it at the nearest out of table area. Also solved by downgrading to 4.17
Scratch that. It was a corrupted line in the table
Okay, resolving INVALID then.
Some guard dogs you are! The only invalid part was Word Pro not pasting into a table. The original complaint still holds: in Approach, the "Shell" script command no longer works in wine-common-4.20-1.fc31.noarch, but works when reverted to wine-common-4.17-1.fc31.noarch -- 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=48200 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression --- Comment #6 from Austin English <austinenglish(a)gmail.com> --- (In reply to Todd Chester from comment #5)
(In reply to Zebediah Figura from comment #4)
(In reply to Todd Chester from comment #3)
(In reply to Todd Chester from comment #2)
Word Pro can't paste into a cell in a table. It just pastes it at the nearest out of table area. Also solved by downgrading to 4.17
Scratch that. It was a corrupted line in the table
Okay, resolving INVALID then.
Some guard dogs you are!
The only invalid part was Word Pro not pasting into a table. The original complaint still holds: in Approach, the "Shell" script command no longer works in wine-common-4.20-1.fc31.noarch, but works when reverted to wine-common-4.17-1.fc31.noarch
Can you run a regression test? -- 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=48200 --- Comment #7 from Todd Chester <ToddAndMargo(a)zoho.com> --- (In reply to Austin English from comment #6)
Can you run a regression test?
I need the directions -- 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=48200 --- Comment #8 from Austin English <austinenglish(a)gmail.com> --- (In reply to Todd Chester from comment #7)
(In reply to Austin English from comment #6)
Can you run a regression test?
I need the directions
https://wiki.winehq.org/RegressionTesting -- 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=48200 --- Comment #9 from Todd Chester <ToddAndMargo(a)zoho.com> --- (In reply to Austin English from comment #8)
(In reply to Todd Chester from comment #7)
(In reply to Austin English from comment #6)
Can you run a regression test?
I need the directions
Oh good lord! That is so over my head! -- 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=48200 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |focht(a)gmx.net Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 Severity|major |normal --- Comment #10 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, is this a bug specific to Wine-Staging or just because you don't use plain Wine? Could you retest with plain Wine 5.0+? 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=48200 --- Comment #11 from Todd Chester <ToddAndMargo(a)zoho.com> --- Hi Anastasius, Fedora uses Wine Staging in its repo, so I am stuck with whatever they provide. I have also had to downgrade to 4.17 to work around this critical (to me at least) error. And I have had to freeze further updates to wine in dnf.repo Do you have a method where I can test regular wine in parallel? -T -- 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=48200 joaopa <jeremielapuree(a)yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree(a)yahoo.fr --- Comment #12 from joaopa <jeremielapuree(a)yahoo.fr> --- https://wiki.winehq.org/Fedora -- 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=48200 --- Comment #13 from Todd Chester <ToddAndMargo(a)zoho.com> --- Would it help if I were to throw together a quick example? Or would this be considered too much of a security risk? -- 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=48200 --- Comment #14 from Todd Chester <ToddAndMargo(a)zoho.com> --- (In reply to joaopa from comment #12)
Uhhhh. That is not in parallel and it destroys my RPM database. Do you have RPM's for 5.x hiding somewhere? -- 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=48200 --- Comment #15 from Todd Chester <ToddAndMargo(a)zoho.com> --- I found the following in the testing repo: https://ewr.edge.kernel.org/fedora-buffet/fedora/linux/updates/31/Everything... Maybe I could put it in a virtual machine? -- 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=48200 --- Comment #16 from Zebediah Figura <z.figura12(a)gmail.com> --- (In reply to Todd Chester from comment #13)
Would it help if I were to throw together a quick example?
If it's something that can be legally distributed, sure. -- 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=48200 --- Comment #17 from Todd Chester <ToddAndMargo(a)zoho.com> --- Created attachment 66493 --> https://bugs.winehq.org/attachment.cgi?id=66493 Test Approach file using the shell function Here you go. Use at your own risk. No rights reserved to the code. Do what you wish with it. This test Approach file gives the ability to test a shell call to /usr/bin/send-notify. The script inside the file is: .................. Sub NotifySend Dim NotifyText As Variant Dim Result As Variant NotifyText = CurrentView.Body.Text~ Box.text 'Note: FullAddress must not have any 000DH (carrage returns) in it; use 000AH (line feeds) instead ' Note: 33 is a good return Result = Shell ( "z:\usr\bin\notify-send" + " -u critical -t 0 " + NotifyText ) Msgbox "Result (33 is a good return) <" + Str (Result) + ">" End Sub ................. The script editor is accessed from Edit --> Scripts & Macros --> Show Script Editor -- 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=48200 --- Comment #18 from Todd Chester <ToddAndMargo(a)zoho.com> --- Well, I got brave and make myself an ESR directory of 4.17, the upgraded to staging wine-core-5.2-1.fc31.i686 from Fedora-testing And the Approach shell is working. So still broken in 4.20 -- 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=48200 Linards <linards.liepins(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |linards.liepins(a)gmail.com --- Comment #19 from Linards <linards.liepins(a)gmail.com> --- (In reply to Todd Chester from comment #18)
Well, I got brave and make myself an ESR directory of 4.17, the upgraded to staging wine-core-5.2-1.fc31.i686 from Fedora-testing
And the Approach shell is working.
So still broken in 4.20
Can you please retest with latest wine version? -- 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=48200 --- Comment #20 from Todd Chester <ToddAndMargo(a)zoho.com> --- (In reply to Linards from comment #19)
(In reply to Todd Chester from comment #18)
Well, I got brave and make myself an ESR directory of 4.17, the upgraded to staging wine-core-5.2-1.fc31.i686 from Fedora-testing
And the Approach shell is working.
So still broken in 4.20
Can you please retest with latest wine version?
Still working as of $ rpm -qa wine-staging\* wine-staging64-6.7-1.1.x86_64 wine-staging-common-6.7-1.1.i686 -- 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=48200 --- Comment #21 from Linards <linards.liepins(a)gmail.com> --- Then I suggest to close this as RESOLVED-FIXED. -- 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=48200 Todd Chester <ToddAndMargo(a)zoho.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Resolution|--- |FIXED --- Comment #22 from Todd Chester <ToddAndMargo(a)zoho.com> --- (In reply to Linards from comment #21)
Then I suggest to close this as RESOLVED-FIXED.
I thought that was the administrators job, but I will give it a try. :-) -- 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=48200 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #23 from Zebediah Figura <z.figura12(a)gmail.com> --- Closing fixed wine-staging bugs. -- 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