https://bugs.winehq.org/show_bug.cgi?id=35967
Bug ID: 35967
Summary: postgresql 9.3.4-3 fails to install (needs to be a
non-administrator)
Product: Wine
Version: 1.7.16
Hardware: x86
URL: http://www.postgresql.org/download/windows/
OS: Linux
Status: NEW
Keywords: download, Installer
Severity: minor
Priority: P2
Component: vbscript
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Depends on: 35966
Created attachment 48074
--> https://bugs.winehq.org/attachment.cgi?id=48074
report non-admin privileges
Background: a user asked about how to get wine to report not running as admin
in #winehackers, for postgresql
After winetricks wsh57 to work around bug 35966, the installer mostly works. At
the end the install, it tells you there was a problem starting the database.
Looking at its log, I see:
creating template1 database in C:/Program Files/PostgreSQL/9.3/data/base/1 ...
Execution of PostgreSQL by a user with administrative permissions is not
permitted.
The server must be started under an unprivileged user ID to prevent
possible system security compromises. See the documentation for
more information on how to properly start the server.
child process exited with exit code 1
initdb: removing contents of data directory "C:/Program
Files/PostgreSQL/9.3/data"
Called Die(Failed to initialise the database cluster with initdb)...
Failed to initialise the database cluster with initdb
Vincent offered the user a suggestion on how to avoid it, I'll attach that
patch. With that patch, the non-admin error goes away, and I get a cmd 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.
http://bugs.winehq.org/show_bug.cgi?id=30672
Bug #: 30672
Summary: QIP Infium: incorrect blending at the edges
Product: Wine
Version: 1.5.4
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: wylda(a)volny.cz
Classification: Unclassified
This is continuation of bug 22902, which was about icon transparency problem.
Icons in connection setting have black shadows as shown on the following link:
http://bugs.winehq.org/attachment.cgi?id=38155
Problem is still present in wine-1.5.4 & QiP Infium build9032.
--
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=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=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=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.
https://bugs.winehq.org/show_bug.cgi?id=47733
Bug ID: 47733
Summary: Project Reality BF2 PRLauncher.exe doesn't start with
Wine-Mono.
Product: Wine
Version: 4.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: apq49584(a)tuofs.com
Distribution: ---
Created attachment 65209
--> https://bugs.winehq.org/attachment.cgi?id=65209
What you see if it works (obtained wth native dotNetFx40_Client)
Debian 10 buster with winehq packaged wine-devel and libfaudio from OBS.
wine-mono-4.9.2.msi downloaded and installed by wine on first run.
Download link:
https://www.realitymod.com/downloads
$ wine start PRLauncher.exe
The entry point method could not be loaded due to Could not load file or
assembly 'PresentationFramework, Version=4.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35' or one of its dependencies.
(The PRLauncher.exe does work if wine-mono is removed and
dotNetFx40_Client_x86_x64.exe is installed with wine uninstaller.
This is again just background information and was NOT done for the bug report.)
I am reporting the bugs with PRBF2.exe and PRLauncher.exe seperately, because
they happen in very different parts of wine and can be tested for
independently.
--
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.