[Bug 56114] New: winecfg allows a cdrom drive path to be inside of the WINEPREFIX
https://bugs.winehq.org/show_bug.cgi?id=56114 Bug ID: 56114 Summary: winecfg allows a cdrom drive path to be inside of the WINEPREFIX Product: Wine Version: 9.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cedric.dewijs(a)eclipso.eu Distribution: --- To reproduce: $ rm -rf ~/wine-tmp/ $ mkdir ~/wine-tmp $ export WINEPREFIX=~/wine-tmp $ cd ~/wine-tmp $ mkdir cd $ touch cd/file.txt $ winecfg choose drives -> add -> D: -> OK now a new drive is added with / as the path copy and paste this into the path and click ok: ~/wine-tmp/cd/ $ ls ~/wine-tmp/dosdevices/d\: /home/cedric/wine-tmp/dosdevices/d: $ cd ~/wine-tmp/dosdevices/d\: bash: cd: /home/cedric/wine-tmp/dosdevices/d:: No such file or directory Wine should refuse to accept a path for the CD when it's in the WINEPREFIX Bonus points for presenting a prompt to the user explaining the limitation. See this bug for more discussion on the subject: https://bugs.winehq.org/show_bug.cgi?id=56091 $ wine --version wine-9.0-rc3 -- 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=56114 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4(a)web.de --- Comment #1 from Fabian Maurer <dark.shadow4(a)web.de> --- It works just fine when using a ~ (tilde). -- 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=56114 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #2 from Alexandre Julliard <julliard(a)winehq.org> --- Please use the forum for support questions. -- 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=56114 --- Comment #3 from Cedric <cedric.dewijs(a)eclipso.eu> --- (In reply to Alexandre Julliard from comment #2)
Please use the forum for support questions.
This is not a support question. I was told wine should not use a directory inside WINEPREFIX as source for an emulated CD drive in bug 56091 (linked) " You can't enter the WINEPREFIX directory from the Unix browser. That's on purpose, to prevent infinite loops and duplicate files. " If the Unix browser can't enter the WINEPREFIX directory on purpose, it's logical it's also not suppose to accept a location inside the WINEPREFIX when manually typed. Following that logic, it's a bug in winecfg that it's possible to manually specify a location as source for a CD drive inside the WINEPREFIX I could be wrong however. -- 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=56114 --- Comment #4 from Alexandre Julliard <julliard(a)winehq.org> --- (In reply to Cedric from comment #3)
(In reply to Alexandre Julliard from comment #2)
Please use the forum for support questions.
This is not a support question. I was told wine should not use a directory inside WINEPREFIX as source for an emulated CD drive in bug 56091 (linked)
That's not what I said.
If the Unix browser can't enter the WINEPREFIX directory on purpose, it's logical it's also not suppose to accept a location inside the WINEPREFIX when manually typed.
No, that's unrelated.
Following that logic, it's a bug in winecfg that it's possible to manually specify a location as source for a CD drive inside the WINEPREFIX
That's not a bug. Please stop assuming that Wine needs fixing just because you see some behavior that you don't understand, ask for an explanation on the forum instead. -- 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=56114 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick(a)piezo-forte.be --- Comment #5 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, I have to agree with the user on that one. I can create a D: drive pointing to the absolute path of the WINEPREFIX directory itself by typing it in the input field, and I can run notepad with: $ wine start 'D:\drive_c\windows\notepad.exe' The same thing can't be achieved using the Unix browser dialog. You say that it's on purpose, to avoid a potential recursion issue. If that recursion issue could only affect the Unix browser dialog itself, and using the WINEPREFIX as a drive path is not at risk, then that Unix browser 'feature' just hinders the selection of the drive path for an unrelated reason, and it should be reworked with a proper fix that would allow selecting a path in the WINEPREFIX while avoiding recursion issues. That would be a valid issue. If using the WINEPREFIX as a drive path may also result in that recursion issue you want to avoid, then such a path should also be rejected when manually typed into the field, not just in the Unix browser dialog, otherwise the purpose of the Unix browser 'feature' is defeated. That would also be a valid issue. So, please, clarify: Does the recursion issue that is prevented by the 'feature' only affects the Unix browser dialog itself, or does it potentially affects the use of the WINEPREFIX as the drive path? 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=56114 --- Comment #6 from Alexandre Julliard <julliard(a)winehq.org> --- (In reply to Olivier F. R. Dierick from comment #5)
So, please, clarify: Does the recursion issue that is prevented by the 'feature' only affects the Unix browser dialog itself, or does it potentially affects the use of the WINEPREFIX as the drive path?
It's only the browser that prevents entering WINEPREFIX, for unrelated reasons. It's not a problem to put the mount point inside the prefix if you want to. It's also not worth investing efforts into improving this, because people shouldn't need to edit drives manually, or put mount points in unusual places. The right way is to use the appropriate tool in the Linux desktop (e.g. gnome-disk-image-mounter) to mount the iso and let Wine create the drives automatically. -- 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=56114 --- Comment #7 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, Thanks for the clarification. 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=56114 --- Comment #8 from Cedric <cedric.dewijs(a)eclipso.eu> --- (In reply to Olivier F. R. Dierick from comment #7)
Hello,
Thanks for the clarification.
Regards.
(In reply to Alexandre Julliard from comment #6)
(In reply to Olivier F. R. Dierick from comment #5)
So, please, clarify: Does the recursion issue that is prevented by the 'feature' only affects the Unix browser dialog itself, or does it potentially affects the use of the WINEPREFIX as the drive path?
It's only the browser that prevents entering WINEPREFIX, for unrelated reasons. It's not a problem to put the mount point inside the prefix if you want to.
Ok. That makes this bug invalid.
It's also not worth investing efforts into improving this, because people shouldn't need to edit drives manually, or put mount points in unusual places. The right way is to use the appropriate tool in the Linux desktop (e.g. gnome-disk-image-mounter) to mount the iso and let Wine create the drives automatically.
If people shouldn't need to edit drives manually, why give them the option to do so in the first place? Following that logic, the proper fix would be to remove the browser entirely, and to make the manual field read-only. Or bug 56091 can be reopened, so one day the browser can work fully. -- 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=56114 --- Comment #9 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, (In reply to Cedric from comment #8)
If people shouldn't need to edit drives manually, why give them the option to do so in the first place?
He said "shouldn't need to", not "must not". Some cases require people to edit drives manually (when setting a drive from a normal directory).
Following that logic, the proper fix would be to remove the browser entirely, and to make the manual field read-only.
That won't be a proper fix due to what I said above. Please, stop pretending to follow other people's logic, when you actually just made-up that broken logic on purpose to make a valid point. I despise willful misinterpretation. 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=56114 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|dark.shadow4(a)web.de | -- 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=56114 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #10 from Austin English <austinenglish(a)gmail.com> --- Closing. -- 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