wine-bugs August 2018

wine-bugs@winehq.org

1 participants
8014 discussions

[Bug 39385] New: Make the VM descriptions visible
by wine-bugs＠winehq.org 04 Nov '18

04 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=39385 Bug ID: 39385 Summary: Make the VM descriptions visible Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Each VM has a long description of its hardware and software configuration. They are meant to help developers figure out what's special about a specific VM and how it may explain its results. The long descriptions can be found on the test.winehq.org site by looking at individual reports information. But they cannot be seen on the testbot.winehq.org site except by the administrator when editing the VM configuration. They should be visible as a tooltip/infotip in most places when the VM's name is displayed. -- 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 34256] New: Please add "See Also" support for NetBSD, FreeBSD, etc.
by wine-bugs＠winehq.org 04 Nov '18

04 Nov '18

http://bugs.winehq.org/show_bug.cgi?id=34256 Bug #: 34256 Summary: Please add "See Also" support for NetBSD, FreeBSD, etc. Product: WineHQ Bugzilla Version: unspecified Platform: x86-64 URL: http://source.winehq.org/git/bugzilla.git/blob/HEAD:/B ugzilla/Bug.pm#l2854 OS/Version: Linux Status: NEW Keywords: download, source Severity: enhancement Priority: P2 Component: bugzilla-unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: kennybobs(a)o2.co.uk Classification: Unclassified Created attachment 45590 --> http://bugs.winehq.org/attachment.cgi?id=45590 Error screen See attached screenshot. Could someone with the relevant skills please add support for adding bug trackers for the following to the "See Also" link? FreeBSD (http://www.freebsd.org/support/bugreports.html) Linux (https://bugzilla.kernel.org/) Illumos/OpenIndiana (https://www.illumos.org/issues/) NetBSD (http://www.netbsd.org/support/query-pr.html) Solaris (http://bugs.sun.com/) OpenBSD has shut down their bug tracking system. *shrugs* http://www.openbsd.org/query-pr.html Not urgent, but useful. -- 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.

1 5

[Bug 39414] New: Add a partway job status
by wine-bugs＠winehq.org 04 Nov '18

04 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=39414 Bug ID: 39414 Summary: Add a partway job status Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- If a task is completed the corresponding job's status is 'Running' even if none or the remaining tasks is actually Running. So one can sometimes end up with dozens of 'Running' jobs when only one or two among them actually has an active task. So the idea would be to reserve the 'Running' status to jobs for which one task is actually running. Jobs where some tasks but not all have completed would instead have the 'Partway' status (suggestions for another name welcome). Another issue is that when multiple jobs are in the 'Running' or 'Partway' state it's hard to know which ones have been modified the most recently because the 'Ended' field is not set. This is probably less important though and a waterfall like presentation would help (see bug 39413). -- 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 5

[Bug 41600] New: Unable to view pre-moderated post in forum
by wine-bugs＠winehq.org 04 Nov '18

04 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=41600 Bug ID: 41600 Summary: Unable to view pre-moderated post in forum Product: WineHQ.org Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: brewmanz(a)gmail.com Distribution: --- I've just posted a comment in a forum thread, and wish to alter/add another comment ... but I can't find my post in 'view your posts'! -- 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 40240] New: ntdll:exception causes the Windows 10 VM to crash
by wine-bugs＠winehq.org 04 Nov '18

04 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=40240 Bug ID: 40240 Summary: ntdll:exception causes the Windows 10 VM to crash Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The ntdll:exception test causes the Windows 10 VM (w1064) to crash. Given that this does not happen on real hardware it is a TestBot bug. Incidentally this is why we don't get any WineTest result from that VM. Either there is a way to avoid the crash by adjusting the QEMU configuration or a QEMU bug should be filed. -- 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 44942] New: It is currently impossible to submit test results for Wine-staging, it says discontinued.
by wine-bugs＠winehq.org 04 Nov '18

04 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=44942 Bug ID: 44942 Summary: It is currently impossible to submit test results for Wine-staging, it says discontinued. Product: WineHQ Apps Database Version: unspecified Hardware: Other OS: other Status: UNCONFIRMED Severity: blocker Priority: P2 Component: appdb-unknown Assignee: wine-bugs(a)winehq.org Reporter: arnfranke(a)yahoo.com Created attachment 61047 --> https://bugs.winehq.org/attachment.cgi?id=61047 Wine Staging 3.5 Test Results Unable to check Staging box I just had a test result come in for "Wine 3.5-Staging". The version is set to "3.5" without the "Wine-staging" box checked, and I can see why - you can't check it! Please see the attached image. Despite WineHQ claiming that it's discontinued, you can download it here: https://www.reddit.com/r/wine_gaming/comments/88m1mz/wine_staging_35_releas… This is a blocker for all test results submitted with Wine-Staging. I can't accept these results as they list an incorrect Wine version (3.5 vs 3.5 staging) so accepting these results as-is would be lying about how it runs in Wine 3.5. So what am I supposed to do, reject these test results? -- 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 10

[Bug 43016] New: Missing component comsvcs
by wine-bugs＠winehq.org 04 Nov '18

04 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=43016 Bug ID: 43016 Summary: Missing component comsvcs Product: WineHQ Bugzilla Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: bugzilla-unknown Assignee: wine-bugs(a)winehq.org Reporter: leslie_alistair(a)hotmail.com Distribution: --- Can someone add component comsvcs which will also cover mtxdm. -- 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 39413] New: Make it easier to monitor the TestBot activity
by wine-bugs＠winehq.org 04 Nov '18

04 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=39413 Bug ID: 39413 Summary: Make it easier to monitor the TestBot activity Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- At the bottom of the main page there is a list of the VMs and their status. However the information there is incomplete: * When a VM is reverting there is no way to know for how long it has been reverting. * When a VM is running a task there is no link to the corresponding task. * There is no history of events so if someone reports that something strange happened there is no way to check(*). So it would be nice to have something like BuildBot's Waterfall display. http://buildbot.buildbot.net/waterfall (*) Actually one could check the WineTestBot log but that has its own problems and requires poring over lots of traces. See bug 39410. -- 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 42070] New: Add "workaround" to defined keywords list to indicate that one or more workarounds are available for a bug.
by wine-bugs＠winehq.org 04 Nov '18

04 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=42070 Bug ID: 42070 Summary: Add "workaround" to defined keywords list to indicate that one or more workarounds are available for a bug. Product: WineHQ Bugzilla Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: bugzilla-unknown Assignee: wine-bugs(a)winehq.org Reporter: o.dierick(a)piezo-forte.be Distribution: --- Enhancement: Add "workaround" to the defined keyword list for open bugs, when one ore more working workarounds have been found. For Moderators: The conditions for the workaround keyword to be valid would be: - The workaround is documented in the comments or a reference is made to the AppDB entry where the workaround is documented (or to an external source). - The workaround is confirmed to be working at least for one person (not just an hypothetic workaround). - If multiple workarounds are discussed, the keyword is valid if one workaround meets the above conditions. Why the keyword?: Other users affected by a bug would know that a workaround exists without having to read all the comments to find out. If someone has documented a workaround in the AppDB for a specific application, and the bug is in fact affecting multiple applications, the keyword would reduce the need to document the workaround in the AppDB for every affected app, provided that the bug is properly referenced in the multiple AppDB entries. -- 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 5

[Bug 45340] New: app versions sorted incorrectly
by wine-bugs＠winehq.org 04 Nov '18

04 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=45340 Bug ID: 45340 Summary: app versions sorted incorrectly Product: WineHQ Apps Database Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: appdb-unknown Assignee: wine-bugs(a)winehq.org Reporter: shoefish(a)gmail.com Distribution: --- app version are not ordered by natural sort. That is, version 10 appears before version 2 instead of after version 9. The only reason It's worth mentioning is that often the latest version is the most interesting and because of this if someone just glances at an app they're likely to get the wrong impression. example: https://appdb.winehq.org/objectManager.php?sClass=application&iId=1347 -- 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

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 August 2018