https://bugs.winehq.org/show_bug.cgi?id=38142
Bug ID: 38142
Summary: Approach fields box only show 3/4 of one line
Product: Wine
Version: 1.7.36
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ToddAndMargo(a)zoho.com
Distribution: ---
Created attachment 50869
--> https://bugs.winehq.org/attachment.cgi?id=50869
Field Box
Hi All,
Wine 1.7.36 and Smart Suite N9.8.0208.1200.
Would you guys please fix this for me. It is driving me NUTS!
In the "Find Assistant" the Fields box only shows about 3/4 on one line. It
makes it impossible to file the other lines in the box.
I will attach a screen shot
Many thanks,
-T
--
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=31882
Bug #: 31882
Summary: arial32.exe randomly crash or deadlock while
installing
Product: Wine
Version: 1.5.14
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fracting(a)gmail.com
Classification: Unclassified
Created attachment 41968
--> http://bugs.winehq.org/attachment.cgi?id=41968
Log: arai32 crash while installing
wine-1.5.14-142-g730479e
$ sha1sum arial32.exe
6d75f8436f39ab2da5c31ce651b7443b4ad2916e arial32.exe
Steps to reproduce:
$ winetricks -q corefont
Or
$ wine arial32.exe /q
How reproducible:
crash > 1/10
deadlock > 1/10
When deadlock, output is:
err:ntdll:RtlpWaitForCriticalSection section 0x15d60c "bitblt.c: surface" wait
timed out in thread 0009, blocked by 0024, retrying (60 sec)
When crashing, backtrace is:
Backtrace:
=>0 0xb757d08d __pthread_cond_signal+0xd() in libpthread.so.0 (0x0054e4d4)
1 0x7e4c4758 in libxcb.so.1 (+0x8757) (0x0054e4d4)
2 0x7e4c363e in libxcb.so.1 (+0x763d) (0x0054e4d4)
3 0x7e4c36c1 xcb_writev+0x70() in libxcb.so.1 (0x7d3d856c)
4 0x7e5330d0 _XSend+0x15f() in libx11.so.6 (0x0054e558)
5 0x7e5334fa _XFlush+0x39() in libx11.so.6 (0x0054e5f8)
6 0x7e512fc1 XFlush+0x30() in libx11.so.6 (0x0054e5f8)
7 0x7e681ecc create_x11_physdev+0xe1(drawable=0xae)
[/home/fracting/wine-git/dlls/winex11.drv/init.c:116] in winex11 (0x0054e5f8)
8 0x7e681ef6 X11DRV_CreateDC+0x1f(pdev=0x15ce38, driver="DISPLAY",
device=0x0(nil), output=0x0(nil), initData=(nil))
[/home/fracting/wine-git/dlls/winex11.drv/init.c:126] in winex11 (0x0054e638)
9 0x7eab3ddf CreateDCW+0x251(driver="DISPLAY", device=0x0(nil),
output=0x0(nil), initData=(nil)) [/home/fracting/wine-git/dlls/gdi32/dc.c:594]
in gdi32 (0x0054e918)
10 0x7e9b3af4 alloc_dce+0x76()
[/home/fracting/wine-git/dlls/user32/painting.c:232] in user32 (0x0054e948)
11 0x7e9b59e2 GetDCEx+0x34d(hwnd=0x30028, hrgnClip=(nil), flags=0x10000)
[/home/fracting/wine-git/dlls/user32/painting.c:1033] in user32 (0x0054e9c8)
--
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=45271
Bug ID: 45271
Summary: Silence winemenubuilder.exe error if it is disabled by
user
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tim110011(a)163.com
Distribution: ---
wine: cannot find L"C:\\windows\\system32\\winemenubuilder.exe"
000b:err:wineboot:ProcessRunKeys Error running cmd
L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (2)
This is not a error if it is disabled manually by user.
--
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=43938
Bug ID: 43938
Summary: wine-gecko does not have an arm build
Product: Wine-gecko
Version: unspecified
Hardware: arm
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: wine-gecko-unknown
Assignee: jacek(a)codeweavers.com
Reporter: austinenglish(a)gmail.com
Distribution: ---
This is blocked until mingw64 supports arm targets in a release, but for now,
dlls/mshtml/tests/* and friends fail on arm.
--
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=42888
Bug ID: 42888
Summary: Adobe Flash CS6 crashes after a few minutes
Product: Wine
Version: 2.6
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: demurgos(a)demurgos.net
Distribution: ---
Created attachment 58012
--> https://bugs.winehq.org/attachment.cgi?id=58012
Adobe Flash CS6 crash 1
Hi,
I just installed Flash CS6 with Wine 2.6 on two of my computers. It seems to
work fine on my older computer by I encounter some stability issues with my new
laptop. Both computers run Arch Linux 64 bits so the difference must come
either from the fact that I have less libraries on the new laptop or there are
some hardware issues.
Concretely, my issue is that if I start Adobe Flash CS6 and leave it open for
about 5 minutes, it crashes. I saved two backtraces (see the attachments). The
issue happens even if I do not mess with the program: leaving it open is enough
to cause the crash.
I documented the exact installation steps here:
https://github.com/demurgos/notes/blob/master/tools/emulation/wine/adobe-cs…
(I used the same steps for both computers.)
Here are the commands I used:
sudo pacman -S wine winetricks wine-mono wine_gecko
sudo pacman -S samba lib32-mpg123
mkdir -p /opt/wine/adobe-cs6
export WINEPREFIX=/opt/wine/adobe-cs6
export WINEARCH=win32
cd $WINEPREFIX
wine wineboot
winetricks msxml3 vcrun2008 vcrun2010 atmlib gdiplus allfonts
wine /patch/to/adob-cs6/Set-Up.exe
I then started Adobe Flash from the start menu.
--
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=22450
Summary: Can't disable unixfs
Product: Wine
Version: 1.1.43
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: shell32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
dlls/shell32/shfldr_unixfs.c claims that you can disable unixfs
by deleting the registry key
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Explorer\Desktop\Namespace\{9D20AAE8-0625-44B0-9CA7-71889C2254D9}
but unfortunately wine will recreate that key the next time you run
a newer version of Wine.
To repeat, do
rm -rf ~/.wine
wine regedit /d
'HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Explorer\Desktop\Namespace\{9D20AAE8-0625-44B0-9CA7-71889C2254D9}'
wine notepad # Do File/Open and note that / does not appear in My Computer.
wineserver -w
~/wine-git/wine notepad # Do File/Open and note that / *does* appear.
If we really want to disable unixfs, we may want a configure option
to not even compile it in. I have a patch ready, will send it in.
--
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=45091
Bug ID: 45091
Summary: wineboot: first boot hangs forever
Product: Wine
Version: 3.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: comeon(a)getbackinthe.kitchen
Distribution: ---
Created attachment 61260
--> https://bugs.winehq.org/attachment.cgi?id=61260
debug output
When I try to boot wine for the first time with no .wine folder, wine just
hangs forever. When doing `winecfg' without a .wine folder, it waits for about
5 minutes before saying:
0009:err:process:__wine_kernel_init boot event wait timed out
and then opening the winecfg menu. Can't see drives with this error:
0015:err:winecfg:open_mountmgr failed to open mount manager err 2
Attached the gzipped output of `WINEDEBUG=warn+all,err+all,fixme+all wineboot
-i', with no .wine folder.
--
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=44403
Bug ID: 44403
Summary: On macOS during first run, Wine configuration
population hangs
Product: Wine
Version: 3.0
Hardware: x86
OS: Mac OS X
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: joe.abbey(a)docker.com
Wine 3.0 is installed using brew for a CI job using electron-loader to build an
installer.
The first time wine runs, it creates the ~/.wine directory and registries.
Wine never completes, and hangs. Force killing the wine dialog and wine64
process produces enough configuration for a second run to complete.
Force killing during CI seems like a bad way forward.
To reproduce
rm -rf ~/.wine
brew install wine
Run any wine application and it will hang on config generation.
This is currently breaking Kitematic builds.
--
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=37777
Bug ID: 37777
Summary: ReadCube can't install
Product: Wine
Version: 1.7.33
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: litimetal(a)gmail.com
Distribution: ---
Created attachment 50315
--> https://bugs.winehq.org/attachment.cgi?id=50315
screenshot.png
ReadCube is a software to read scientific papers (like Nature)
https://www.readcube.com/download
I downloaded http://download.readcube.com/desktop/2.0.12/ReadCube-Setup.exe
$ sha1sum ReadCube-Setup.exe
972a2893e0b8b65e3cfaec5198b8d36b688e585c ReadCube-Setup.exe
$ wine --version
wine-1.7.33-84-gfecbc88
The installer refused to continue, as there are other ReadCude applications.
--
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.