https://bugs.winehq.org/show_bug.cgi?id=49994
Bug ID: 49994
Summary: Starcraft2 shows blank screen: DVI-D out of range
89.5Khz, 60Hz
Product: Wine
Version: 5.18
Hardware: x86-64
URL: https://www.blizzard.com/en-us/download/
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: cedric.dewijs(a)eclipso.eu
Distribution: ArchLinux
Summary
Starcraft2 shows blank screen: DVI-D out of range 89.5Khz, 60Hz
Prepare wine:
$ rm -rf ~/.wine/
$ wineserver -k
$ wineboot
https://www.blizzard.com/en-us/download/https://www.blizzard.com/download/confirmation?platform=windows&locale=en_U…
$ sha256sum StarCraft-II-Setup.exe
4e1afeba8130a9665b402f9550e86bca6c78022ff2b6d83d2813be13ac553d55
StarCraft-II-Setup.exe
wine StarCraft-II-Setup.exe
Choose English (US), continue
Install location (default), continue
Now the login screen appears, enter email and password, login
Now the Starcraft 2 installer starts for real. Choose the defaults, and start
install.
Now the scan for games reports no games found. press close
Now Starcraft2 is downloading 27GB
Press play when it has downloaded enough. Now my monitor goes blank
(unsupported video mode, and I hear the Protoss intro video.)
Press alt-f4. Now the desktop re-appears.
A retest with another monitor shows the same thing with this message on the
screen: DVI-D out of range 89.5Khz, 60Hz
My video card:
$ lspci -vvv
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Lexa
PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] (rev c7) (prog-if 00 [VGA
controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8a90
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 36
NUMA node: 0
Region 0: Memory at c0000000 (64-bit, prefetchable) [size=256M]
Region 2: Memory at d0000000 (64-bit, prefetchable) [size=2M]
Region 4: I/O ports at e000 [size=256]
Region 5: Memory at fea00000 (32-bit, non-prefetchable) [size=256K]
Expansion ROM at 000c0000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: amdgpu
Kernel modules: amdgpu
My versions
$ wine --version
wine-5.18 (Staging)
$ pacman -Q wine
wine-staging 5.18-1
uname -a
Linux cedric-p4 5.8.14-arch1-1 #1 SMP PREEMPT Wed, 07 Oct 2020 23:59:46 +0000
x86_64 GNU/Linux
--
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=32128
Bug #: 32128
Summary: Incorrect links in the mailing list archives
Product: WineHQ.org
Version: unspecified
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: www-unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fgouget(a)codeweavers.com
Classification: Unclassified
Email addresses such as wineconf(a)winehq.org are being converted into links to
the wine-devel mailing list (which happens to be the mailing list where the
email was posted).
See for instance:
http://www.winehq.org/pipermail/wine-devel/2012-November/097669.html
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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=37815
Bug ID: 37815
Summary: onigirl
Product: Wine
Version: 1.7.0
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: windowscodecs
Assignee: wine-bugs(a)winehq.org
Reporter: Crazy_TrickzZzz(a)yahoo.com
Distribution: ---
Created attachment 50364
--> https://bugs.winehq.org/attachment.cgi?id=50364
i dont understand it runs so smothly but when i log it it just crashes
i cant play the game right after i log into it
--
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=46992
Bug ID: 46992
Summary: Battle.net won't start after installing.
Product: Wine
Version: 4.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bellucc.e(a)gmail.com
Distribution: ---
Created attachment 64157
--> https://bugs.winehq.org/attachment.cgi?id=64157
the error appearing after few secs
When i launch battle.net the first window (login window) appears but i can do
nothing but writing my credentials. The loading animation (some rays rotating,
i guess it's the connect wait) keep rotating. After few seconds the error
appears.
--
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=19386
Summary: Please provide single login for all websites of
winehq.org portal.
Product: WineHQ.org
Version: unspecified
Platform: PC
OS/Version: All
Status: UNCONFIRMED
Severity: major
Priority: P5
Component: www-unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: yurikoles(a)gmail.com
For every website users must create new account. I think it's really annoying.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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=47894
Bug ID: 47894
Summary: mfreadwrite error dialog causes the user32:winstation
tests to fail
Product: Wine
Version: 4.17
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: mfplat
Assignee: wine-bugs(a)winehq.org
Reporter: sven.wine(a)gmail.com
Distribution: ---
When mfreadwrite is not present, a dialog appears, which seems to cause the
user32:winstation tests to fail:
https://test.winehq.org/data/b360cd67e8f7f8c01f09457bacb032fd4a248d0a/2008_…
Sometimes it disappears just in time, in which case the tests succeed:
https://test.winehq.org/data/b360cd67e8f7f8c01f09457bacb032fd4a248d0a/2008_…
I'm not sure whether to file this under user32 or mfreadwrite.
--
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=47163
Bug ID: 47163
Summary: Photoshop 6 not working on Wine Ubuntu
Product: Wine
Version: 4.0
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ichbinleider1(a)web.de
Distribution: ---
Created attachment 64396
--> https://bugs.winehq.org/attachment.cgi?id=64396
Description of Bug Report, Photoshop 6 not working on Wine Ubuntu
Photoshop 6 not working on Wine Ubuntu, not even starting up! Log file 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=49767
Bug ID: 49767
Summary: All resources deleted during update Logos Bible
Software
Product: Wine
Version: 5.16
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: johnpgoodman(a)gmail.com
Distribution: ---
Created attachment 68072
--> https://bugs.winehq.org/attachment.cgi?id=68072
Console output from during update
Updates result in data wipe.
Logos stores all resources, eg. ebooks, videos etc in a subdir like
drive_c/users/$username/Local Settings/Application
Data/Logos/Data/$uniqueid/ResourceManager/
When an update to Logos Bible Software becomes available there is a
notification in the app. The update will usually install ok however on wine the
Resources are all wiped. The user is now stuck with a massive download eg.
40gb+. On Windows the resources are always still there after an update.
It's as if the msi somehow overwrites the directory rather than merging with
it?
I've attached a console log updating from 8.15.0.0004 to 8.16.0.0002 - in this
case the update also did not relaunch the newly updated app but simply kept
running. At this point I checked and confirmed all resources were wiped. Once
quit and reloaded it was clear the update had completed but it began to
download everything again.
--
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=45151
Bug ID: 45151
Summary: patches: 'git send-email' through Zoho SMTP causes
patch queue to go berserk
Product: WineHQ.org
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kyle.auble(a)zoho.com
Distribution: ---
Created attachment 61339
--> https://bugs.winehq.org/attachment.cgi?id=61339
I'm starting to get embarrassed
So I'll probably just start using my Gmail account for submissions to Wine
anyways, but I've been having problems sending patches through Zoho.
I've followed the instructions on
https://wiki.winehq.org/Submitting_Patches
and when running 'git send-email', there are no issues on my computer. I'm
prompted for my SMTP password, git does its thing, and I've received an "OK /
250" return code every time.
Small, one-off patches seem to make it through fine, but beyond that, then the
wine-devel or the patch-list doesn't get them. Furthermore, Zoho delivers me a
message saying that wine-devel can't be reached and that they'll keep retrying
the delivery. And they do, which is where I think part of the problem might be
coming from.
---
In the first case, I tried sending a series of 7 patches. The first patch was a
very short text change, the next five were larger batch substitutions on
different strings, and the last one was a relatively short binary patch to
delete five images.
The first patch made it through pretty quickly, but the rest never showed up.
To make things more confusing, I received Zoho notices that patches 5-7
couldn't reach the list and would be retried, but nothing about 2-4. Then a few
hours later, the mailing list confirmed that patch 7 had made it through fine,
but no sign of the middle 5.
Since I had no notification from wine-devel or Zoho for patches 2-4, I tried
resending patch 2 a couple times. Everything besides patches 1 & 7 seemed to
just be falling into a black-hole though... until the next morning, every last
patch I had sent (including the repeats of patch 2) was on both wine-devel and
the patch-list, showing the original send dates, as if they had been there all
along.
---
In the second case, I had three large binary patches for deleting old images
that have since been moved onto the wiki. I tried sending them one-at-a-time,
'git send-email' gave me an OK / 250, and they never made it to the list. This
time Zoho sent me a notice saying that there was a fatal error with
wine-devel's address, specifically
"ResponseCode 421, Read timed out"
The notice said they would keep retrying the delivery for 4 days, but then I
didn't hear anything... until all of a sudden, today I see this on the patch
queue (screenshot attached). I know I didn't resend either of these patches,
much less 17 times. Weirdly enough, the wine-devel mailing list seems to
understand what's going on a little better and only shows the message once.
---
The one other pattern I have noticed is that it almost seems like the mailing
list is clocking out for business hours. The first was on a Wed evening, but it
wasn't until the next morning that everything suddenly appeared. The second
time, I tried sending in my patches before Friday evening, but there was still
no sign of them when I checked yesterday (Sun). Sure enough, they're all there
today though.
TL/DR: I know very little about how mail protocols work, and it could very well
be on my mail service's end, but it almost seems like the mailing-list is
actually receiving the emails. It then puts them in quarantine outside of
normal work-hours, which doesn't seem like a problem in isolation. Somehow the
sender is getting "delivery failed" codes though, and I only seem to get
delivery receipts sporadically, despite turning on delivery receipts in my
pipermail settings for wine-devel.
--
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.