[Bug 46385] New: TreePad X Enterprise 12GB (single user) v7.17.0: Unable to copy and paste to/from TreePad
https://bugs.winehq.org/show_bug.cgi?id=46385
Bug ID: 46385 Summary: TreePad X Enterprise 12GB (single user) v7.17.0: Unable to copy and paste to/from TreePad Product: Wine Version: 4.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: winebugrpt18356@fastmail.jp Distribution: ---
Created attachment 63144 --> https://bugs.winehq.org/attachment.cgi?id=63144 TreePad database
Unable to copy and paste text to or from TreePad. This is a regression as the functionality worked in WINE v3.0.4.
Reference bug #46352 for instructions on installing TreePad.
I'm providing a TreePad database for testing purposes.
01) Create a folder named "coding_tips".
02) Unzip the file into the folder created in step 01.
03) Open TreePad and simultaneously depress CTRL and the letter O keys to start the database open prompt.
04) Locate and select the folder created in step 01.
https://bugs.winehq.org/show_bug.cgi?id=46385
Van winebugrpt18356@fastmail.jp changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Debian
https://bugs.winehq.org/show_bug.cgi?id=46385
Van winebugrpt18356@fastmail.jp changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winebugrpt18356@fastmail.jp
https://bugs.winehq.org/show_bug.cgi?id=46385
Van winebugrpt18356@fastmail.jp changed:
What |Removed |Added ---------------------------------------------------------------------------- CC|winebugrpt18356@fastmail.jp |
https://bugs.winehq.org/show_bug.cgi?id=46385
Van winebugrpt18356@fastmail.jp changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winebugrpt18356@fastmail.jp
https://bugs.winehq.org/show_bug.cgi?id=46385
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression
https://bugs.winehq.org/show_bug.cgi?id=46385
--- Comment #1 from Alexandre Julliard julliard@winehq.org --- Copy/paste works fine here as far as I can tell. Could you please describe exactly what you are doing that's not working?
https://bugs.winehq.org/show_bug.cgi?id=46385
--- Comment #2 from Van winebugrpt18356@fastmail.jp --- I copy text from an article in a TreePad database and attempt to paste the text in a text editor. The paste doesn't work.
I copy text from a text editor and attempt to paste the text in an article in a TreePad database. The paste doesn't work.
About a couple of hours ago, I attempted to copy a link from the address field of a browser into an article in a TreePad database. The paste didn't work.
Could it possibly be due to the fact that I'm using TreePad in a WINE prefix? If so, that also worked prior to WINE v4.
https://bugs.winehq.org/show_bug.cgi?id=46385
--- Comment #3 from Alexandre Julliard julliard@winehq.org --- Which article? In which text editor? Windows or Linux? What do you mean by WINE prefix?
Please give step by step reproduction instructions.
https://bugs.winehq.org/show_bug.cgi?id=46385
--- Comment #4 from Van winebugrpt18356@fastmail.jp --- (In reply to Alexandre Julliard from comment #3)
Which article? In which text editor? Windows or Linux? What do you mean by WINE prefix?
Please give step by step reproduction instructions.
The issue is present, on my end anyway, in any article of any TreePad database I use as well as any text editor I use...Bluefish, Geany, Leafpad, or Medit. As I stated in my last reply, the issue also occurred when attempting to copy a link from a browser into a TreePad database article.
I only use Linux.
So basically, again on my end anyway, I'm only able to copy and paste within TreePad database articles and tree nodes and the issue became apparent when WINE was upgraded to version 4.x under Debian Unstable.
Wine Prefix: https://wiki.winehq.org/FAQ#Wineprefixes
I'll install TreePad outside of a WINE prefix on my end and see if using the prefix might be part of the issue. Again though, using a prefix under WINE 3.x didn't cause copy and paste issues.
https://bugs.winehq.org/show_bug.cgi?id=46385
--- Comment #5 from Van winebugrpt18356@fastmail.jp --- Okay, I installed TreePad X Enterprise (single user) 12 GB v7.17.0 in a regular WINE environment and the copy and paste issue does not exit. So, there appears to be an issue with copying and pasting outside of TreePad within a WINE prefix under WINE 4.x.
I will next test creating a new WINE prefix for TreePad, install a new instance of TreePad into the new WINE prefix, and test copying and pasting from there to verify whether or not there's an issue with copying and pasting within a WINE prefix in WINE 4.x.
https://bugs.winehq.org/show_bug.cgi?id=46385
--- Comment #6 from Van winebugrpt18356@fastmail.jp --- I believe there's an issue with using WINE prefixes under WINE 4x that limits copying and pasting only within TreePad. To recreate:
01) Start with a clean WINE prefix or bottle; i.e. a clean .wine folder under your home folder.
02) From terminal or the command line, enter the following command:
cp .wine .wine-treepad
03) Install TreePad XSU Enterprise 12GB (single user) v7.17.0 into .wine-treepad using the steps outlined in bug #46352.
04) Issue the following command from terminal or the command line to start TreePad:
WINEPREFIX="/home/[user]/.wine-treepad" wine start 'C:\Program Files (x86)\TreePadXSU\TreePadXEnterprise.exe'
05) Open an existing TreePad database, or create a new one, and attempt to copy and paste text in a TreePad database article (right window) to or from another application in Linux; e.g. text editor, word processor, browser, etc.
The copy and paste should fail when attempting to do so outside of TreePad.
https://bugs.winehq.org/show_bug.cgi?id=46385
--- Comment #7 from Van winebugrpt18356@fastmail.jp --- Correction to step #2 above. The command should be:
cp -r .wine .wine-treepad
https://bugs.winehq.org/show_bug.cgi?id=46385
--- Comment #8 from Alexandre Julliard julliard@winehq.org --- The name of the prefix directory shouldn't make any difference, and there shouldn't be any reason to copy prefixes around.
Anyway, even replicating your instructions, everything works fine here. If things work for you in a plain .wine prefix too, I suspect something went wrong with your prefix manipulations.
https://bugs.winehq.org/show_bug.cgi?id=46385
--- Comment #9 from Van winebugrpt18356@fastmail.jp --- (In reply to Alexandre Julliard from comment #8)
The name of the prefix directory shouldn't make any difference, and there shouldn't be any reason to copy prefixes around.
Anyway, even replicating your instructions, everything works fine here. If things work for you in a plain .wine prefix too, I suspect something went wrong with your prefix manipulations.
You asked for step-by-step reproduction steps.
I waited to reply because I checked and there was an upgrade in the Debian Unstable repo that hadn't trickled down to the mirrors yet. I just upgraded a few minutes ago and the problem still exists.
You say you are not able to replicate the issue on your end. Are you testing in an up-to-date Debian Unstable?
https://bugs.winehq.org/show_bug.cgi?id=46385
--- Comment #10 from Alexandre Julliard julliard@winehq.org --- (In reply to Van from comment #9)
(In reply to Alexandre Julliard from comment #8)
The name of the prefix directory shouldn't make any difference, and there shouldn't be any reason to copy prefixes around.
Anyway, even replicating your instructions, everything works fine here. If things work for you in a plain .wine prefix too, I suspect something went wrong with your prefix manipulations.
You asked for step-by-step reproduction steps.
Yes, and following them, everything works fine for me. I also don't see any reason why changing the prefix name would make a difference. There must be something else that's different with your setup. Please get a WINEDEBUG=clipboard trace.
I waited to reply because I checked and there was an upgrade in the Debian Unstable repo that hadn't trickled down to the mirrors yet. I just upgraded a few minutes ago and the problem still exists.
You say you are not able to replicate the issue on your end. Are you testing in an up-to-date Debian Unstable?
Debian testing, but that shouldn't make any difference either.
https://bugs.winehq.org/show_bug.cgi?id=46385
--- Comment #11 from Van winebugrpt18356@fastmail.jp --- (In reply to Alexandre Julliard from comment #8)
I suspect something went wrong with your prefix manipulations.
If that were true, wouldn't there have been an issue under WINE v3.0.4?
(In reply to Alexandre Julliard from comment #10)
There must be something else that's different with your setup. Please get a WINEDEBUG=clipboard trace.
Could be. I'm beginning to wonder if the issue might be caused by something else. That's why I asked what you were testing under on your end. I've noticed updates to the apparmor package lately. However, I'm not sure exactly what apparmor does or how it works.
I'll try the WINEDEBUG trace later. I'm not currently using Debian Unstable.
Debian testing, but that shouldn't make any difference either.
It makes a huge difference. Debian Testing and Debian Unstable are very different; different versions of packages and sometimes one contains packages that the other doesn't.
WINE v4.0-rc4 isn't even currently in the Debian Testing repos. I've stated that I'm using Debian Unstable, so I'm dumbfounded why you would even test under Debian Testing and assume that if everything is okay there, it should be okay on my end.
https://bugs.winehq.org/show_bug.cgi?id=46385
Van winebugrpt18356@fastmail.jp changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |NOTOURBUG Status|UNCONFIRMED |RESOLVED
--- Comment #12 from Van winebugrpt18356@fastmail.jp --- Alexandre,
I owe you an apology. I didn't report exactly what I was doing basically because I didn't think it mattered. In hindsight, I also don't think you would have wanted to install, configure, and run the Openbox window manager and obmenu.
I've found the issue, but I'm not sure why it is happening now. What I'm doing has always worked fine in the past.
I usually run TreePad via WINE from an obmenu (Openbox menu) commmand as follows:
terminator --command="WINEPREFIX="$HOME/.wine-treepad" wine start 'C:\Program Files (x86)\TreePadXSU\TreePadXEnterprise.exe'"
Basically what the above command does is open terminator (terminal emulator) and automatically run the command to startup TreePad using a specific WINE prefix.
I manually started TreePad from the command line while using the WINEDEBUG command as you suggested and that's when I noticed that I could copy and paste fine. The light bulb went off so to speak.
I've tested twice and there's something about my obmenu command to start TreePad that results in only being able to copy and paste within TreePad.
So, I don't think there's an issue with WINE. I need to figure out another way to run TreePad from obmenu.
https://bugs.winehq.org/show_bug.cgi?id=46385
--- Comment #13 from Van winebugrpt18356@fastmail.jp --- Experimented a bit more and found out what the real culprit was: using "wine start" instead of "wine". I remember changing from "wine" to "wine start" awhile ago, something I read about it being safer I think. Anyway, it's worked ever since I began using it up until WINE v4.x.
More info on "wine start":
https://wiki.winehq.org/Wine_User%27s_Guide#Using_wine_start
https://bugs.winehq.org/show_bug.cgi?id=46385
Van winebugrpt18356@fastmail.jp changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|NOTOURBUG |FIXED
--- Comment #14 from Van winebugrpt18356@fastmail.jp --- I forgot to come back and update this bug. It was resolved with a newer update, but unfortunately, I don't remember which one.
https://bugs.winehq.org/show_bug.cgi?id=46385
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |NOTOURBUG CC| |z.figura12@gmail.com Status|RESOLVED |CLOSED
--- Comment #15 from Zebediah Figura z.figura12@gmail.com --- (In reply to Van from comment #14)
I forgot to come back and update this bug. It was resolved with a newer update, but unfortunately, I don't remember which one.
-
wine-bugs＠winehq.org