http://bugs.winehq.org/show_bug.cgi?id=29604
Bug #: 29604
Summary: Hanacaraka v.1.0: Crashes when open the application .
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: th31syn(a)gmail.com
Classification: Unclassified
Created attachment 38353
--> http://bugs.winehq.org/attachment.cgi?id=38353
this is the picture when i open the Hanacaraka .
Hanacaraka crashes when i open it .
--
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=25681
Summary: wine iexplore.exe cannot open png files directly
Product: Wine
Version: 1.3.10
Platform: x86
OS/Version: Linux
Status: NEW
Keywords: download
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
I noticed this while looking at bug 4122. If I put a jpeg and a png in
~/.wine/drive_c, then do:
austin@aw21 ~/.wine/drive_c $ wine iexplore.exe "C:\\test.jpeg"
it works fine. Doing the same with a png file, however, fails:
austin@aw21 ~/.wine/drive_c $ wine iexplore.exe "C:\\test.png"
fixme:ole:CoResumeClassObjects stub
fixme:storage:create_storagefile Storage share mode not implemented.
fixme:urlmon:URLMoniker_BindToObject use running object table
fixme:shdocvw:BindStatusCallback_OnProgress status code 11
fixme:shdocvw:BindStatusCallback_OnProgress status code 14
fixme:urlmon:create_object Could not find object for MIME L"image/png"
--
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=7961
exposight <exposight(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |exposight(a)gmail.com
--- Comment #20 from exposight <exposight(a)gmail.com> ---
Still repro in wine 4.18
--
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=6394
exposight <exposight(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |exposight(a)gmail.com
--- Comment #26 from exposight <exposight(a)gmail.com> ---
Still reproducible in wine 4.18 with rapget 1.41
Main download link is dead, but it still can be found on soft library sites.
--
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=38201
Bug ID: 38201
Summary: Newly displayed dialogs have inactive-looking
decorations although are actually active
Product: Wine
Version: 1.7.38
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: b7.10110111(a)gmail.com
Distribution: ---
Created attachment 50980
--> https://bugs.winehq.org/attachment.cgi?id=50980
Screenshot of Windows (left) and Wine (right) MessageBox
If I uncheck "Allow the window manager to decorate the windows" in Graphics tab
of winecfg, or just set wine to show all its windows in a virtual desktop or
launch the apps like `wine explorer /desktop=a,1152x864 appname.exe`, their
windows often look as inactive (gray title bar) while they are actually active.
This is visible in particular in winecfg dialog, Mono/Gecko downloaders dialogs
on wine prefix update, as well as with a simple program like this:
#include <windows.h>
int main() { MessageBox(0,"Hello","Message",MB_OK); }
I've tested the code above in Wine and Windows XP, and in Windows it has
correct active title (blue-lightBlue gradient), while in wine it has inactive
title (gray-lightGray gradient).
If I make any other window active, then switch back to this one, it'll then
show the correct title colors.
The attachment compares Windows' MessageBox with that of Wine, both untouched
at the moment of screenshooting.
--
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=41215
Bug ID: 41215
Summary: Necromancer's Dos Navigator (NDN) fails to run
Product: Wine
Version: 1.9.17
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ddascalescu+wine(a)gmail.com
Distribution: ---
I'm trying to run the W32 version of NDN from http://ndn.muxe.com/download/
because the GNU version fails pretty miserably on current *nixes. The W32
version works great on Windows 7 in XP compatibility mode, but when I run it in
Wine, I get the exact error I get in Windows 7 without XP compatibility turned
on:
$ wine ndn.exe
fixme:process:SetProcessShutdownParameters (00000280, 00000001): partial stub.
Not enough memory available for Necromancer's Dos Navigator .
Please check if at least 400kb memory is available...
$ wineconsole ndn.exe
fixme:process:SetProcessShutdownParameters (00000280, 00000001): partial stub.
dosbbox doesn't work because the program must be run in Win32.
--
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=3599
bignintyfan(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bignintyfan(a)gmail.com
--- Comment #28 from bignintyfan(a)gmail.com ---
I just tried this myself with vanilla Wine 4.18 staging and in a new Wine
prefix. The page printed successfully to a network printer. I think this issue
can be closed.
--
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=47380
Bug ID: 47380
Summary: GT Legends: Slow graphics and 100% CPU usage
Product: Wine
Version: 4.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: timschumi(a)gmx.de
Distribution: ---
GT Legends does have a significant graphics slowdown when running in wine,
while a single CPU thread is locked at 100%.
When looking at the process in a profiler, most of the time is spent in the
function wined3d_cs_mt_finish() (and I guess the wined3d_pause() function
within, which doesn't show up in a profiler due to being inline).
This seems to be a regression as well, since there are videos (for Wine 1.9.10,
[1]) and AppDB entries (latest entry for Wine 1.7.0, [2]) that claim that the
game was running fine on earlier releases of Wine, but I wasn't able to find
the exact commit that introduced the regression so far.
Patches from wine-staging don't help either. Please let me know what type of
logs would be the most suitable ones to debug this, since a normal +d3d log
seems impractical with over 13MB in size.
[1] https://www.youtube.com/watch?v=L80NsdNcVgI
[2] https://appdb.winehq.org/objectManager.php?sClass=version&iId=28706
--
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.