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.
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.
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.
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.
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.
https://bugs.winehq.org/show_bug.cgi?id=44526
Bug ID: 44526
Summary: Building Biarch instructions: lxc-templates package is
not mentioned as requirement
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: juewei(a)fabmail.org
Distribution: ---
https://wiki.winehq.org/Building_Biarch_Wine_On_Ubuntu#Install_LXC
starts with
sudo apt-get install lxc
that should be
sudo apt-get install lxc lxctl lxc-templates
otherwise the subsequent lxc-create -t ubuntu ... cannot find the ubuntu
template.
I tried to create an account on the wiki, but I still do not see, if it should
be possible for me to suggest edits there directly. Please advise.
thanks,
--
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=32354
Bug #: 32354
Summary: testbot: A crashing test is not detected
Product: Wine-Testbot
Version: unspecified
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: wine.dev(a)web.de
Classification: Unclassified
A 64bit test crashed on all 64bit testbot machines,
but the summary has "0" as "Number of failures".
Test run for the broken patch:
http://testbot.winehq.org/JobDetails.pl?Key=22963&log_301=1#k301
Later test:
http://testbot.winehq.org/JobDetails.pl?Key=23106&log_302=1#k302
(I send a fix for the broken code in wine in some minutes)
--
By by ... Detlef
--
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=40237
Bug ID: 40237
Summary: account not deletable
Product: WineHQ Bugzilla
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bugzilla-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: BerlinerPaul(a)web.de
Distribution: ---
hi,
I want to delete my account but I'm unable to find some link in the preferences
for this.
best
--
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=39441
Bug ID: 39441
Summary: The reverts keep getting slower
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: ---
A revert that would take under 10 seconds right after creating the snapshot
would take over 7 minutes 6 months later. So every few months this would cause
the TestBot to become really sluggish and barely able to keep up with the patch
influx. Restarting libvirt, rebooting the host, restoring the VM from backup or
even transferring it to another host had no effect on the revert time.
While the revert is taking place the QEmu process fully occupies one core, no
disk I/O is performed and the VM is not running. The exact reason is not yet
known exactly but it seems to have to do with the VM's timer devices,
particularly the rtc one.
To confuse matters further not all VMs are affected: only Windows 2000, XP,
2003, 2008 and 10 suffer from this. The other post Windows Vista are immune.
Yet the guest is not active while the revert is taking place so it should not
have an impact on it.
Finally at WineConf 2015 it was discovered that the revert time of a live
snapshot is simply proportional to the snapshot's age.
This yielded a first workaround which is to refresh the live snapshots
regularly.
Further investigation showed that the common point between the impacted live
snapshots is that they all have the following clock settings
<clock offset='localtime'>
<timer name='rtc' tickpolicy='delay'/>
<timer name='pit' tickpolicy='delay'/>
<timer name='hpet' present='no'/>
</clock>
while the unaffected VMs have
<clock offset='localtime'/>
But switching from the former to the latter does not fix the affected VMs.
Still this lead to a better fix which has now been put in place: setting
track='guest' on the rtc timer.
Regardless, something is wrong with the way QEmu handles timers and live
snapshots so a bug was reported:
https://bugs.launchpad.net/qemu/+bug/1505041
Maybe this will shed some light on what's really happening and what the correct
timer settings are.
--
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=44581
Bug ID: 44581
Summary: *.winehq.org tls certificate deprecated
(Symantec/GeoTrust/RapidSSL)
Product: WineHQ.org
Version: unspecified
Hardware: Other
OS: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tyng(a)cock.li
https://groups.google.com/forum/#!msg/mozilla.dev.security.policy/Oaeqtddo_…
as of today for firefox nightly:
Error code: SEC_ERROR_UNKNOWN_ISSUER
--
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.