[Bug 57092] New: Battle.net Launcher has trouble with winbind and malloc
https://bugs.winehq.org/show_bug.cgi?id=57092 Bug ID: 57092 Summary: Battle.net Launcher has trouble with winbind and malloc Product: Wine Version: 5.0.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: version Assignee: wine-bugs(a)winehq.org Reporter: jepetersen(a)utexas.edu Distribution: --- Created attachment 76970 --> https://bugs.winehq.org/attachment.cgi?id=76970 backtrace file I thought I'd launch my battle.net version of d3 resurrected for the new ladder, since Sony temp banned my PSN account for no reason whatsoever. These companies don't understand that people actually want to use the products they pay for. I own it on two different platforms, and I can't play it on either... This country is outrageously frustrating. People just want to leave nowadays. The problem is that when you launch the launcher, the login screen pops up, but the button to submit your login information is bugged out. At first, it looked like a winbind error, but then I installed winbind/samba, and now it's some sort of malloc error. The backtrace is attached. -- 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=57092 --- Comment #1 from Austin English <austinenglish(a)gmail.com> ---
Wine build: wine-5.0.3 (Debian 5.0.3-3)
That is several years old, try with 9.x.
0x020100e1 EntryPoint+0xffffffff in libcef: int $3
Try 'winetricks corefonts'. -- 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=57092 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download Component|version |-unknown -- 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=57092 --- Comment #2 from jepetersen(a)utexas.edu --- Bullseye was released in the Spring of 2022. What ever happened to LTS support? Almost all Wine users are Debian users. Nobody wants to have to install all those dependencies from source -- there are at least 50 of them, both amd64 and i386. Basically, you're telling me that Bullseye is useless for gaming, unless it's native linux. I find it hard to believe that Wine, a project that has been around for well over a decade just jumped from version 5.x to 9.x. Version number conventions don't tend to jump up so quickly, in my experience. Perhaps I should rephrase my question, as I am sure I am not the only Debian user on the planet with similar issues. Would it be possible to get a 9.0 release in the Debian Bullseye repository, since Bullseye is a LTS release? Or, at least a workable version. I see in the Bullseye "backports" a 7.0 release. Maybe I'll try that one. I'm more married to Bullseye at the moment than you might think. Most people who work on extra large projects solo stick to the same LTS version long after LTS expires, in my experience. -- 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=57092 --- Comment #3 from jepetersen(a)utexas.edu --- (In reply to Austin English from comment #1)
Wine build: wine-5.0.3 (Debian 5.0.3-3)
That is several years old, try with 9.x.
0x020100e1 EntryPoint+0xffffffff in libcef: int $3
Try 'winetricks corefonts'.
winetricks has some serious security holes in Bullseye -- 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=57092 --- Comment #4 from Rafał Mużyło <galtgendo(a)o2.pl> ---
Almost all Wine users are Debian users.
No, most wine users aren't you. IOW that's an assertion without any evidence.
Would it be possible to get a 9.0 release in the Debian Bullseye repository, since Bullseye is a LTS release?
wine devs have no control over Debian/Ubuntu/Fedora/RedHat/etc. repositories; as their names suggest, those are *distro* repos. -- 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=57092 --- Comment #5 from jepetersen(a)utexas.edu --- (In reply to Rafał Mużyło from comment #4)
Almost all Wine users are Debian users.
No, most wine users aren't you. IOW that's an assertion without any evidence.
Would it be possible to get a 9.0 release in the Debian Bullseye repository, since Bullseye is a LTS release?
wine devs have no control over Debian/Ubuntu/Fedora/RedHat/etc. repositories; as their names suggest, those are *distro* repos.
That's right -- they're not me. I'm not millions of people. Wow, that's such a revelation. Check out the Linux market share on the itsfoss website, and you'll see that more Linux users use some variant of Debian than anything else. Quit picking a fight for no reason at all. I realize the wine developers do not control the Debian, Ubuntu, Raspian or any other Debian variant repository. Bullseye is a very common release right now that many people use, and the fact that Wine does not work very well in this particular release is very unsettling for the Linux community as a whole, in my opinion. Many people want to use Linux, exclusively, yet have one or two pieces of software which prevent them from being able to. While not a panacea, Wine is so fundamental to many users' workflows that ignoring problems in the Bullseye repositories is a mistake, in my opinion. -- 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=57092 --- Comment #6 from mata <sutupud(a)yahoo.com> --- (In reply to jepetersen from comment #2)
Bullseye was released in the Spring of 2022. What ever happened to LTS support?
August 2021 actually. At that time the most recend wine stable was at 6.0.
Almost all Wine users are Debian users. Nobody wants to have to install all those dependencies from source -- there are at least 50 of them, both amd64 and i386. Basically, you're telling me that Bullseye is useless for gaming, unless it's native linux. I find it hard to believe that Wine, a project that has been around for well over a decade just jumped from version 5.x to 9.x. Version number conventions don't tend to jump up so quickly, in my experience.
It's one major release per year (stable branch, X.0). Then deveolpment continues in the X.X branches, and after a feature freeze and several release candidates a new stable version is released. Of course that model doesn't match Debian's release model, which sticks to one major version and keeps that over its release. There's very little chance to get any bugfixes into the 5.0 branch now, much less to have it show up in debian.
Perhaps I should rephrase my question, as I am sure I am not the only Debian user on the planet with similar issues. Would it be possible to get a 9.0 release in the Debian Bullseye repository, since Bullseye is a LTS release? Or, at least a workable version. I see in the Bullseye "backports" a 7.0 release. Maybe I'll try that one. I'm more married to Bullseye at the moment than you might think. Most people who work on extra large projects solo stick to the same LTS version long after LTS expires, in my experience.
That's fine if you want stability, but if you want non-security critical bugs fixed you'll ofen feel left beind on such a model. That said, there is a winehq debian repo with newer packages, which I bet "most debian users" who want a more recent version of wine than the debian repos provide use: https://dl.winehq.org/wine-builds/debian/dists/bullseye/ -- 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=57092 --- Comment #7 from Rafał Mużyło <galtgendo(a)o2.pl> --- :sigh: No. Your chain of reasoning seems to be: most of the people *I* know, that use Linux are Debian users therefore almost all Wine users are Debian users. What I've said was: such a chain is *deeply* flawed. The other part was mostly like comment 6: wine's concept 'LTS' is significantly different than most of the standard distros, much less Debian. That's due to its development process - sometimes a few decisions made within a single year may nearly completely overhaul some of implementation details, resulting in major changes to build process, deps, etc. So best you'll get is some minor backports of fixes to the release made at the start of the year, otherwise you'll only have the most recent release...well, unless a SNAFU happens and significant regression slips into the tree, so that you need to skip that particular release - that, unfortunately happens too; fortunately though, it's relatively rare (though this year is somewhat unlucky). -- 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=57092 --- Comment #8 from Austin English <austinenglish(a)gmail.com> --- (In reply to jepetersen from comment #3)
(In reply to Austin English from comment #1)
Wine build: wine-5.0.3 (Debian 5.0.3-3)
That is several years old, try with 9.x.
0x020100e1 EntryPoint+0xffffffff in libcef: int $3
Try 'winetricks corefonts'.
winetricks has some serious security holes in Bullseye
I don't see any https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=winetricks Where are you getting that from? -- 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