http://bugs.winehq.org/show_bug.cgi?id=34446
Bug #: 34446
Summary: LANG=ru_RU.UTF-8 locale makes fonts look blurry
Product: Wine
Version: 1.7.1
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winex11.drv
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: t.artem(a)mailcity.com
Classification: Unclassified
Created attachment 45856
--> http://bugs.winehq.org/attachment.cgi?id=45856
en_US.UTF-8 screenshot
I will now attach two screenshots showing the same application running with
en_US.UTF-8 locale
and
ru_RU.UTF-8 locale
English looks fine, Russian looks blurry and very unpleasant.
--
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=42305
Bug ID: 42305
Summary: Microsoft money 2000: the mouse click does not select
the good line
Product: Wine
Version: 2.0-rc6
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dobbyspam(a)gmail.com
Distribution: ---
When entering an expense / recessed, in the drop down menu to the insertion of
the categories, at the click of the mouse select the right item, but when you
release the mouse button, the selected item is the second bottom.
--
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=23493
Summary: Safari, when installed with quiet mode, refuses to run
Product: Wine
Version: 1.2-rc6
Platform: x86
URL: http://www.apple.com/safari
OS/Version: Linux
Status: NEW
Keywords: download, Installer
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
Installing safari normally works fine.
Installing it with silent mode (wine SafariSetup.exe /qn) reports success for
the installer, but trying to run it fails with a messagebox:
Safari can't open.
Your copy of Safari is missing important software resources. Please reinstall
Safari.
OK
terminal shows:
fixme:actctx:parse_depend_manifests Could not find dependent assembly
L"Microsoft.VC80.CRT" (8.0.50727.4053)
fixme:msvcrt:_controlfp_s ((nil) 65536 196608) semi-stub
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
--
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.
http://bugs.winehq.org/show_bug.cgi?id=33760
Bug #: 33760
Summary: Jagged edges on most text and art in the Touhou 14
demo
Product: Wine
Version: unspecified
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: murela_alba(a)abv.bg
Classification: Unclassified
Created attachment 44705
--> http://bugs.winehq.org/attachment.cgi?id=44705
windows 7 main menu 960x720
When running the "Touhou 14 ~ Double Dealing Character" demo (ver 0.01a) on any
resolution other than the highest (1280x960), pretty much all text displays
varying degrees of aliasing. Same goes for the edges of all the 2D art and UI
elements from the loading screen, to the main menu, to the game proper. Here's
the title screen on windows 7 in 960x720 (windowed).
--
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=37010
Bug ID: 37010
Summary: DYMO Stamps "Unable to connect to postage transaction
server" with wine-mono
Product: Wine
Version: 1.7.23
Hardware: x86
URL: http://sites.dymo.com/Promotions/Pages/DYMOStamps.aspx
?locale=enUS
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: mscoree
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Depends on: 31686
Follow up to bug 31687.
You'll need native gdiplus for bug 31686. Optionally, apply
https://source.winehq.org/patches/data/105843.
The app installs fine, and with native gdiplus, starts up. But when you try to
login, the application cannot connect to the server.
Terminal shows one mscoree fixme:
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"configSections"
in state 2
With native dotnet20, it will attempt to connect, then fails with 'This account
is not active'. Trying to login via the website shows the same problem, so
that's okay. But wine-mono should fail the same way.
I'm using an archived installer:
austin@aw25 ~/oldbugs/31687 $ sha1sum DYMOstampsWebSetup.exe
6f96fbdc9806effa499edba7e89329534b5901a7 DYMOstampsWebSetup.exe
austin@aw25 ~/oldbugs/31687 $ du -h DYMOstampsWebSetup.exe
3.5M DYMOstampsWebSetup.exe
the current version of the program appears to have other .Net/Mono issues
--
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=31687
Bug #: 31687
Summary: DYMO Stamps can't connect to its server
Product: Wine
Version: 1.5.12
Platform: x86
URL: http://sites.dymo.com/Promotions/Pages/DYMOStamps.aspx
?locale=enUS
OS/Version: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
Depends on: 31685, 31686
Classification: Unclassified
Created attachment 41656
--> http://bugs.winehq.org/attachment.cgi?id=41656
WINEDEBUG=crypt,chain,context,secur32
Install the app. You'll need native gdiplus for bug 31686.
After that, you can get native hid, for bug 31685. I also installed dotnet20,
to verify that it wasn't a mscoree fixme to blame, but the problem happens
either way.
Start it up, and it asks for your credentials. Put them in, and click next.
That gives an error:
The remote certificate is invalid according to the validation procedure.
terminal output doesn't show much relevant. Tried native wininet/winhttp, which
then in turns shows a few fixme's for crypt32/secur32/winsock.
If you add in native crypt32, you get:
Attempted to read or write protected memory. This is often an indication that
other memory is corrupt.
and with native secur32 as well:
The requested security package is not supported.
Not sure what to try next. The initial problem seems to indicate crypt32 or
secur32, so hopefully this log will help:
WINEDEBUG=crypt,chain,context,secur32
--
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=39350
Bug ID: 39350
Summary: Alone in the Dark: The New Nightmare (GOG.com) hangs
on start when WRITECOPY enabled
Product: Wine-staging
Version: unspecified
Hardware: x86
URL: http://www.gog.com/game/alone_in_the_dark_the_new_nigh
tmare
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: michael(a)fds-team.de, sebastian(a)fds-team.de
Distribution: ---
I have this problem with the GOG.com version of the game, but can't reproduce
it with the original demo version.
After starting the game with alone4.exe, it switches screen resolution then
hangs with an empty black screen and 100% CPU usage.
Plain terminal output doesn't show anything.
The game starts properly when STAGING_WRITECOPY variable is unset.
wine-1.7.51-225-g3966aff
Fedora 22 32-bit
--
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=43234
Bug ID: 43234
Summary: Allow users to show all full logs
Product: Wine-Testbot
Version: unspecified
Hardware: Other
OS: other
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: z.figura12(a)gmail.com
Currently it's possible to expand one log at a time to show not only the
failing lines but also the trace() output. It would be nice if we had a way to
see them all at once, though. Of course the user does get the full results
e-mailed to them, but the e-mail can take a while to go through, and also it
might be good if other people can get the full logs of a test they didn't run
(e.g. because it was linked to by the user.)
--
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=41723
Bug ID: 41723
Summary: Install ucrtbase.dll on at least one of the machines
Product: Wine-Testbot
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: piotr.caban(a)gmail.com
Distribution: ---
We have tests for ucrtbase.dll in wine but currently they are never run on
testbot. It would be nice to install the dll on at least one of the machines.
--
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=39487
Bug ID: 39487
Summary: Make step dependencies more flexible
Product: Wine-Testbot
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
The TestBot jobs are split into steps and tasks.
* The steps are numbered and must be executed in order. Each step has an
associated file.
* Each step has one or more tasks which can all be run in parallel.
Typically the first step is the build step associated to the patch. It produces
the 32 and 64 bit executables for the following steps hence why it has to be
executed first. When it fails the other steps are skipped which is not the case
for the other steps.
So the general structure is:
Step 1 - patch.diff - Build
Step 2 - test_32.exe - One task per VM
Step 3 - test_64.exe - One task per VM
So one source of inefficiency is that the 64 bit tests cannot start until all
the 32 bit tests have completed. It does not necessarily make the overall job
execution longer but it can leave a VM host idle while it waits for the
remaining 32 bit tests to complete. And if a developer is watching the job's
page he will not know of 64 bit failures until then.
So while the build step has to come before all others, that condition should be
relaxed for the other steps.
The database schema presented in bug 39412 adds a DependencyNo field to the
Step table so that step dependencies can be made explicit. This would allow
making both test steps depend on build one. Note that with this scheme a given
step could not directly depend on multiple other steps but that does not seem
needed.
It would also make more explicit the fact that test steps cannot be run if the
build one fails instead of hard-coding that behavior in Jobs::UpdateStatus().
--
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.