https://bugs.winehq.org/show_bug.cgi?id=42758
Bug ID: 42758
Summary: test.winehq.org: Provide stats on the tests output
size
Product: WineHQ.org
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
The Wine test reports are pretty close to the 1.5 MB limit so having an idea of
which the biggest offenders are would be helpful.
test.winehq.org could easily extract this data while parsing the reports and
then generate some per-build index files showing the test units sorted based on
how much they spammed the report.
--
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=42757
Bug ID: 42757
Summary: test.winehq.org: Provide stats on the tests run time
Product: WineHQ.org
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
It would be interesting to have some information about where WineTest.exe
spends the most time as it sometimes takes close to 20 minutes (the maximum
allowed on the TestBot is 30 minutes so there is still some margin).
Having data on how long a test unit takes per platform could be valuable. This
would help identify which test units take too much time or which machines are
having trouble keeping up compared to their peers.
The WineTest reports contain run time data for each test unit with a 1s
granularity. This could be exploited to generate some extra per-build index
files showing the test units sorted by run time with some min, max and average
data.
--
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=38877
Bug ID: 38877
Summary: Ancestry Family Tree Maker 2014 on Wine1.6 Ubu14.04
Fails To Pass SN entry
Product: Wine
Version: 1.6.2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: loader
Assignee: wine-bugs(a)winehq.org
Reporter: jcjackson(a)joe-jackson.net
Distribution: ---
Ancestry Family Tree Maker 2014 on Wine1.6 Ubu14.04 Fails To Pass the Serial
Number Entry security pop-up, where the same install works properly on a
Windows partition on the same machine.
The Wine install worked without problem, and components like Notepad work as
expected, and the FTM install process starts as expected and seems to run well
up to the presentation of the security pop-up requesting the software serial
number, the error it throws is "Error Activating License! The requested feature
is not implemented. Please try again or visit our support site for help."
Retries do not work at all either. It is as if there is no network connection,
but the network features are working fine for other Ubu apps, and the install
works well on the Windows partition on the same machine.
One additional point, before winetricks would install 7-zip the permissions for
the .wine directory required normalization, .wine installed with just use
permissions for my user id without my group.
So few people use FTM there seems to be little chatter anywhere about the
install problems, most users seem to give up in 2009 and worked around by using
a Windows VM.
--
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=17063
Summary: Test results page should distinguish between 32-bit and
64-bit
Product: WineHQ.org
Version: unspecified
Platform: All
URL: http://test.winehq.org/data
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P2
Component: www-unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
Looking at http://test.winehq.org/data, it's hard to find x86-64 test results
(wine or windows). We should probably separate them out into their own column
next to the 32-bit OS, e.g.:
Win2k3 WinXP-32bit WinXP-64bit ... Wine-32bit Wine-64bit
We've got Platform under the report info that shows if it's x86 or x86_64, so
extending tools/winetest/dissect to account for this shouldn't be too much
trouble for a perl guru.
--
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=36198
Bug ID: 36198
Summary: winetest reports now starting to exceed 1.5MB limit
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: testcases
Assignee: wine-bugs(a)winehq.org
Reporter: alasdairsinc(a)gmail.com
some of my winetest submissions are running into the 1.5MB limit that is
currently enforced by winetest, the win32 and wow64 ones are the worst.
When slightly over we get parial submissions like my wow64 in
http://test.winehq.org/data/b84e112dd60e9fb6f4d04e82115fcb46e71f9693/index_….
--
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=42689
Bug ID: 42689
Summary: ACDSee Pro 10 won't launch the main UI
Product: Wine
Version: 2.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: spleefer90(a)gmail.com
Distribution: ---
Created attachment 57653
--> https://bugs.winehq.org/attachment.cgi?id=57653
main UI launch log
The program launches into tray, but opening it from there only shows up the
"launching UI" which then promptly disappears.
Logs from that attached.
Tested with recent wine-git
--
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=33734
Bug #: 33734
Summary: Word 2007 has wrong colors at window corners
Product: Wine
Version: 1.5.31
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdi32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: b7.10110111(a)gmail.com
Classification: Unclassified
Created attachment 44670
--> http://bugs.winehq.org/attachment.cgi?id=44670
Screenshot
See screenshot. Top corners have black dots, and bottom ones have purple dots.
--
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=14127
Summary: Microsoft Office 2003 - mouse scroll and combo boxes
behavior
Product: Wine
Version: 1.0.0
Platform: PC-x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dsent(a)mail.ru
Invoking mouse scroll over toolbars should not result in scrolling document if
some combo box on toolbar is opened. It should scroll values in opened combo
box (like font selector, font size selector, style selector).
Scrolling with mouse in regular dialogs with combo boxes works almost well (see
Tools->Options->Save "Save Word documents as" combo box). However, it works
only if mouse pointer is over that dialog. In Windows, it works if mouse is
outside dialog window (and even program's main window). Opened combo box "eats"
all mouse scroll events :-)
--
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=42224
Bug ID: 42224
Summary: Latest version Gigatribe crashes when running second
time
Product: Wine
Version: 2.0-rc5
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: Garfield80(a)gmx.com
Distribution: ---
Created attachment 56864
--> https://bugs.winehq.org/attachment.cgi?id=56864
a backtrace of gigatribe crash
I tried to run gigatribe 3.04 on my wine 2.0-rc5, but it keeps crashing
everytime after I've installed.
--
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=42750
Bug ID: 42750
Summary: sync.com 1.1.9: network limits have been exceeded.
Product: Wine
Version: 2.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tsartakov(a)gmail.com
Distribution: ---
Created attachment 57760
--> https://bugs.winehq.org/attachment.cgi?id=57760
execution log
sync.com client stop syncing after few minutes of work and show message:
Your Sync network limits have been exceeded.
Click here to increase them.
Client consists of two process: taskbar and worker.
Message appears after worker die
As i see worker tries use lock file.
Every seconds count of opened files by wineserver extended by 6 and most of
this descriptors are links to 'worker.lock' file
when count of opened files by wineserver achieve 4096 worker dies
The same behaviour on x86 clean installation.
--
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.