https://bugs.winehq.org/show_bug.cgi?id=37205
Bug ID: 37205
Summary: Android NDK does not support some syscalls
Product: Wine
Version: 1.7.25
Hardware: arm
OS: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: build-env
Assignee: wine-bugs(a)winehq.org
Reporter: matyapiro31(a)gmail.com
As I researched from a believeable blog,
Andriid NDK does not have some syscall headers and some funcs are commented
out=disabled.
Wine uses these syscalls,so We cannot transplant Wine on Android with NDK.
--
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=28026
Summary: chromium crash if --no-sandbox hasn't set
Product: Wine
Version: 1.3.25
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fracting(a)gmail.com
1. Download chromium from
http://build.chromium.org/f/chromium/snapshots/Win/95816/chrome-win32.zip
unpack chrome-win32.zip, cd to the directory.
2. start chrome.exe:
$ wine chrome.exe
chrome will crash without backtrace. A error box will ask you to restart
chrome.
if --no-sandbox is set, then chrome will start without crash, this is similar
to Bug 21232.
--
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=21490
Summary: Debug build of Chromium aborts on startup because
GdiInitializeLanguagePack() returns failure
Product: Wine
Version: 1.1.32
Platform: x86
OS/Version: Linux
Status: NEW
Keywords: download, patch, source
Severity: normal
Priority: P2
Component: gdi32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
This was mentioned in passing in bug 20671.
You can run a debug build of Chromium on Wine with --no-sandbox,
but you have to get GdiInitializeLanguagePack to return success
first, or it will abort early with
[41:42:5571:FATAL:render_process.cc(62)] Check failed: gdi_init_lpk.
The patch attached to bug 20671 does the trick.
http://m-a-tech.blogspot.com/2009/04/emf-buffer-idiocracy.html
explains why Chrome calls that function; it's needed to make native behave.
--
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=9144
Maik Wagner <maiktapwagner(a)aol.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |maiktapwagner(a)aol.com
--- Comment #17 from Maik Wagner <maiktapwagner(a)aol.com> ---
wine-1.7.25 on openSUSE 12.3 - Download from the download URL works and
resizing the window also works for me.
Unfortunately I can't get into the iTunes Store at all. I indicated to be taken
directly to the iTunes store. Also Pull-Down menus from the menu bar are not
shown and there is no reaction when I click other menu items on the left (Music
Library, Movies etc.)
Looks like a "Bronze Medal" for me. Works but has some issues for regular use.
--
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=37191
Bug ID: 37191
Summary: Winehq.org Google custom search is broken
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: austinenglish(a)gmail.com
CC: jnewman(a)codeweavers.com
I've seen this for a while, but assumed it was a browser plugin. It was also
reported in #winehackers, so I tested with Chromium in privacy mode.
Go to https://www.winehq.org. Search for anything (Ubuntu, Photoshop,
Julliard). No results.
Also fails on Firefox.
--
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=34444
Bug #: 34444
Summary: Wine web
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: zorw2016(a)ymail.com
Classification: Unclassified
The Web page
http://www.winehq.org/download/ubuntu
is out of Date =) it has Wine 1.5 latest on there and i know there is 1.7.1 out
so for those that Want ur alsome experience of ur Program lets teach them how
to Install wine 1.7 or 1.6 so they can get the full experience of Wine so they
don’t have to worry about some stuff not work-in for them and have a lot of
Reports to Save =) peace
--
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=13481
Summary: ChangeDisplaySettings can't set *only* BPP
Product: Wine
Version: 1.0-rc2
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P4
Component: gdi32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: rolf(a)neuberrosoft.de
Created an attachment (id=13402)
--> (http://bugs.winehq.org/attachment.cgi?id=13402)
Test case, w Makefile and full NetBeans project tree
Given an "incomplete" DEVMODE structure, with no fields set except for
dmBitsPerPel, and the corresponding flag in dmFields (i.e.
dmFields=DM_BITSPERPEL), ChangeDisplaySettings as implemented in Wine doesn't
replicate the behaviour of a real Windows system correctly.
A real Windows system happily executes the call and returns
DISP_CHANGE_SUCCESSFUL. Display bit-depth will be adjusted, if it was different
to begin with, while the remaining parameters stay as they were. After the
call, resolution and refresh are still whatever the user selected as the
desktop resolution. Even on 2k/XP, which are sometimes happy to drop the
refresh rate to 60Hz, the refresh rate remains constant, which is one of the
reasons I found this type of call to be useful sometimes.
I've tested this today with a MingW-built executable, and found the above to be
accurate for Windows 98SE, Windows 2000 SP4 and Windows XP SP2, irrespective of
whether the initial desktop bit depth is 16 bit or 32 bit.
On Wine (wine-1.0-rc2 on Ubuntu 8.04), the very same call to
ChangeDisplaySettings, made from the same executable, will fail with a return
code of -2 (DISP_CHANGE_BADMODE).
I've attached my test case. It will make the call and pop up a message box with
the results of the call.
I used the i586-mingw32msv-gcc compiler provided by the "mingw32" package in
the official Ubuntu repositories.
The project was set up in NetBeans 6 so the Makefile is somewhat convoluted,
but it doesn't appear as if the build process requires NetBeans. Just
navigating to the directory and running make seems to work. The executable ends
up in dist/Debug/GNU-Windows/.
Priority of the bug isn't high. I've used it in some graphics-library code, but
only in debug builds for my own testing purposes. I'm not aware of publically
available shipping programs that hit on this. Reported anyway, for
correctness's sake.
The app-level workaround is to query the current desktop mode and fill in the
DEVMODE structure more completely. Beyond the scope, but you get the idea.
I'm new to this Bugzilla stuff, so if I forgot some vital piece of info, please
be gentle. I want to be helpful.
--
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=1347
anioshoot(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |anioshoot(a)gmail.com
--
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.