https://bugs.winehq.org/show_bug.cgi?id=53652
Bug ID: 53652
Summary: invalid URL in wine-bugs digest email footer
Product: WineHQ Bugzilla
Version: 3.2.3
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: bugzilla-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
CC: austinenglish(a)gmail.com, jnewman(a)codeweavers.com,
julliard(a)winehq.org
Distribution: ---
I'm guessing this happened around the mailman upgrade:
Sep 10:
_______________________________________________
wine-bugs mailing list -- wine-bugs(a)winehq.org - To unsubscribe send an email
to wine-bugs-leave(a)winehq.org
%(web_page_url)slistinfo/%(_internal_name)s
versus:
July 26:
_______________________________________________
wine-bugs mailing list - wine-bugs(a)winehq.org
https://www.winehq.org/mailman/listinfo/wine-bugs
'bisecting' the regression, it occurred between:
bad: Aug 12 wine-bugs Digest, Vol 205, Issue 46
good: Aug 12 wine-bugs Digest, Vol 205, Issue 45
--
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=56630
Bug ID: 56630
Summary: Broken links in email for "Test Results added to
version ..."
Product: WineHQ Apps Database
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: appdb-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: 56ms2hl02(a)sneakemail.com
Distribution: ---
In an E-Mail I got:
Test Results added to version GoG of Sid Meier's Alpha Centauri by axm
-------------------------------------------------------
https://appdb.winehq.org/objectManager.php?sClass=3Dversion&iId=3D24358&=
;iTestingId=3D114903
This Test data has been submitted by axm.
... where the link is malformed due to the line break but I also could not fix
it manually.
It should probably be:
https://appdb.winehq.org/objectManager.php?sClass=version&iId=24358
Note this is the current version and it got autoapproved (probably because I am
the maintainer, too).
Using this search
https://bugs.winehq.org/buglist.cgi?bug_status=__all__&content=link&no_redi…
I found a simimar, but very old and outdated bug report that maybe can be
closed instead:
https://bugs.winehq.org/show_bug.cgi?id=25699
--
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=56612
Bug ID: 56612
Summary: AppDB now lists everyone who is e-mailed
Product: WineHQ Apps Database
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: critical
Priority: P2
Component: appdb-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: imwellcushtymelike(a)gmail.com
Distribution: ---
Created attachment 76367
--> https://bugs.winehq.org/attachment.cgi?id=76367
Screenshot (censored)
I've received a few e-mails from the AppDB, which is the norm. It used to only
list me in the To:, now it lists everyone who receives the e-mail.
Leaking the user's e-mail addresses could be considered a data breach.
--
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=57479
Bug ID: 57479
Summary: link for email reply in appdb is corrupted.
Product: WineHQ Apps Database
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: appdb-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: alois.schloegl(a)gmail.com
Distribution: ---
I received an email starting with this information;
From: appdb-noreply(a)winehq.org
[PM] Cadence AWR on Wine
-------------------------------------------------------
The following message was sent to you from Franco Curotto through the Wine =
AppDB contact form.
To Reply, visit https://appdb.winehq.org/contact.php?iRecipientId=3D460194&=
amp;sSubject=3DRe%3A+Cadence+AWR+on+Wine
...
The reply link does not work for me, and seems to be corrupted.
--
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=28467
Summary: Chromium Browser restore button doesn't work
Product: Wine
Version: 1.3.28
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 with --no-sandbox, works around Bug 21232
$ wine chrome.exe --no-sandbox
Notice that the chrome window is decorated by the Linux native window manager.
Is it a bug? On windows, chrome have no traditional "window bar".
Now there is two "Maximal" button: one is drawn by Linux native window manager,
the other is drawed by wine chrome browser it self.
3. Click on the "Maximal" button which is drawn by Linux native window manager,
then chrome browser switch to maximal mode as expect.
This time, the Linux native window bar is disappear.
4. Click on the "Restore" button of wine chrome browser. However it doesn't
work. Wine chrome switch to normal mode for a second, then switch back to
maximal mode automatically.
I use ubuntu 11.04 , with traditional gnome desktop, gnome 2.32.1 .
There is some ways to work around:
I. Instead of clicking on the native "Maximal" button in step 3, try to click
the wine chrome "Maximal" button, then everything works as expect.
II. Do not set "Allow the window manager to decorate the windows" in winecfg,
then everything works as expect.
III. Do not set "Allow the window manager to control the windows" in winecfg,
then everything works as expect.
--
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=56647
Bug ID: 56647
Summary: ntdll-Junction_Points prevent rustup from correctly
installing a toolchain
Product: Wine-staging
Version: 9.8
Hardware: x86-64
URL: https://rustup.rs/
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lorenzofer(a)live.it
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ArchLinux
Created attachment 76423
--> https://bugs.winehq.org/attachment.cgi?id=76423
return STATUS_NOT_A_REPARSE_POINT instead of STATUS_INVALID_PARAMETER
Hi.
With the recent rustup 1.27.0 using wine-staging with the
ntdll-Junction_Points patches, the toolchain installation doesn't complete
properly, failing to write to the settings.toml under the prefix home .rustup
directory info.
A bug with the same root cause is also present on rustup 1.26.0 where while the
installation was completing properly, it was failing to remove the
.rustup/tmp/* directories, causing issues with subsequent installations.
Both bugs express the same behavioral pattern with few differences. I
investigated the directory bug firstly, so I will detail this, and confirmed
that the problem and the expected solution are the same.
Rustup (or one of it's dependency managing files) get the handle of the
temporary directory using CreateFileW and then checking if it's a reparse point
using DeviceIoControl with FSCTL_GET_REPARSE_POINT.
The directories (and the file) aren't reparse points at all, so the readlink
fails returining EINVAL.
This EINVAL is then mapped to an NT_STATUS using errno_to_status that map
EINVAL to STATUS_INVALID_PARAMETER.
However this mapping is incorrect for FSCTL_GET_REPARSE_POINT as in this case
applications that handle this case like rustup try to handle this case by
epxecting STATUS_NOT_A_REPARSE_POINT.
Returning STATUS_NOT_A_REPARSE_POINT in this case allow rustup to work (both
versions )
Attaching a patch to show the change in the file.c code (and restored also the
out_buffer check)
--
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=56707
Bug ID: 56707
Summary: AppDB PHP8 rewrite
Product: WineHQ Apps Database
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: appdb-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jnewman(a)codeweavers.com
Distribution: ---
The current codebase is not compatible with PHP8. We are stuck on 7.4.
The main issue is how all the objects are setup. PHP8 requires you define a
constructor as __construct, but the AppDB is using the old method of naming the
constructor the same as the object itself. While you could just rename all
those to __construct, there are places in the objects where the code refers to
$this->className(), these would need to be changed to $this->__construct() or
parent::__construct if called from a child class
There are other PHP8 issues to be solved as well. Things like some built in
functions changing how the null type is handled.
--
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=36692
Bug ID: 36692
Summary: Bad performance when combineng SetEvent /
WaitForSingleObject for synchronizing worker threads
Product: Wine
Version: 1.6.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: milasudril(a)gmail.com
In a 2d simulation program, each worker thread has its own pair of events. One
event is used to signal master thread that the worker thread is ready. The
other is used by the master thread to signal that the worker thread may
continue.
In Master thread:
while(!m_stop)
{
auto proc_ptr=processors.begin();
while(proc_ptr!=processors.end())
{
// Call SetEvent on "start" event object owned by the object pointed
// to by proc_ptr
proc_ptr->frameNext();
++proc_ptr;
}
proc_ptr=processors.begin();
while(proc_ptr!=processors.end())
{
// Call WaitForSingleObject on "ready" event object owned by
// the object pointed to by proc_ptr
proc_ptr->wait();
++proc_ptr;
}
++framecounter;
}
In worker thread:
while(!m_stop)
{
// Wait for master thread signaling start event (Calls
WaitForSingleObject)
start.wait();
m_model->process(m_framecounter,m_buffers[0].first
,m_buffers[0].second,m_offset);
swap(m_buffers[0],m_buffers[1]);
// Signal master thread that we are ready for next frame (Calls SetEvent)
ready.set();
}
On Wine, the framerate is half of that on Windows 7 on the same machine
Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz. Also there seems to be a huge
different workload on differnt cores when running under Wine.
I realize that SetEvent/WaitForSingleObject are heavy functions on Windows too
as they need kernel assistance, so it might be hard to make it perform better.
--
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=43766
Bug ID: 43766
Summary: Safrosoft RoX - Level editor doesn't start
Product: Wine
Version: 2.17
Hardware: x86-64
URL: http://www.autofish.net/shrines/rox/
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: oleaut32
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
Distribution: ArchLinux
Created attachment 59268
--> https://bugs.winehq.org/attachment.cgi?id=59268
wine log
The game's level editor crashes with a messagebox:
"Run-time error '481': Invalid picture"
Getting an oleaut32.dll from win7, copying it into wine's system32 folder and
adding a dll override fixes the issue.
--
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=44900
Bug ID: 44900
Summary: Colour problem with builtin gdiplus
Product: Wine
Version: 3.5
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdiplus
Assignee: wine-bugs(a)winehq.org
Reporter: jeremielapuree(a)yahoo.fr
Distribution: ---
Created attachment 60981
--> https://bugs.winehq.org/attachment.cgi?id=60981
Good looking with a native gdiplus
With a builtin gdiplus, there is a problem with coloring the cases of channel.
Problem does not occur with a native gdiplus dll. Compare the two screenshot:
the first one with native dll, the second one with the builtin dll.
Note the behaviour in a real Windows 10 box is the behaviour of the native dll.
So, there is a problem with the builtin dll.
--
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.