[Bug 59735] New: The solution for launching Photoshop 2021
http://bugs.winehq.org/show_bug.cgi?id=59735 Bug ID: 59735 Summary: The solution for launching Photoshop 2021 Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs@list.winehq.org Reporter: jon9097@gmail.com Distribution: --- Hello. Like many others, I would be grateful if you could run Photoshop in Wine. Unfortunately, Wine in its current form does not allow this to be done. Photoshop either crashes or doesn't start at all. Many people still can't upgrade to Linux due to the lack of Photoshop support. It installs, but it doesn't work. I found a solution where you don't have to do anything at all. There is a project that allows you to launch Photoshop 2021 and it works fine. I place a critical importance, as it is important to a huge number of people. I think it can be done a long time ago. The number of people who will be grateful to you will be huge. I have been professionally involved in graphics for many years and know many people and studios who would have switched to Linux a long time ago. If you provide Photoshop support, the Linux community will grow significantly. Because Photoshop − It's the only thing that can't be replaced. Please implement the parts that are in the project, which I will link to below. This is a fork of your Wine. The fork is called bleeding-edge-local -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59735 --- Comment #1 from Konstantin <jon9097@gmail.com> --- https://github.com/PhialsBasement/wine-adobe-installers -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59735 Ken Sharp <imwellcushtymelike@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEEDINFO Severity|critical |normal Ever confirmed|0 |1 --- Comment #2 from Ken Sharp <imwellcushtymelike@gmail.com> --- Bugzilla is for reporting bugs. Do you have a bug to report? -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59735 --- Comment #3 from Konstantin <jon9097@gmail.com> --- @Ken Sharp, yes, the bug occurs when starting photoshop, and this bug has been fixed in this fork. Everything has already been done. You just need to take the fixes and add them to the main branch. Start monitoring process. libEGL warning: pci id for fd 33: 10de:2c02, driver (null) pci id for fd 34: 10de:2c02, driver (null) pci id for fd 35: 10de:2c02, driver (null) libEGL warning: egl: failed to create dri2 screen libEGL warning: pci id for fd 33: 10de:2c02, driver (null) pci id for fd 34: 10de:2c02, driver (null) pci id for fd 35: 10de:2c02, driver (null) libEGL warning: egl: failed to create dri2 screen libEGL warning: pci id for fd 33: 10de:2c02, driver (null) err: readMonitorEdidFromKey: Failed to get EDID reg key size err: DXGI: Failed to parse display metadata + colorimetry info, using blank. err: readMonitorEdidFromKey: Failed to get EDID reg key size err: DXGI: Failed to parse display metadata + colorimetry info, using blank. libEGL warning: pci id for fd 35: 10de:2c02, driver (null) pci id for fd 36: 10de:2c02, driver (null) pci id for fd 37: 10de:2c02, driver (null) libEGL warning: egl: failed to create dri2 screen libEGL warning: pci id for fd 35: 10de:2c02, driver (null) pci id for fd 36: 10de:2c02, driver (null) pci id for fd 37: 10de:2c02, driver (null) libEGL warning: egl: failed to create dri2 screen libEGL warning: pci id for fd 35: 10de:2c02, driver (null) err: readMonitorEdidFromKey: Failed to get EDID reg key size err: DXGI: Failed to parse display metadata + colorimetry info, using blank. err: readMonitorEdidFromKey: Failed to get EDID reg key size err: DXGI: Failed to parse display metadata + colorimetry info, using blank. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59735 --- Comment #4 from Konstantin <jon9097@gmail.com> --- Why can I only select "need info", "resolved" and "closed" when reporting information? You can't select "Reported" or something like that. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59735 --- Comment #5 from Austin English <austinenglish@gmail.com> --- (In reply to Konstantin from comment #4)
Why can I only select "need info", "resolved" and "closed" when reporting information? You can't select "Reported" or something like that.
Because bugzilla is for reporting problems in wine/applications under wine, not for sharing links to github projects/forks. See https://gitlab.winehq.org/wine/wine/-/wikis/Bugs for more info. There are already >50 bug reports for Adobe Photoshop. What additional value does this one provide? It would be more helpful to have the author of the patches submit their patches upstream for inclusion (assuming that they're eligible for inclusion, i.e., not LLM generated, have conformance tests, etc.). -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59735 --- Comment #6 from Konstantin <jon9097@gmail.com> --- I'm not a developer. You wrote yourself that you have many requests for a solution to this problem. I showed you the place where it has already been solved, you just need to take from there what solves the problem of photoshop. I have shown you the problem and its solution. What's the problem with adding the fixes that are there to the main branch? I have found a solution to a problem that has not been solved for many years. This is a ready-made solution that just needs to be included in the main 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.
http://bugs.winehq.org/show_bug.cgi?id=59735 Olivier F. R. Dierick <o.dierick@piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick@piezo-forte.be --- Comment #7 from Olivier F. R. Dierick <o.dierick@piezo-forte.be> --- Hello, Adobe Photoshop 2021 is already reported as running in the AppDB [1]. It's the installation that seems to not work. If you want to tell Photoshop users about a fork that allows installing the application without using a Windows virtual machine/dual boot, then you're at the wrong place. The right place is the comment section of the AppDB, where users go to search for their application and explanations how to run it. As for taking code from other people without their knowledge or consent: It's not only morally but also possibly legally, wrong. We don't do that. The authors of the fork didn't bother to contribute to Wine so, they either don't want their code to be upstreamed or they consider it a hack not ready for inclusion. Better ask them about it. [1] https://appdb.winehq.org/objectManager.php?sClass=application&iId=17 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.
http://bugs.winehq.org/show_bug.cgi?id=59735 --- Comment #8 from Alexandre Julliard <julliard@winehq.org> --- Actually, they did submit it, and we've been working with them to integrate the changes correctly, cf. https://gitlab.winehq.org/wine/wine/-/merge_requests/10025 -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59735 --- Comment #9 from Nikolay Sivov <bunglehead@gmail.com> --- (In reply to Alexandre Julliard from comment #8)
Actually, they did submit it, and we've been working with them to integrate the changes correctly, cf. https://gitlab.winehq.org/wine/wine/-/merge_requests/10025
We can really close this MR at this point. There is nothing left to be merged. For the linked github repo - there is 3 patches over 11.10, once of them won't matter. The other two very likely never submitted. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59735 Ken Sharp <imwellcushtymelike@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Resolution|--- |INVALID --- Comment #10 from Ken Sharp <imwellcushtymelike@gmail.com> --- As everyone has explained, there are bug reports and this is not one of them. If you have a new bug please open a new bug report. https://gitlab.winehq.org/wine/wine/-/wikis/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