http://bugs.winehq.org/show_bug.cgi?id=13954
Summary: Only top half of screen visible
Product: Wine
Version: CVS/GIT
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: michael(a)araneidae.co.uk
Created an attachment (id=14107)
--> (http://bugs.winehq.org/attachment.cgi?id=14107)
In game menu with only half of screen covered.
For this bug report I'll concentrate on Thief (The Dark Project), but I'm
seeing this problem in a lot of places. In brief, only the top half of the
screen is visible in certain graphical modes.
In more detail: Thief seems to use four different graphical modes, each with
different behaviour.
1. The first mode, used for the menu screens on entry to the game, work
normally. I'm doing this test with a wine virtual desktop at 640x480
resolution (and my real desktop is 1280x1024).
2. On entry to the game it uses hardware 3d graphics that runs very slowly.
This seems to be a known problem with Thief, though I can't see a bug report
for this.
3. Hitting ESC brings up the in-game menu which normally replaces the entire
display; in this report only just under the top half the screen is visible.
Fortunately I can see just enough of the configuration menu to select software
3d graphics.
4. Software 3d graphics used to work tolerably (in a somewhat earlier release,
maybe 0.9.59?), but now I see only the top quarter or less of the screen!
I'll try and attach some screenshots to illustrate this. Um -- how am I
supposed to add more than one screenshot in this message? I've attached an
example for case (3).
This is with Wine 1.0-rc5 built from git, but I've been seeing this problem for
a while now.
--
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=16212
Summary: http://www.winehq.org/site/images/shots/full/wine_1.png
Product: WineHQ.org
Version: unspecified
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: www-unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: vladimiroski(a)gmail.com
Full size Screenshots do not exist anymore, but thumbnails are still showed in
the main page.
A page with a 404 error is displayed instead when you click a thumbnail.
Besides it, a funny error is displayed about where to report the bug, in the
404 error page it says that you should report the bug to the following url:
http://bugs.winehq.org/enter_bug.cgi?product=WineHQ.com
WineHQ.com? sure... :)
--
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=16778
Summary: « News » link in winehq's French home page leads to
an error
Product: WineHQ.org
Version: unspecified
Platform: Other
URL: http://www.winehq.org/news/
OS/Version: other
Status: NEW
Severity: enhancement
Priority: P2
Component: www-unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jonathan(a)ernstfamily.ch
Clicking on "Nouvelles" (News) in winehq's French home page, leads to an error
:
"500 News not found!"
--
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=15419
Summary: Test Data reports should include wine stable versions
(i.e. 1.0, 1.2...) and not just recent betas
Product: WineHQ Apps Database
Version: unspecified
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: appdb-unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: milest3g(a)gmail.com
For AppDB test data to be usefull to users, and since we know have stable wine
releases, "Add Test Data" page should list wine 1.0 as a Tested release, and
not just list 1.1.0 to 1.1.5 (for example), since corporate users and users
looking for stability will be sticking to 1.0 for a long time.
It should be the same for future stable releases like 1.2 - but those should
not supersede 1.0 since some users/distributions might keep 1.0 for a long
time.
--
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=16941
Summary: interrupts cause nested trace output
Product: Wine
Version: 1.1.12
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: hoehle(a)users.sourceforge.net
The winmm periodic timer interrupt (used e.g. by the dsound PCM player) causes
confusion in wine's debug log. I believe every line in the log should be output
atomically. This is not the case and makes the log harder to analyse.
Please search your traces using the following regexp
.[0-9]{4}:[a-zCR]
to find sections where one thread manages to interrupt another one amid a log
line.
In my case, all such occurrences are caused by one thread, identified as
follows:
0019:trace:mmtime:TIME_MMSysTimeThread Starting main winmm thread
Here's a sample where the main thread's (0009) logline is interrupted by the
timer's thread (0019) trace output:
0009: get_handle_fd(0019:Call KERNEL32.GetTickCount()
0019:Ret KERNEL32.GetTickCount()
0019:trace:dsound:DSOUND_timer (1,0,0x1fbbb0,0x0,0x0)
0019:[many lines omitted]
handle=00a4 ) <- This is the remains of the trace output
from the interrupted thread (0009)
0009: *fd* 00a4 -> 83
Here's another example, involving a redispatch to thread 0018:
001e0019:Call KERNEL32.GetTickCount()
0019:Ret KERNEL32.GetTickCount() ...
0019: [many lines omitted]
: create_key() = 0 { hkey=0020, created=0 }
^^^^ remains from thread 001e
0018: get_new_process_info( info=0038 )
0018: select() = PENDING { timeout=infinite, ...
001e:trace:reg:NtCreateKey <- 0x20
The interruptor's pattern is always the same:
- 2x GetTickCount()
- trace:dsound:DSOUND_timer
- dsound perform mix etc.
Looking at libs/wine/debug.c:default_dbg_vlog() I see no obvious mechanism to
ensure atomic output, while and dlls/ntdll/debugtools.c:NTDLL_dbg_vlog() might
have the machinery given a temporary output buffer and a single call to
write().
--
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=17751
Summary: EverQuest: Mouse look issues
Product: Wine
Version: 1.1.17
Platform: PC-x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: winehq(a)hjarding.dk
Using the mouse to look up/down and left/right it seems that a check is made
against the screen boundaries and the movement stops. To look more in the
direction one has to release the mouse look key (often right mouse button) and
click it again to move further in that direction.
--
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=16469
Summary: Favicon is too large and trimmed by web browsers
Product: WineHQ.org
Version: unspecified
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: www-unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: andriusmao(a)gmail.com
winehq.org has a too large favicon, both chrome and firefox do not display the
entire icon, I believe that's not intentional as
http://www.winehq.org/favicon.ico seems different ( this link do not work in
firefox, but ok in chrome)
--
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=16468
Summary: Freelancer renders huge fonts sizes
Product: Wine
Version: 1.1.10
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: kai(a)kaishome.de
My resolution is set to 1600x1200 which computes to 126dpi on my monitor. In
Xorg this is fine, programs render nice. But it's common knowledge that most
windows programs look ugly or render unusable dialogs when the font resolution
is set other than 96dpi. So in winecfg I set it to 96 dpi and all windows
programs I try render correctly (with tiny fonts however - but that's okay for
a windows program ;-)).
But it looks like either wine doesn't respect that when rendering Freelancers
fonts or it renders font sizes wrong on opengl surfaces independent of dpi
settings.
In Freelancer there are overlapping texts in almost any dialog (attaching an
example screenshot). The buy screen is almost unusable.
Maybe it's related: In some dialogs (eg. mission briefings) I find something
that looks like html code and I suppose it comes from the dialogs utilizing rtf
code to do the formatting. Some rtf tags are ignored by wine and rendered plain
text - so formatting isn't really working. Maybe this relates to the incorrect
font sizes...
--
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.