wine-bugs

wine-bugs@winehq.org

1 participants
158774 discussions

[Bug 57732] New: "Ooops! Something has gone terribly wrong!" message when trying to see queued items in appdb
by WineHQ Bugzilla 25 Jan '25

25 Jan '25

https://bugs.winehq.org/show_bug.cgi?id=57732 Bug ID: 57732 Summary: "Ooops! Something has gone terribly wrong!" message when trying to see queued items in appdb 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: francisco278herrera(a)gmail.com Distribution: --- "Ooops! Something has gone terribly wrong!" message appears when trying to see queued items in appdb while logged into the appdb -- 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.

1 3

[Bug 57731] New: Gateway time-out when trying to look browse apps in appdb
by WineHQ Bugzilla 25 Jan '25

25 Jan '25

https://bugs.winehq.org/show_bug.cgi?id=57731 Bug ID: 57731 Summary: Gateway time-out when trying to look browse apps in appdb 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: francisco278herrera(a)gmail.com Distribution: --- Gateway time-out occurs when trying to browse apps in the appdb from the home page. -- 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.

1 4

[Bug 57730] New: Gateway time-out when trying to look at all versions of an app
by WineHQ Bugzilla 25 Jan '25

25 Jan '25

https://bugs.winehq.org/show_bug.cgi?id=57730 Bug ID: 57730 Summary: Gateway time-out when trying to look at all versions of an app 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: francisco278herrera(a)gmail.com Distribution: --- Gateway time-out occurs when trying to look at all versions of an app for example this one: https://appdb.winehq.org/objectManager.php?sClass=version&iId=9194 -- 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.

1 4

[Bug 56612] New: AppDB now lists everyone who is e-mailed
by WineHQ Bugzilla 25 Jan '25

25 Jan '25

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.

1 2

[Bug 57479] New: link for email reply in appdb is corrupted.
by WineHQ Bugzilla 25 Jan '25

25 Jan '25

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.

1 2

[Bug 28467] New: Chromium Browser restore button doesn't work
by wine-bugs＠winehq.org 25 Jan '25

25 Jan '25

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.

2 14

[Bug 56647] New: ntdll-Junction_Points prevent rustup from correctly installing a toolchain
by WineHQ Bugzilla 25 Jan '25

25 Jan '25

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.

1 13

[Bug 57729] New: Game (Witch's Heart) runs faster than intended at times/given areas.
by WineHQ Bugzilla 24 Jan '25

24 Jan '25

https://bugs.winehq.org/show_bug.cgi?id=57729 Bug ID: 57729 Summary: Game (Witch's Heart) runs faster than intended at times/given areas. Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kyubi015(a)proton.me Distribution: --- Game (Witch's Heart) runs faster than intended at times. Mostly noticable in a selected few rooms, havent noticed any case where it did not run faster than intended in those areas. This bug isnt specific to said areas however, also noticed a case where a previously not affected area sped up after a transition but that only happened once. Download link: https://vgperson.com/games/witchheart.htm Its not a 2.03 version specific issue, also was present for 2.00 Only tried main game, not any of the bonus ones. -- 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.

1 2

[Bug 56707] New: AppDB PHP8 rewrite
by WineHQ Bugzilla 24 Jan '25

24 Jan '25

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.

1 7

[Bug 36692] New: Bad performance when combineng SetEvent / WaitForSingleObject for synchronizing worker threads
by wine-bugs＠winehq.org 24 Jan '25

24 Jan '25

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.

2 30

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs