http://bugs.winehq.org/show_bug.cgi?id=18741
Summary: Wine printing output should be in .pdf rather than
postscript
Product: Wine
Version: 1.1.22
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: wineps.drv
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: scott(a)open-vote.org
Blocks: 5551,6416
The new CUPS standards from http://openprinting.org/ say that .pdf is the
preferred printing format over postscript:
https://lists.linux-foundation.org/pipermail/printing-architecture/2008/001…
--
PDF as the Standard Print Job Format
------------------------------------
To improve the reliability of the printing process, especially for
complex graphics, high color depths, and for jobs where pages get
separated and reordered (2 pages per sheet, booklets, selected pages,
...) we are switching from PostScript to PDF as standard print job format.
The server (printing system) side is nearly completely implemented in
the form of new CUPS filters and file conversion rules.
On the client (application) side it is needed that the applications
generate the print jobs in PDF and not in Postscript. This would mean a
change of the print job generation part of OpenOffice.org. As
OpenOffice.org has an excellent "Export to PDF" function, there will not
be needed much new code. One can use this functionality to generate
print jobs, using PDF settings optimized for printing.
This is not absolutely urgent, as CUPS can convert PostScript to PDF
with a pstopdf filter, but applications which directly produce PDF have
a better control over the graphical quality of the print job, and they
even solve page management (2 on a sheet, booklets, selected pages, ...)
problems on old PostScript-based servers, as a CUPS filter will generate
PostScript from the incoming PDF then (pdftops) and this PostScript is
much cleaner as the one coming from most applications.
So I am asking you whether you can change OpenOffice.org to make the
"Print" command emitting PDF instead of PostScript. To not break lagacy,
non-PDF-capable environments, make this a configurable option.
I am very grateful for any support from the OpenOffice.org side in terms
of these OpenPrinting projects. They will improve the printing workflow
a lot and will make many bugs and user complaints go away.
--
We should do a similar thing in Wine
--
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=30740
Bug #: 30740
Summary: winedump should extend ordinal imports/exports with
known names from our spec files
Product: Wine
Version: 1.5.4
Platform: x86-64
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P2
Component: tools
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: wine.dev(a)web.de
Classification: Unclassified
winedump in dump mode show ordinal imports/exports only as numbers,
but we have names for many of them in our spec files.
In addition to create *def files for all exports from spec files,
we should create a database (set of c or h files) for all numbered export
for every dll in Wine and add them to winedump.
No idea, if this database is an improvement for other tools or dlls.
(winedbg, dbghelp.dll as examples)
--
By by ... Detlef
--
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=37044
Bug ID: 37044
Summary: Freedom Fighters game has slow performance
Product: Wine
Version: 1.7.22
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: subins2000(a)gmail.com
The game starts and works, but the gameplay is slow. The intro, menu and
gameplay is slow.
--
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=17329
Summary: Wine needs more userfriendly message when certain dlls
are not registered/missing
Product: Wine
Version: 1.1.12
Platform: PC
URL: http://www.whizlabs.com/download.php?prod=SCJP6.0.exe
OS/Version: Linux
Status: NEW
Keywords: download
Severity: enhancement
Priority: P2
Component: ole32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: xerox_xerox2000(a)yahoo.co.uk
Created an attachment (id=19352)
--> (http://bugs.winehq.org/attachment.cgi?id=19352)
an idea of how to generate more userfriendly message
This bug's intention is to enhance user friendlyness, and hopefully less
invalid bug reports, and more first time success experience for users.
Take for example app from http://www.whizlabs.com/download.php?prod=SCJP6.0.exe
(from some bug in bugzilla). The application fails with a run-time error, and
some , for newbies, cryptic ole errors.
I think it would enhance wine's userfriendlyness a big deal, if we would just
put up a nice messagebox, with a message what the error means, and what should
be done.
I'll attach a (crappy) patch , just to give an idea how easy it would be to
give users more clues how to get around the "bug".
Just apply patch , and run the app above, and user will know he has to install
wsh56.
--
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=40925
Bug ID: 40925
Summary: Flame in the Flood crashes with a Fatal error
Product: Wine
Version: 1.9.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: blue-t(a)web.de
Distribution: ---
Created attachment 55034
--> https://bugs.winehq.org/attachment.cgi?id=55034
Log output
Now that R16-Typeless is supported as of b53b717 the game no longer crashes
with a fatal error in CreateTexture2D.
The crash window now only talks about Fatal Error without any additional hints.
--
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=17323
Summary: Superbase Dialogs are too wide
Product: Wine
Version: 1.1.14
Platform: PC-x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: harv(a)gmx.de
Created an attachment (id=19348)
--> (http://bugs.winehq.org/attachment.cgi?id=19348)
Uppre is how it looks like in XP, lower part is same dialog in wine 1.1.14
Superbase (a Relational database management system) displays its internal
dialogs way too wide. They don't even fit on the screen. See attachment.
--
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=40110
Bug ID: 40110
Summary: d3d10core:device and d3d11:d3d11 regression
Product: Wine
Version: 1.9.3
Hardware: x86
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Since the commits below, my fg-acer64 test machine is getting new failures on
Windows 8, in both 32 and 64 bits. fg-acer64 is an Acer laptop with an i5-3317U
processor and HD Graphics 4000 integrated graphics.
d3d10core:device failures:
device.c:4858: Test failed: Got unexpected color 0xff0000ff at (0, 0), expected
0xffffffff.
device.c:4858: Test failed: Got unexpected color 0xff00ffff at (1, 0), expected
0xff000000.
device.c:4858: Test failed: Got unexpected color 0xff00ff00 at (2, 0), expected
0xff000000.
device.c:4858: Test failed: Got unexpected color 0xffffff00 at (3, 0), expected
0xff000000.
device.c:4858: Test failed: Got unexpected color 0xffff0000 at (0, 1), expected
0xffffff00.
device.c:4858: Test failed: Got unexpected color 0xffff00ff at (1, 1), expected
0xff0000ff.
device.c:4858: Test failed: Got unexpected color 0xff000000 at (2, 1), expected
0xff00ffff.
device.c:4858: Test failed: Got unexpected color 0xff7f7f7f at (3, 1), expected
0x00000000.
device.c:4858: Test failed: Got unexpected color 0xffffffff at (0, 2), expected
0xff7f7f7f.
device.c:4858: Test failed: Got unexpected color 0xffffffff at (1, 2), expected
0xffff0000.
device.c:4858: Test failed: Got unexpected color 0xffffffff at (2, 2), expected
0xffff00ff.
device.c:4858: Test failed: Got unexpected color 0xff000000 at (3, 2), expected
0xff7f7f7f.
device.c:4858: Test failed: Got unexpected color 0xff000000 at (1, 3), expected
0xffffffff.
device.c:4858: Test failed: Got unexpected color 0xff000000 at (3, 3), expected
0x00000000.
d3d11:d3d11 failures:
d3d11.c:4508: Test failed: Got unexpected color 0xff0000ff at (0, 0), expected
0xffffffff.
d3d11.c:4508: Test failed: Got unexpected color 0xff00ffff at (1, 0), expected
0xff000000.
d3d11.c:4508: Test failed: Got unexpected color 0xff00ff00 at (2, 0), expected
0xff000000.
d3d11.c:4508: Test failed: Got unexpected color 0xffffff00 at (3, 0), expected
0xff000000.
d3d11.c:4508: Test failed: Got unexpected color 0xffff0000 at (0, 1), expected
0xffffff00.
d3d11.c:4508: Test failed: Got unexpected color 0xffff00ff at (1, 1), expected
0xff0000ff.
d3d11.c:4508: Test failed: Got unexpected color 0xff000000 at (2, 1), expected
0xff00ffff.
d3d11.c:4508: Test failed: Got unexpected color 0xff7f7f7f at (3, 1), expected
0x00000000.
d3d11.c:4508: Test failed: Got unexpected color 0xffffffff at (0, 2), expected
0xff7f7f7f.
d3d11.c:4508: Test failed: Got unexpected color 0xffffffff at (1, 2), expected
0xffff0000.
d3d11.c:4508: Test failed: Got unexpected color 0xffffffff at (2, 2), expected
0xffff00ff.
d3d11.c:4508: Test failed: Got unexpected color 0xff000000 at (3, 2), expected
0xff7f7f7f.
d3d11.c:4508: Test failed: Got unexpected color 0xff000000 at (1, 3), expected
0xffffffff.
d3d11.c:4508: Test failed: Got unexpected color 0xff000000 at (3, 3), expected
0x00000000.
The results on test.winehq.org:
https://test.winehq.org/data/tests/d3d10core:device.htmlhttps://test.winehq.org/data/tests/d3d11:d3d11.html
commit 50a8d3f6d2c0bce11aefa94a0b7fa53951d0defe
Author: Józef Kucia <jkucia(a)codeweavers.com>
Date: Tue Jan 19 22:28:12 2016 +0100
d3d10core/tests: Port test_copy_subresource_region() from d3d11.
Signed-off-by: Józef Kucia <jkucia(a)codeweavers.com>
Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
commit c161543c8678125b00972282208035ad710ff648
Author: Józef Kucia <jkucia(a)codeweavers.com>
Date: Tue Jan 19 22:28:11 2016 +0100
d3d11/tests: Add test for ID3D11DeviceContext::CopySubresourceRegion().
Based on test_update_subresource().
Signed-off-by: Józef Kucia <jkucia(a)codeweavers.com>
Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
--
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=35397
Bug ID: 35397
Summary: Endless Steam Client Update even after fresh install
Product: Wine
Version: unspecified
Hardware: x86-64
OS: FreeBSD
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lehmannwer(a)gmail.com
Classification: Unclassified
$ wine --version
wine-1.7.10
$
FreeBSD (x64) 9.1
Geforce 8600 GT
nvidia-driver-319.32
Even after complete deletion of the Steam folder and a fresh install of the
SteamSetup.exe file, when setup seems complete, it downloads about 104 MB of
updates and starts an update process which never ends. I thought that this
problem had been fixed with version 1.7.8. The Steam client used to work on
this machine last year with version 1.4, so it can't be a hardware related
problem.
--
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=41071
Bug ID: 41071
Summary: PCSX2 1.4.0 needs
api-ms-win-crt-stdio-l1-1-0.dll._wsopen_dispatch
Product: Wine
Version: 1.9.15
Hardware: x86-64
URL: http://pcsx2.net/download/releases/windows/send/40-win
dows/119-pcsx2-1-4-0-binaries.html
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: msvcrt
Assignee: wine-bugs(a)winehq.org
Reporter: 00cpxxx(a)gmail.com
Distribution: Debian
Next after bug 41009.
To reproduce just unpack and run pcsx2.exe.
f6ddb2c354c1b24585f32dd381b3e0b8b62e3972 pcsx2-1.4.0-binaries.7z 4.6Mb
--
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=28132
Summary: MDDClone starts without audio unless 'Sound' tab is
activated in the launcher
Product: Wine
Version: 1.3.26
Platform: x86
URL: http://mercenarysite.free.fr/mddclone.htm#mddclone
OS/Version: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gyebro69(a)gmail.com
MDDClone (a.k.a Mercenary/Damocles/Dion Crisis clone) is a freeware PC remake
of a once classic computer game, written originally for 8-bit computers in the
mid-1980s, and was later ported to the Amigas, too.
Description: when launching the PC remake of the game, you're greeted with a
launcher offering you several choices like game, screen, input, sound. You can
change various settings inside those tabs. The launcher also has the buttons:
<Ok>, <Cancel> and <Exit>. Pressing on <Ok> is starting the game whichever tab
is chosen.
The problem: the game starts without audio unless I choose the <Sound> tab in
the launcher window.
To reproduce the problem:
1) Download and extract the contents of the archive, containing the game.
2) Start the game by executing MDDClone 31 EN.exe (in case you downloaded the
English version).
3) Press on the <Ok> button: the game should start (in a small window) but it
doesn't generate any sounds.
4) Start the game again and select the <Sound> tab in the launcher: you don't
need to change anything, just press on <Ok>: the game will start and audio is
playing correctly.
This behaviour is different to what I experienced when I tried to run the game
under Windows: audio is playing correctly whether the <Sound> tab in the
launcher was selected formerly or not.
A plain terminal output is neither too long nor too informative, so I'm pasting
it here (instead of attaching):
fixme:win:EnumDisplayDevicesW ((null),0,0x32f84c,0x00000000), stub!
fixme:alsa:AudioClient_GetMixFormat Don't know what to do with 10000 channels,
pretending there's only 2 channels
fixme:alsa:AudioClient_GetMixFormat Don't know what to do with 10000 channels,
pretending there's only 2 channels
fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x1489c8,0x13fa60): stub
There was one more fixme added to the log, when the game was started by
selecting the <Sound> tab in the launcher:
fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x13f168,0x13ffe8): stub
The same behaviour with Wine-1.0.1, 1.2.3 etc.
Changing Alsa to 'emulation' mode doesn't help.
Fedora 15 x86
Alsa 1.0.24
Pulseaudio is not running
--
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.