http://bugs.winehq.org/show_bug.cgi?id=32805
Bug #: 32805
Summary: Android AVD Manager does not run
Product: Wine
Version: 1.5.22
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: john.aaron.rose(a)googlemail.com
Classification: Unclassified
Created attachment 43326
--> http://bugs.winehq.org/attachment.cgi?id=43326
Terminal output.
AVD Manager gives Java exception when it starts.
NB SDK Manager works OK.
--
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=42771
Bug ID: 42771
Summary: MSI error during StudioTax 2011 installation
Product: Wine
Version: 2.5
Hardware: x86-64
URL: https://www.downloadstudiotax.com/ver11/StudioTax2011I
nstall.exe
OS: Linux
Status: NEW
Keywords: download, Installer
Severity: normal
Priority: P2
Component: msi
Assignee: wine-bugs(a)winehq.org
Reporter: frederic.delanoy(a)gmail.com
Distribution: ---
MSI error early in installer.
SHA1 StudioTax2011Install.exe 51bf0afc5e3ced584951568ab4f1cf9d0a841d4d
Installing mono or dotnet20sp2 from winetricks doesn't help (the installer just
gets a little further, but installation still fails/hangs at the end)
err:msidb:msi_table_load_transform borked.
0007 L"FileCost"
1201 (null)
0000 L""
030a L"B21EBECC_CED3_4773_B2F7_2A9B571B8007"
03d3 L".NET Framework 2.0 SP2"
068f
L"http://download.microsoft.com/download/c/6/e/c6e88215-0178-4c6c-b5f3-158ff7…"
0001 L"AdminExecuteSequence"
8000 (null)
0000 L""
8000 (null)
0000 L""
0000 L""
0000 L""
0000 L""
0000 L""
8000 (null)
0000 L""
0000 L""
0000 L""
000f L"NET_Framework_2.0_SP2_1"
0690 L"( 1 AND ( NOT AI_NET_20_SP2_PREREQSEARCH_2_PROP ) AND ( NOT
AI_NET_20_SP2_PREREQSEARCH_1_PROP ) AND ( NOT
AI_NET_20_SP2_WIN_PREREQSEARCH_PROP ) AND ( NOT
AI_NET_20_SP2_40_CP_PREREQSEARCH_PROP ) AND ( NOT
AI_NET_20_SP2_40_PREREQSEARCH_PROP ) ) "
0000 L""
0000 L""
0000 L""
--
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=14299
Summary: winhelp: Missing << and >> buttons with some help files
Product: Wine
Version: 1.1.0
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: markk(a)clara.co.uk
For many help files, the forward and back buttons (<< and >>) are not shown in
Wine winhelp. However they do appear with other help files (e.g. pphelp.hlp).
For example, download winehelp_bugs.tar.bz2 from
http://bugs.winehq.org/attachment.cgi?id=14574
and load castle1.hlp, chess.hlp or emle.hlp into Wine winhelp.
--
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=22984
Summary: winhelp: Corrupted/incorrectly-rendered italic text
Product: Wine
Version: 1.2-rc2
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: markk(a)clara.co.uk
I noticed this when viewing a specific help file in Wine winhlp32, but the
issue doesn't seem to be specific to that. Viewing it using winhlp32 from
Windows 98 under Wine shows a similar rendering issue, so the cause most
probably lies elsewhere. They both render the text incorrectly, but
differently.
Italic text does not render properly. View the attached license.hlp file in
Wine winhlp32. In the "4. SAMPLE CODE" and "5. REDISTRIBUTABLE COMPONENTS"
paragraphs, the second instance of "Microsoft Systems Journal" is supposed to
be rendered in italics (followed by "(MSJ)" which is not italic).
Bug 7520 may be related to this. But in this case, Wine could/should at least
render the text normally I think, rather than corrupted/garbled???
--
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=22950
Summary: nokia music player installation failed
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: loader
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: versterj(a)gmail.com
when running setupoviplayer.exe to install nokia music player
the installation hangs after terms and condition page has been "ok".
i want to start to download the music asap.
thanks
--
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=32910
Bug #: 32910
Summary: QQImage crashes when exiting it
Product: Wine
Version: 1.5.23
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jactry92(a)gmail.com
Classification: Unclassified
Created attachment 43464
--> http://bugs.winehq.org/attachment.cgi?id=43464
The dmp file
1. download it, 'winetricks -q vcrun2005' to make Bug 23094 go away;
2. install it on default setting ('一键安装') and it will startup after
installation;
3. click the close button and select the right option (as the picture) then
click the button to enter and it will crashes and generate a error window.
It will generate a 'dmp' file in '~/.wine/drive_c/user/username/Application
Date/tencent/QQImage/Dump/', backtrace.txt is the infonation get by 'wine
QQImageApp_06-02-2013-17-53-19.dmp'.
sha1sum QQImage_Setup_30_890.exe
ba4c3d2e431ad9c76817fa31447abb696cbcce96 QQImage_Setup_30_890.exe
--
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=33985
Bug #: 33985
Summary: Nokia Music Player: window decorations should not be
displayed in installer window
Product: Wine
Version: 1.6-rc4
Platform: x86-64
URL: http://nds1.nokia.com/files/support/nseries/phones/sof
tware/SetupOviPlayer.exe
OS/Version: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: frederic.delanoy(a)gmail.com
Classification: Unclassified
Created attachment 45154
--> http://bugs.winehq.org/attachment.cgi?id=45154
WinXP/wine-1.6-rc4-52-g9a0b434 side-by-side comparison
The windows decorations (here from XFCE 4.10) are present in Wine while they
aren't in native Windows.
See attached screenshot for a comparison
--
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=33984
Bug #: 33984
Summary: Nokia Music Player: extraneous transparent gray border
in installer window
Product: Wine
Version: 1.6-rc4
Platform: x86-64
URL: http://nds1.nokia.com/files/support/nseries/phones/sof
tware/SetupOviPlayer.exe
OS/Version: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: frederic.delanoy(a)gmail.com
Classification: Unclassified
Created attachment 45152
--> http://bugs.winehq.org/attachment.cgi?id=45152
WinXP/wine-1.6-rc4-52-g9a0b434 side-by-side comparison
See attached screenshot for a comparison
--
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=33027
Bug #: 33027
Summary: sPlan 7.0: text label not displayed entirely in popups
Product: Wine
Version: 1.5.24
Platform: x86-64
URL: http://www.abacom-online.de/demos/splan70(demo).exe
OS/Version: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: frederic.delanoy(a)gmail.com
Classification: Unclassified
Install the demo version of sPlan 7.0, and start the program
You should see a "sPlan" popup containing:
"This is a limited sPlan 7.0 demo
Saving, exporting and printing is disabled."
The popup is present, but the "disabled." part is not displayed.
A similar issue occurs when you exit the program.
--
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=42756
Bug ID: 42756
Summary: test.winehq.org uses a lot of disk space
Product: WineHQ.org
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
According to my estimates the static HTML files for the test.winehq.org site
use around 21.5 GB. That seems a lot for such a simple website.
This estimate is based on the following data collected from 3 days worth of
reports:
8.3MB / report
60 reports / day
500MB / day
44 days history
-> 21.5 GB total
It's not because the raw reports are big either. On any given day we get:
50 MB of raw report files
180 MB of full report HTML files
285 MB of individual test unit HTML files
3 MB of index files
So most of it is caused by the HTML files.
Here are some ways one could minimize the bloat:
1) Split the raw report into one file per test unit plus one index file to know
in which order to reassemble them. These would not use more space than the
original raw report except for the filesystem's internal fragmentation. Then
each file the web server serves would be generated from these. For the raw
report one would just have to concatenate them in the right order. The full
report and the individual test unit files would have to parse the relevant
source text files. A drawback is all the extra parsing required to generate
each page. Plus some issues in the raw report can only be detected when parsing
the full report as they show up as issue transitioning from one test result to
the next.
2) An other option would be to skip generating the full report HTML file and
omit the header and footer of the individual test unit HTML files. Then each
page could be generated by assembling the individual HTML fragments with the
right HTML glue to build either a full HTML report or an individual test unit
HTML file. This would have the advantage of not requiring more parsing to serve
each file.
3) Drop the individual test unit HTML files and always link to the full HTML
report. The drawback is more bandwidth usage since every one looking at a test
result would end up downloading the 180 MB full report instead of the small
individual test unit reports.
4) Drop the full HTML report and only keep the per test unit HTML files. This
provides a lower disk saving but does not force users to download a big file
when they are only interested in the result of one test unit.
5) Use some way to reduce the size of the links to the Git source. Removing the
links altogether saves 191 MB in the test case. Out of the 128 characters of a
typical link, 95 of these are identical from one link to the next. So maybe
using some JavaScript one could factorize most of this.
A drawback of options 1 and 2 is that since the files would no longer be static
they could probably not be put up on a content distribution network. But I'm
not sure test.winehq.org uses a CDN now so this probably does not matter.
It may still be possible to reduce the processing load introduced by 1 and 2 by
caching the generated files for a few hours or days. All in all this would
increase complexity quite a bit though.
--
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.